Abbey Next Parsing and Validation
Made Abbey's NEXT.md planning contract executable and closed an existing framework backlog item.
Tags: Abbey Root
Abbey Next Parsing and Validation
Summary
Improved abbey next so its planning input has one documented, validated
structure. The command now accepts normal Markdown heading and body formats,
reports every missing required section clearly, and can create a safe skeleton
with abbey next init.
Accomplishments
- Established six stable NEXT.md sections shared by the planning schema,
abbey init,abbey next init, and Abbey Root itself. - Added guarded template generation that never overwrites an existing NEXT.md.
- Added deterministic regression fixtures and expanded Abbey Next coverage from its pre-existing failing baseline to 39 passing tests.
- Kept Abbey Init green with 25 passing tests.
- Closed the existing Abbey Framework backlog parent, moving the generated count from 93 to 94 complete and from 267 to 266 pending.
Lessons Learned
- Backlog-clearing sessions should define success using checkable parent items, not only descriptive subtasks.
- Regression fixtures must not inherit mutable live planning state.
- A documented structure becomes durable only when generators, consumers, and validation enforce the same contract.
Next Steps
- Use the improved validation during normal Abbey work; no follow-up backlog item is required for this change.