v0.4.2 — Version-structured history, design log & MCP release tools
Phase C of the releases-and-asset-history spec, plus the Phase-B deferrals.
- Version-structured history: shipped releases render as version tick marks in the asset History timeline, with a sticky version ladder; the asset header shows the current version.
- Asset design log (
asset_design_log): curated notes on what a change meant for an asset's design, anchored to a release and/or plan, with user/agent attribution (agent badge), expandable markdown, and an authoring side panel. - Plan-side release picker: "ships in" selector on plan detail.
- MCP: 28 → 39 tools: release lifecycle management,
get_asset_history, andrecord_design_note— whose description guides coding agents to record a design note per significantly changed asset after completing a plan. Shipped releases are rejected for mutation at the tool layer.
See docs/specs/releases-and-asset-history-spec.md (Phase C) and PR #38.