Repository navigation
Bind selected stock diagnostics to the capture output - #32
Merged
EHotwagner merged 1 commit intoOct 3, 2026
Merged
Conversation
EHotwagner
deleted the
routine/bar-stock-pairing-output-source-repair-20261003
branch
October 9, 2026 16:28
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.
The selected stock smoke constructed its pairing context without outputPath. The new diagnostic writer therefore derived undefined.pairing-diagnostic.json instead of the owned capture destination. Bind outputPath to the existing admitted capturePath so pairing diagnostics are written beside the capture and arm-failure sidecar.
Strengthen the existing sidecar control to execute the actual selected-stock initializer with synthetic handoff/environment values and a journal stub, then call the actual diagnostic writer. It reproduces the old writer refusal, verifies the capture-derived destinations after repair, and refuses a foreign capture before journal construction. All fourteen existing JavaScript controls pass; source syntax, scope/trigger checks, routine eligibility and 59operation-boundary fixtures pass. Workflow and Gateway/union bytes remain identical.
This is source-only qualification. Native exact-head checks remain required. Fresh artifact/build/custody, any runtime grant and protected activation remain pending separate root admission. Historical cause and READY/raw-map gaps remain Unknown; useful native play remains 0/6.