Skip to content

v0.4.4 — Asset Record Phase A: the capabilities register

Choose a tag to compare

View all tags
@github-actions github-actions released this 04 Aug 16:45
v0.4.4
7000204
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Phase A of the Asset Record spec: every asset now carries a Record — a register of what it actually does today, built only from delivered work.

Highlights

  • Record tab on asset detail — capabilities with delivery lineage chips (work item → plan → release version), verification freshness dots, expandable markdown descriptions, and derived Known issues / Debt register sections
  • Graduation — resolved feature/enhancement work items graduate into the record with one click (a candidates banner surfaces them); graduation is idempotent and carries full lineage receipts
  • Tombstones, not deletes — removing a capability moves it to a struck-through Previously section with a reason; "used to do X" is record too
  • asset_capabilities table (PG + SQLite) — origin FKs are SET NULL on delete, but the originSummary text lineage survives
  • 2 new MCP tools — get_asset_record and graduate_work_item (41 tools total), so coding agents can read an asset's current-state record and keep it complete
  • Demo seed — graduates two resolved features with full lineage (one verified, one not)
  • 8 new tests (198 total)

Next up (v0.4.5): agent-driven reconciliation proposals — the record verified against the code it describes.

Assets 2
Loading