Acceptance Criteria
spec rune accepts implemented and shipped status values (schema, enums.ts, MCP)spec rune accepts an optional released-in attribute (semver format, e.g. v0.11.4)decision rune accepts a rejected status value (in addition to proposed | accepted | superseded | deprecated)config.ts status sentimentMaps render implemented / shipped (positive) and rejected (negative/muted) appropriately; render-pipeline orderings place them correctlyplan validate errors on a status="shipped" spec that lacks released-inimplemented / shipped are registered in TERMINAL_STATUSES.spec and ACHIEVING_STATUSES.spec; rejected is terminal for decision- Tests cover schema acceptance, the shipped-without-released-in error, and badge sentiment
Dependencies
- WORK-492 — adds values to the consolidated
enums.ts shape
References
- SPEC-049 — spec (New spec statuses, New ADR status)
Resolution
Completed: 2026-07-09
Branch: claude/milestone-v0-28-0-llvtfa PR: refrakt-md/refrakt#565
What was done
spec accepts implemented/shipped + released-in; decision accepts rejected. Wired into enums terminal/achieving sets, config sentiment maps, and render orderings.validate errors on shipped-without-released-in and malformed released-in.