1.9 KiB
1.9 KiB
id, title, status, wave, depends_on, plan, requirements, acceptance_criteria, system_design
| id | title | status | wave | depends_on | plan | requirements | acceptance_criteria | system_design | |
|---|---|---|---|---|---|---|---|---|---|
| 08-verify-complete-migration | Verify complete specification migration | completed | 8 |
|
plan.md |
Task 08: Verify complete specification migration
Summary
Run the repository's structural and link checks, inspect the final diff for lost source detail, and record the verification results in the migration plan.
In scope
- Specification linter unit tests and full lint.
- Markdown link and
spec:reference audits. - Size-limit, duplicate-ID, frontmatter, and migration-state checks.
- Final diff review for deleted or unintentionally changed source content.
Out of scope
- Broad application tests unrelated to documentation.
- Semantic redesign of an existing product contract.
Acceptance
- All specification tests and lint checks pass.
- No legacy
spec.mdorplan.mdremains in an editable system tree. - Every completed system has
migration: completeand an authoritative map.
Verification
python3 scripts/lint-spec-files.test.py
python3 scripts/lint-spec-files.py --all
make lint-specs
git diff --check -- docs/specs docs/decisions docs/plans
Files likely touched
docs/plans/specification-migration/plan.md
Dependencies
Task 07.
Risks
- A passing structural linter does not prove that a migrated document kept all behavior detail. Compare each moved source and its canonical replacement.
Parallelism
sequential
Inputs
- The completed migration diff.
- The specification guide and linter output.
Results
Completed. The specification test suite, full specification lint, size and
duplicate-ID checks, frontmatter checks, migration-state checks, and diff
whitespace audit all passed. The final inventory contains no editable legacy
spec.md or plan.md under docs/specs/.