Repository navigation
[codex] Fence Web correction preview ownership and background lifecycle - #40
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
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.
Scope
Related to #3 and #2. Preserve the single canonical Web source, existing editor
and shared HTTP owner. The already-integrated preview-on-edit adapter now keeps
the original connection-generation pin for acquire, renewal, readback and release
instead of obtaining fresh generic command admission. No named WebSocket preview
command exists, so none is invented.
Hidden-document/pagehide events retire the owned RAM lease. Foreground/BFCache
return is passive; disposal removes listeners. Explicit Save remains the only
persistent correction writer. Rules, indices and diagnostic numbering are unchanged.
Verification
HTTP tests pass, including captured-pin identity, background/page departure,
passive restoration, same-board connection replacement and listener disposal.
hash-bound comparison checks pass. Only reviewed changed-file references were
rebound; donor counts and pending gaps are not promoted.
aa518a96eea2dd7d787cb0a31d5191c78886e2e31605eda64458a0cea728835d:
HTML546206 bytes / gzip154031 bytes.
this is not rendered-browser or hardware acceptance.
Remaining boundaries
Explicit workspace-panel hiding, rendered/RTL/touch lifecycle and actual board
lease/output acceptance remain open. Windows browser URL-policy enforcement
still blocks visual automation; no alternate route bypassed it. No board,
production client, saved configuration, firmware upload or actuator was contacted
or changed. The previously blocked/deferred generated bytecode file is untouched.
CI remains a separate exact-head gate. GitHub connector creation returned403
because its integration lacks write access; authenticated gh is the documented
publishing fallback.