This repository was archived by the owner on Oct 11, 2026. It is now read-only.
Repository navigation
Enforce same-change machine recovery checks in CI - #1
Merged
Merged
Conversation
azuttre
marked this pull request as draft
October 11, 2026 16:52
azuttre
marked this pull request as ready for review
October 11, 2026 16:52
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Every source change now requires a recovery disposition tied to its exact Git content: updated authoritative owner documentation or a concrete no-impact explanation. The terminal CI job validates this evidence on PR and manual feature-branch runs. DSM manual changes are outside scope.
This coordinated rollout covers all 19 active owned non-fork repositories. Changes marked updated require their matching consolidated recovery catalog update to land before merging. Private-account plans cannot enforce required branch protection; the portfolio merge guard requires successful current-head CI, approved checker/policy pins and the landed central binding. Public repositories will require the terminal CI check through branch protection.
Maintainability: done. A single canonical stdlib checker is vendored with byte-pinned policy and meaningful regressions; CI stays offline with no private-catalog credential. The existing merge guard independently validates GitHub tree data and central evidence. Existing app validation remains in place; the recovery check itself adds seconds, and eight formerly CI-free repositories get a five-minute-bounded Python gate.
Review: required for shared CI and merge gates. Claude Opus5.5 via Alex's local Claude Code subscription, configured high with strict read-only/process monitoring, reviewed the full rollout. TAKE F1: manual runs must compare against the default branch and enforce exact feature-head evidence. Claude Sonnet, configured high completed the focused closure review with no remaining non-minor findings. Generated Python cache artifacts were removed; metadata exclusions now cover JSON receipts only. No additional review round is required for deterministic cleanup.
Validation: canonical portable checker 16 regression tests; Personal Context 85 focused tests; CoS 136 focused tests and 98 subtests, plus its full 4,193-test suite and 374 subtests. All 19 exact-change receipts and vendored hashes passed. Required app validation passed locally for Air Watch, Marcel, Leon, Central Perks and Venaison; full current-head hosted checks must pass before merge. Application/runtime behavior is unchanged.
Activation: normal cos-pull on each Mac activates source-linked hooks and the existing merge-guard shim; no service deployment, frozen runtime install or restart is needed.