Repository navigation
📝 Register fixed remote-target programs outside the sync fence - #111
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
Draft against core-split. Head: e6ff1e1.
The documentation registry names the updater remote-target spawnSync program without extending the AST census or granting allowances. Future encoded sync programs require a source comment, pinned-constant test and registry entry. Python staging remains explicitly deferred until its next move/change.
Root test:remote-target-programs runs the registry check. Root test:unit:source now runs that named command FIRST with &&, followed by every previous package-suite command unchanged. The existing hosted Unit tests step therefore reaches the check without workflow edits. The registry documents this wiring.
The wiring amendment changes only package.json and scripts/remote-target-programs.md. Fence, allowances, pinned inventory, workflows, production source and registry test source are unchanged.
Validation status
Exact-head local checks and root-chain mutation controls are PENDING DISK RECOVERY. The initial test attempt was refused before test subprocess spawn under the 3 GiB floor. Point explicitly authorized committing and pushing before local validation. Static inspection confirmed the root prefix and unchanged remaining source-unit chain. No local whole-chain run occurred. E1 did not dispatch CI.
After space recovers, E1 must run the named check and prepared root-chain mutation controls on both Bun 1.3.13 and 1.3.14 at this head, restoring source and rerunning green. Hosted CI and Fable review remain point-owned; no hosted result is claimed here.
Historical parent-head evidence at da86413: registry 5/0, updater 146/0, fence 175 pairs on both Buns, plus six direct-check mutation negatives. Those results are not current-head acceptance and did not establish root-chain wiring.