cloud: original OpenCloud Files UI for private read-only recovery - #4
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Working owner-local recovery interface
Connects the source-built original OpenCloud Web8 Files application to the existing private catalog/read service. Explicit numeric-loopback recovery uses an in-memory bearer and honest read-only local authority, not a fabricated upstream OIDC/account identity. Normal upstream authentication is unchanged unless this mode is selected.
The product seam adds authenticated readonly capability/space projection, coherent catalog-bound space/resource IDs, original navigation/download support and exact hash-verified public assets. No new storage ledger, redundancy setting, origin fallback or private-content publication is introduced. Documentation includes the explicit source-build and usage procedure.
Actual UI verification
The original Files UI in a fresh isolated Firefox140.16.0 profile passes project listing, root and nested navigation, two actual Downloads with exact-byte checks, wrong-token denial, in-memory-only token checks, logout/relocking and removal of both temporary materializations plus the private profile. This trial has a synthetic backend, explicitly not peer-storage evidence.
Original receipt SHA256
320480e45a88a3cabafd357d6f0dce1e449ba7e9691f7c7a59d2118cf5f03644; upstream11e699ac82fda4dd113ac3ceb2ecb2dd74574045; patchf7d26672d3a571f7beceb65b3bffffaedcc4191a9f9e59cef30d0dba56cb8064; build report3a482aef27fe84d057eab2958b3d6c9076c968103efcbc3ee19d3fcf3092b62c.Thirty catalog/HTTP checks, nine service/asset checks and the original pinned SDK read check pass. Independent review of authentication, catalog-only ID resolution and read-only projection found no blocker. Dependencies are frozen-lock with lifecycle scripts off; the actual Vite build is offline. No global installation or host-network changes.
Boundaries
The prior real SDK-to-peer trial remains separate. A joined original-UI/peer proof, upstream account enrollment, cross-device key/catalog recovery, writable synchronization and sharing/revocation remain open. This PR is a usable owner-local read-only interface milestone, not complete server-independent OpenCloud.
Exact head:
b134275294ecd4c81a6695e9c14c8af70967c406.