Add spec implemented/shipped and ADR rejected statuses

Close the "is it built / is it available?" gap on specs, and give ADRs an honest "considered and declined" state. Rides on the consolidated vocabulary from WORK-492.

main View source

Criteria completion

Tracking started Jul 9 — check back for trends.

Relationships

ID:SPEC-049Status:draft

Spec lifecycle and PR linkage

ID:WORK-492Status:ready

Consolidate plan status vocabulary into a single source of truth

Priority:highComplexity:complexMilestone:v0.28.0

ID:WORK-497Status:draft

plan status PR rollups and implemented-flip suggestion

Priority:mediumComplexity:moderateMilestone:v0.28.0

ID:WORK-499Status:draft

CLAUDE.md pr checklist bullet and spec-lifecycle docs

Priority:mediumComplexity:simpleMilestone:v0.28.0

main current draft

claude/plan-runes-status-vocab-jcq1tx draft claude/milestone-v0-28-0-llvtfa done main draft

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 correctly
plan validate errors on a status="shipped" spec that lacks released-in
implemented / 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)