Repository navigation
governance: prevent recursive state-only reconciliation loops - #144
Conversation
|
Exact-head Windows Certification failed on |
* ci: supervise Windows Playwright app server * ci: restart unhealthy Playwright app server * fix(ci): harden local E2E server shutdown and URL validation
|
Exact-head CI observation for |
|
Candidate documentation was corrected and pushed with expected-head protection. New exact head: |
|
After durable status sync and live Gate A/A2 reconciliation, current candidate is |
|
Merged exact reviewed head |
Scope
Prevent continuous AI fallback execution from entering a self-referential post-merge state-sync loop.
Root cause
After a reconciliation PR merges, fields such as
observed_main_sha, active PR identity and merge metadata naturally point to the prior source baseline. Treating that expected pointer drift as standalone fallback work can create:state-sync PR -> merge -> pointer stale again -> another state-sync PR.Changes
observed_main_shaas a resume anchor, not live Git authority9e6e95082fd8bc5511dc5502a3e3259203667356Safety
This does not weaken live Git rehydration, README/state semantic synchronization, exact-head certification, review, security, product-scope, migration, provider/production/release or Runner authority.
Verification
Fresh exact-head WorkIntel CI, Code Quality and Windows Certification are required before merge.