IRON LAW: No review-automation trigger caused by this workflow's planned publication events may be accepted or released until the final SHA is the authoritative remote head and every workflow-planned context write in the frozen publication plan except the atomic operation that emits the final trigger is authoritative. A context write may occur before the final SHA is remote when it is authoritatively proven non-triggering. A triggering or unknown context write may occur earlier only when documented suppression, batching, or coalescing guarantees that it cannot emit, accept, or schedule a trigger before those conditions hold and that the eventual trigger is bound to the final SHA and frozen context. Delaying run start after trigger acceptance is not safe. Verify every triggering or unknown context operation scheduled before thread transitions authoritatively before the first transition; for serial transitions that are themselves triggering or unknown, verify each transition before proceeding to the next.

Resolve Review Comments

Workflow

• 1. Preflight and trigger inventory
• 2. Fetch complete review context ⛔ BLOCKING
• 3. Build the item ledger and triage ⛔ BLOCKING
• 4. Implement fixes
• 5. Review-fix loop until verification and full-diff review converge
• 6. Commit and obtain publication approval
• 7. Synchronize replies and PR/MR context ⛔ BLOCKING
• 8. Push and transition threads
• 9. Verify automation and completeness

Global Rules