Add resolution validation checks to plan validate

Add three resolution-related checks to refrakt plan validate as specified in SPEC-027.

claude/file-naming-convention-LJdwR View source

Criteria completion

No incremental history — criteria tracking started on Apr 21.

Relationships

ID:SPEC-027Status:accepted

Work Item Resolution Summaries

Version:1.0

ID:WORK-071Status:done

Lumina Per-Rune Redundant CSS Cleanup

Priority:lowComplexity:moderateMilestone:v0.9.0

claude/file-naming-convention-LJdwR current done

main done changeset-release/main done

Apr 21, 01:29 PMbbbb94c
Created (done)by bjornolofandersson
Apr 21, 01:17 PMf2b3512
Content editedby Claude
Add {ID}-{slug}.md filename convention + migrate filenames subcommand

Acceptance Criteria

Info-level check: work/bug items with status done/fixed but no ## Resolution section
Warning-level check: items with a ## Resolution section but status is not done/fixed
Warning-level check: files with multiple ## Resolution headings
All three checks appear in plan validate output with correct severity levels
Unit tests cover each check

Approach

Add a checkResolutions() function in runes/plan/src/commands/validate.ts. This depends on the scanner exposing resolution data (WORK-071), so the checks can use entity.resolution to determine presence. Alternatively, the validator could do its own raw-text scan of the file for ## Resolution headings to avoid depending on the scanner change — simpler but slightly redundant.

References

SPEC-027
WORK-071 — scanner resolution parsing (dependency)

Resolution

Completed: 2026-03-30

All three resolution checks implemented in runes/plan/src/commands/validate.ts with checkResolutions() function. Five unit tests cover each check type. All criteria verified met.