WORK-126
ID:WORK-126Status:done

Parse Resolution sections in the plan scanner

Extend the plan scanner to extract ## Resolution sections from work item and bug files into a structured resolution field on PlanEntity.

Priority:highComplexity:moderateMilestone:v1.0.0Source:SPEC-027
main View source

Criteria completion

No incremental history — criteria tracking started on Apr 21.

Relationships

Implements 1
Branches 2
main current done
claude/file-naming-convention-LJdwR donechangeset-release/main done
History 2
  1. e900a90
    Created (done)by bjornolofandersson
  2. 1676387
    Created (done)by Claude
    Accept SPEC-037 and break into work items; fix plan validation issues

Acceptance Criteria

  • PlanEntity interface in runes/plan/src/types.ts gains an optional resolution field with date, branch, pr, and body subfields
  • parseFile() in runes/plan/src/scanner.ts extracts the Resolution section from the raw source when present
  • Completed: line is parsed into resolution.date (ISO date string)
  • Branch: line is parsed into resolution.branch (backticks stripped)
  • PR: line is parsed into resolution.pr
  • Remaining content goes into resolution.body
  • Files without a ## Resolution section produce resolution: undefined
  • Unit tests cover: full resolution, minimal resolution (just a sentence), missing resolution, resolution with only some fields

Approach

Add a Resolution interface to types.ts. In the scanner, after extracting criteria, locate ## Resolution within the rune's line range and parse it using simple line-prefix matching as described in SPEC-027. The extraction should work on the raw source string (not the AST) since it's a convention-based section, similar to how extractCriteria works.

References

  • SPEC-027