status

# Draft Status Display a comprehensive overview of project progress. ## Red Flags - STOP if you're: - Reporting status without actually reading the files - Making up progress percentages - Skipping blocked items in the report - Not checking each active track's actual state - Summarizing without evidence from the files **Always read before reporting.** --- ## Gather Data 1. Read `draft/tracks.md` for track list 2. For each active track, read: - `draft/tracks/<id>/metadata.json` for stats. If `metadata.json` is malformed or unreadable, display `(metadata unavailable)` for that track's statistics instead of failing. - `draft/tracks/<id>/plan.md` for task status - `draft/tracks/<id>/architecture.md` for module status (if exists) - `metadata.json:scope_includes` / `scope_excludes` for the track's scope footprint. Surface these in the status output so reviewers can spot overlap at a glance. Conflicts are detected by `scripts/tools/check-scope-conflicts.sh` (see [core/shared/template-contract.md](../../core/shared/template-contract.md)). 3. Check for project-wide `draft/.ai-context.md` (or legacy `draft/architecture.md`) for module status 4. **Detect orphaned tracks:** - Scan `draft/tracks/` for all directories - For each directory, check if it has `metadata.json` - Cross-reference with `draft/tracks.md` entries - If directory has metadata.json but NOT in tracks.md → orphaned track - Collect list of orphaned track IDs for warning...