Repository navigation
Retain bounded pairing diagnostics before BAR native readiness - #31
Merged
EHotwagner merged 3 commits intoOct 3, 2026
Merged
Conversation
EHotwagner
deleted the
routine/bar-prearm-diagnostic-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
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.
The selected browser failure lacked authentication, bootstrap, and close classifications. Add four finite Gateway pairing reasons, preserving existing union tags, and a bounded private browser sidecar so future qualified attempts retain those observations without credentials or payloads. Historical failure cause remains Unknown; useful native play remains 0/6.
Wire native source qualification for these previously uncovered paths through one exact-head, read-only linear job: fourteen JavaScript source controls, one .NET restore/build, and exactly three synthetic compiled controls. The test receipt refuses zero, missing, skipped, or unexpected results. Gateway/live/project/tool dependencies trigger the job. Existing RuntimeEvidence workflow bytes are unchanged.
Preflight: static YAML/trigger/shell/exact-result checks; a custom model adds no useful interaction coverage for this linear job. Local SDK10.0.401 build passed with zero warnings, three exact compiled tests and fourteen JS controls passed, existing tags0–14 plus four appended tags passed compiled reflection, and routine eligibility plus59operation-boundary fixtures passed. Local Node26.10.0 differs from hosted24.8.0; native exact-head acceptance is still required.
Publication, protected activation, new captures or runtime grants, and native operation remain separately pending.
Native run 37145445532 at the previous head passed the fourteen hosted JavaScript controls, then refused protobuf generation because pinned grpc-fsharp 0.2.0 requires .NET 6 and the runner has 8/9/10. Compiled controls were skipped. Supply DOTNET_ROLL_FORWARD=LatestMajor only to the build step, following the repository's existing generator policy; retain SDK10.0.401, Node24.8.0, pinned dependencies, all controls, and RuntimeEvidence bytes.
Setup-only validation: the unchanged generator on an isolated .NET-10-only host refused with exit150 without the setting and succeeded with exit0 with it. YAML/environment-scope/shell checks confirm all other workflow data unchanged. No build/test repetition or native/game operation was performed for this setup repair. Repaired exact-head native acceptance remains pending.