gsd-audit-milestone

Milestone verification assesses alignment with its definition of done by aggregating verification data across multiple phases, reading existing VERIFICATION.md files, and highlighting coverage gaps. It provides orchestration gates and end-to-end validation to ensure readiness before archiving.

Aggregating technical debt and deferred gaps requires reading verification files from all phases to consolidate findings into a single source of truth. This process provides a comprehensive view of milestone readiness and highlights outstanding coverage gaps across the workflow.

End-to-end integration wiring is validated by spawning an integration checker that assesses cross-phase connections. It operates across multiple phases, aggregates verification data, and guides archiving decisions based on consolidated milestone readiness.

Milestone audit workflows require existing VERIFICATION.md files to aggregate findings and highlight coverage gaps. Without these files, the workflow cannot consolidate technical debt or assess phase alignment against the definition of done for archiving decisions.

Incomplete cross-phase wiring coverage appears when the integration checker identifies gaps in end-to-end validation. The audit process aggregates these deferred gaps from verification files, indicating that milestone completion criteria are not fully met before archiving.