Repository navigation
ci: promote the realized Go 1.27 bridge authority - #1040
Merged
intel352 merged 1 commit intoOct 9, 2026
Merged
Conversation
intel352
marked this pull request as ready for review
October 9, 2026 18:41
intel352
deleted the
prep/ci-go127-bridge-promote-f043-01a11223-20261008
branch
October 9, 2026 18:41
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.
Promotes the realized Go 1.27 bridge workflow and complete 38-member policy bundle from staged to active authority, removing obsolete bridge groups. Only five policy JSON files change; executable bytes, unrelated authority and the realized staged benchmark group are preserved.
Exact head:
040610a6e4cbde25acd357972fc5f490fb89a071, based on accepted Task16 mainf043410f5dc727af7adc800e48786a31c09b3f7e(#1039). Independent security and antagonistic reviews verified the full frozen source inventory, row conservation and source equality.Current hosted checks: 19 success, two failures, one skipped and one neutral. Trusted policy passes; Go tests, lint, build, UI and security scans pass. The candidate harness failure is exactly the original EVENT_NAME fixture signature admitted only through original Tasks1–4 by ADR0155. The original diagnostic and native scanner-debt evidence remain retained. Task5's actual repaired hosted harness must pass and expire that exception before Task6.
The benchmark retry failure is retained as advisory under Jon's ADR0172/B14 disposition; cached equality and same-host comparison no longer gate this promotion. The accepted B15 plan retains separate Task4 stage, Task5 source adoption and Task6 promotion for the shared repair needed by #1042/#1043/#1044.
Fresh GitHub readback still reports REVIEW_REQUIRED and no formal reviews. Independent agent reviews are supporting evidence; they do not invent a GitHub approval. Any authorized admin merge remains subject to the actual platform response and immediate-main verification.