Conversation
…ed required_status_checks
Theme C of the AceHack/LFG 0/0/0 reconciliation per
`docs/0-0-0-readiness/CLASSIFICATION.md`.
Single-line additive change: add `"build-and-test (macos-26)"`
to the required_status_checks contexts list in alphabetical
position (before existing `build-and-test (ubuntu-*)` entries).
Verification (per the bounded-provenance rule): macos-26 IS
already in actual LFG branch protection, confirmed via:
gh api repos/Lucent-Financial-Group/Zeta/branches/main/protection \
--jq '.required_status_checks.contexts'
Returns:
['lint (semgrep)', 'lint (shellcheck)', 'lint (actionlint)',
'lint (markdownlint)', 'build-and-test (macos-26)',
'build-and-test (ubuntu-24.04)', 'build-and-test (ubuntu-24.04-arm)']
So LFG's expected.json was the drift; AceHack's expected.json
correctly captured the actual branch-protection state. This
commit corrects expected.json to match reality (and matches
AceHack).
Will be flagged by github-settings-drift workflow on next run
as 'no drift detected' — the expected snapshot now matches the
actual state.
Closes Theme C. After this lands, all 4 NEEDS-FORWARD-SYNC files
should be reconciled; tree-diff between origin/main and
acehack/main on the AceHack-newer side should reach zero.
There was a problem hiding this comment.
Pull request overview
Aligns the repo’s expected GitHub branch protection snapshot with the already-live branch protection configuration by adding the missing macOS required check context, supporting the 0/0/0 drift reconciliation plan.
Changes:
- Add
build-and-test (macos-26)torequired_status_checks.contextsin the expected GitHub settings snapshot.
AceHack
deleted the
ops/theme-c-expected-snapshot-macos-26-forward-sync-2026-04-28
branch
4 tasks
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.
Theme C (final) of the AceHack/LFG 0/0/0 reconciliation per
docs/0-0-0-readiness/CLASSIFICATION.md.Single-line additive change to expected.json: macos-26 IS already in actual LFG branch protection (verified via gh api). LFG's expected.json was the drift; this commit makes it match reality.
Pure 1-line addition, no other changes.
Closes Theme C — final NEEDS-FORWARD-SYNC item. After this lands + Themes A (#696) + B (#697), tree-diff should reach zero, completing Step 2 of the path-to-0/0/0 plan.