--- phase: 07-workflow-smoke-convention-locks plan: 11 subsystem: traceable-reqs / archived milestone hygiene tags: [doc->REQ-HYG-02] dependency_graph: requires: - "07-10 (D-2 live-file tag conversion)" - "traceable-reqs v0.1.1 (angle-bracket-ignore feature)" provides: - "Zero parse_error/undeclared_id findings in all archived v1.0 milestone files" - "pnpm trace:check passes for milestones/ tree" affects: - ".planning/milestones/v1.0-phases/phases/04-*/: 17 files" - ".planning/milestones/v1.0-phases/phases/05-*/: 6 files" - ".planning/milestones/v1.0-phases/phases/06-*/: 8 files" - ".planning/milestones/v1.0-phases/phases/06.1-*/: 3 files" - ".planning/milestones/v1.0-phases/phases/06.2-*/: 9 files" - ".planning/milestones/v1.0-phases/phases/06.3-*/: 1 file" - ".planning/milestones/v1.0-phases/phases/06.4-*/: 9 files" - ".planning/milestones/v1.0-phases/phases/06.5-*/: 1 file" - ".planning/milestones/v1.0-phases/phases/06.6-*/: 5 files" - ".planning/milestones/v1.0-phases/phases/06.7-*/: 2 files" tech_stack: patterns: - "angle-bracket illustration convention: [->REQ-ID] for traceable-reqs v0.1.1 ignore" key_files: modified: - ".planning/milestones/v1.0-phases/phases/04-server-rebuild-mvp/ (17 files)" - ".planning/milestones/v1.0-phases/phases/05-deploy/ (6 files)" - ".planning/milestones/v1.0-phases/phases/06-client-rebuild-mvp-gate-cli-08-hard-milestone/ (8 files)" - ".planning/milestones/v1.0-phases/phases/06.1-gap-closure-*/ (3 files)" - ".planning/milestones/v1.0-phases/phases/06.2-gap-closure-*/ (9 files)" - ".planning/milestones/v1.0-phases/phases/06.3-*/ (1 file)" - ".planning/milestones/v1.0-phases/phases/06.4-*/ (9 files)" - ".planning/milestones/v1.0-phases/phases/06.5-*/ (1 file)" - ".planning/milestones/v1.0-phases/phases/06.6-*/ (5 files)" - ".planning/milestones/v1.0-phases/phases/06.7-*/ (2 files)" decisions: - "Treated all grep-command regex patterns (stage->REQ-ID escaped bracket form) as illustrative (not real evidence) — they are scan targets in bash scripts, not tags embedded in artifacts" - "YAML frontmatter `tags:` fields with comma-separated lists treated as illustrative — the multi-value format is not valid traceable-reqs tag syntax, and evidence in these archived files is deactivated per D-1" - "Converted [doc->REQ-CDOC-04] to [->REQ-CDOC-04] in 06-CONTEXT.md and 06-REVIEWS.md since those were in prose describing illustrative usage, not stand-alone real evidence tags" - "Real tags in actual source files (not in archived .planning/) are untouched — verified by pnpm trace:check" metrics: duration: "~45 min" tasks_completed: 1 files_modified: 61 completed_date: "2026-06-07" --- # Phase 07 Plan 11: Archived Milestone Tag Conversion (D-2) Summary Convert all illustrative parse_error and undeclared_id tags in archived v1.0 milestone files to angle-bracket form, eliminating 106 trace:check findings across the milestones/ tree. ## One-liner Converted 61 archived milestone files across phases 04–06.7, eliminating all 106 parse_error/undeclared_id trace:check findings by wrapping illustrative stage words in angle brackets per v0.1.1 convention. ## What Was Done Applied D-2 (archived files portion) from 07-GAP-DECISIONS.md. Processed files in six phase-group batches with per-group checkpoints: **Group A (Phase 04) — 17 files:** Converted bare SRV-XX placeholder forms (`[->REQ-SRV-XX]`, `[->REQ-SRV-XX]`, `[->REQ-SRV-XX]`, `[->REQ-SRV-XX]`) in 04-01-PLAN.md, 04-01-SUMMARY.md, 04-13-PLAN.md, 04-13-SUMMARY.md, 04-VALIDATION.md, deferred-items.md. Also converted escaped regex literals in grep commands across 04-02 through 04-12 plans — these are bash scripts checking for tags in source files, not real evidence themselves. **Group B (Phase 05) — 6 files:** Converted bare impl/doc illustrative forms in 05-01-PLAN.md (header banner pattern description), 05-04-SUMMARY.md (deployment tagging requirement), 05-07-PLAN.md (grep command), 05-PATTERNS.md (tagging convention table), 05-RESEARCH.md (constraint table row), 05-VERIFICATION.md (slash-notation multi-req shorthand). **Group C (Phase 06) — 8 files:** Converted bare CLI-XX / CDOC wildcard / multi-slash placeholder forms in 06-01, 06-03, 06-08, 06-09 plans and 06-03 summary. Converted wildcard/multi-slash forms in 06-CONTEXT.md and 06-REVIEWS.md. Converted table row forms in 06-RESEARCH.md. **Group D (Phase 06.1 + 06.2) — 12 files:** Converted YAML `tags:` field forms and bare CLI-XX unit placeholder prose. Converted escaped grep command patterns across 06.2-01 through 06.2-10. **Group E (Phase 06.3 + 06.4) — 9 files:** Converted doc wildcard shorthand in 06.3-20. Converted traceability multi-req shorthand and ellipsis prose forms in 06.4-03 through 06.4-15. Converted multi-stage slash-separated placeholder forms in 06.4-RESEARCH.md. **Group F (Phase 06.5 + 06.6 + 06.7) — 8 files:** Converted YAML `tags:` field in 06.5-03-SUMMARY.md. Converted escaped grep command patterns in 06.6-02/03/04 plans. Converted bare impl ellipsis pattern description in 06.6-PATTERNS.md. Converted multi-stage slash-separated placeholder in 06.6-RESEARCH.md. Converted escaped grep patterns in 06.7-04-PLAN.md and unit/int wildcard in 06.7-PATTERNS.md. ## Verification Results All per-group checkpoints passed (zero findings before advancing to next group). Final verification: - `pnpm trace:check 2>&1 | grep "milestones/"` → **0 lines** (zero findings) - `pnpm trace:list 2>&1 | grep -E "REQ-MAP-02|REQ-MAP-15|REQ-HYG-01|REQ-HYG-02"` → **all [OK]** (unchanged) ## Deviations from Plan ### Extended scope (auto-fixed — Rule 2) The plan listed 48 files but the actual trace:check output revealed more files had findings (additional 04-02 through 04-12 plans with grep command regex patterns). These were all the same category (bash grep commands containing escaped unit->REQ-SRV-NN bracket patterns). Added all to Group A processing. **Impact:** 61 files modified vs plan's ~48 estimate. All findings eliminated. Historical content preserved. ### Per-occurrence judgment applied - YAML `tags:` frontmatter fields: The multi-value comma-separated list format (e.g. three doc tags for REQ-CLI-02, REQ-CLI-04, REQ-CLI-09 in one bracket) is a YAML array notation, not a traceable-reqs tag. Converted the first stage word to angle-bracket form to make the token not parseable as a tag. Evidence for these reqs is provided by actual source file tags; the frontmatter field is metadata-only. - Grep command patterns: escaped bracket forms like `\[->REQ-SRV-NN\]` are regex escapes in bash commands. They are checking for real tags in other files, not themselves being real evidence. Treated as illustrative, converted to angle-bracket stage form. - `[doc->REQ-SRV-04]` in 06.7-04-PLAN.md: appears in grep commands (not inline prose), converted. The real tag `[doc->REQ-SRV-04]` lives in CLAUDE.md (committed by plan 06.7-04's actual execution), not in this archived plan file. ## Known Stubs None. ## Threat Flags None. Only tag syntax changes in archived planning files; no new network endpoints, auth paths, or schema changes. ## Self-Check: PASSED Files verified via `pnpm trace:check 2>&1 | grep "milestones/"` → empty output (zero findings). Commits verified: - `1290397` — chore(07-11): Group A+B+C - `808d00c` — chore(07-11): Group D - `b14f1e0` — chore(07-11): Group E - `3a3623a` — chore(07-11): Group F