Fix plan status/severity vocabulary drift in MCP and renderer config

The MCP server and renderer config hard-coded their own copies of the status/severity vocabulary and have drifted from the canonical enums.ts — a regression of the drift SPEC-037 / WORK-127 fixed once. This is the quick, standalone fix that ships value before the larger consolidation work.

main View source

Criteria completion

Tracking started Jul 9 — check back for trends.

Relationships

ID:SPEC-117Status:draft

Plan status vocabulary consolidation and terminal work states

ID:SPEC-037Status:accepted

Plan Package Hardening

Version:1.0

ID:WORK-127Status:done

Fix plan schema bugs: pending status, severity mismatch, tag filtering

Priority:highComplexity:simple

ID:WORK-492Status:ready

Consolidate plan status vocabulary into a single source of truth

Priority:highComplexity:complexMilestone:v0.28.0

main current ready

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

Acceptance Criteria

mcp-bindings.ts STATUS_VALUES accepts pending (currently omitted — MCP plan.update rejects the valid pending work status)
mcp-bindings.ts SEVERITY_VALUES uses cosmetic, not trivial (currently rejects the valid cosmetic and accepts trivial, which plan validate then flags)
config.ts bug sentimentMap keys cosmetic instead of trivial
config.ts work sentimentMap includes a pending entry
Tests cover plan.update accepting pending and cosmetic via the MCP path

Approach

Point-fix the three files. This deliberately does not attempt the full single-source refactor (the follow-up consolidation work does that and makes these fixes structural rather than manual) — the aim here is to close the live bugs immediately.

References

SPEC-117 — spec (Drift-bug fixes)
SPEC-037 / WORK-127 — the earlier fix this regressed