project-queue-audit

To audit GitHub issue queue readiness, you reconcile Project metadata with issue-body runtime markers and dependency refs to classify dispatch safety as Manual, Dependency-gated, Blocked, or Ready. This process validates unsafe projection patterns and verifies cross-field consistency before automation execution.

Dependency gating blocks automation dispatch until referenced issues are closed and PRs are merged. Unverifiable or cross-repo references without clear identifiers are treated as blockers to ensure unsafe dependencies are never automatically dispatched.

Yes, you can prevent unsafe project dispatches by cross-checking issue body runtime markers against GitHub Project fields like AutomationState and DispatchMode. This consistency check ensures the queue state labels and dependency refs match before classifying an item for local automation.

Resolving contradictory GitHub Project and issue queue states requires assigning the safest classification when multiple risks exist. You verify dependency closure, enforce the OnePRContract for unattended dispatch, and produce explicit dry-run versus apply guidance for operator action.

You should not use automated dispatch for blocked GitHub issues when dependencies are unclosed, PRs are unmerged, or cross-repo refs lack clear identifiers. Items without concrete boundaries, acceptance criteria, or required validation evidence must remain in Manual state.