design-15 S6b: preview + encrypted endpoint vault + backend error surface (0.4.0-alpha.1) - #3
Merged
Merged
Conversation
design-15 §7 companion slice (0.4.0-alpha.1): - preview (read): pulls the same vpn-core export, reads the remote managed sub, and reports added/removed/unchanged labels — no writes, full links never leave the artifact. - save_endpoint / clear_endpoint / endpoint_status: the endpoint (and the auto-sync flag) lives in this plugin's encrypted vault via secret:read/secret:write; endpoint_status hints scheme://host only, so the secret path never round-trips. The server resolves secret:// operator-target references for status/preview/import calls. - http responses now decode body_base64 and non-2xx failures surface the Sub-Store backend's own error text (bounded, flattened); transport failures stay opaque so the secret path cannot leak. - UI: Preview changes panel, save/use/clear endpoint controls, auto-sync toggle; secret:// references accepted by the endpoint validator. - Manifest declares backing="runtime" per the alpha server's require-declared-backing gate; bundle rebuilt and re-signed.
The plugin stores one versioned endpoint document, reports vault and autosync failures, serializes dirty follow-up syncs, and removes secret-bearing response and preview text. The prerelease manifest is signed against the deterministic bundle. Constraint: Endpoint changes and autosync outcomes must be observable without leaking credentials. Rejected: Independent secret keys | permits torn endpoint and autosync state Confidence: high Scope-risk: moderate Directive: Preserve atomic endpoint writes and explicit degraded status semantics. Tested: UI tests and typecheck; Go race tests and vet; deterministic Node 22/Go 1.26.4 bundle; server-parity manifest verification Not-tested: Live Sub-Store service before canary deployment
lr00rl
marked this pull request as ready for review
July 22, 2026 13:29
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.
Summary
design-15 §7 companion slice (pairs with LatticeNet/lattice-server#16):
preview(read,proxy:read): pulls the same vpn-core export, reads the remote managed sub, returns added/removed/unchanged labels (URL fragment → host fallback) — read-only, full links never leave the artifact.save_endpoint/clear_endpoint/endpoint_statusviasecret:read/secret:write(§9.4 encrypted store, this plugin's own namespace).endpoint_statushintsscheme://hostonly — the secret path never round-trips. Operator calls then usebase_url: "secret://endpoint", which lattice-server#16 resolves before operator-target binding. Theautosyncflag stored alongside drives the server's debounced auto-sync.body_base64; non-2xx failures surface the Sub-Store backend's own error text (bounded 4 KiB, flattened). Transport failures stay opaque — the existing no-leak test (secret URL path) still pins that behavior.secret://refs.backing:"runtime"(require-declared-backing gate); capabilities +=secret:read,secret:write; bundle rebuilt (Go 1.26.4 / Node 22), packed 2× byte-identical, re-signed (server-parity OK).Verification
-count=1Refs LatticeNet/lattice#2, LatticeNet/lattice-server#16.