Asset Record Phase A (v0.4.4): capabilities register with delivery lineage - #45
Merged
Merged
Conversation
…neage Implements Phase A of docs/specs/asset-record-spec.md — the per-asset Record tab, built only from delivered work: - asset_capabilities table (both dialects + migration 0015): claims with receipts — origin FKs (work item partial-unique, plan, release, all set-null) plus originSummary text that survives FK nulling; tombstone status instead of deletes - graduateWorkItem mutation: validates resolved + feature/enhancement + has asset, idempotent per work item, composes lineage from the item's first linked plan and that plan's release stamp - updateCapability / removeCapability (tombstone with reason appended to the description) - getAssetRecord query: capabilities, derived known issues (open bug/ux), debt register (open tech_debt), and graduation candidates, org-scoped - Record tab on asset detail: candidates banner with one-click graduation, capability rows with lineage chips and verification freshness dots, edit/remove dialogs, derived registers, and a struck-through Previously section for tombstones - MCP tools get_asset_record + graduate_work_item (41 tools total) - Activity feed entries for capability_graduated / capability_removed - Demo seed graduates two resolved features with full lineage (one verified, one not) and stays idempotent - 8 new tests (198 total); docs/README/app-spec/site synced; v0.4.4 Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Y7FhGxYjnJHJ7m9MpH2dgJ
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Implements Phase A of
docs/specs/asset-record-spec.md— the per-asset Record tab: a capabilities register built only from delivered work, never intent.Schema & data layer
asset_capabilitiestable (PG + SQLite, migration 0015): capability claims with receipts — origin FKs to work item (partial-unique → idempotent graduation), plan, and release (allON DELETE SET NULL) plus anoriginSummarytext lineage that survives FK nulling.statusactive/removed — removals are tombstones, never deletes.graduateWorkItem: validates resolved + feature/enhancement + has-asset; composes lineage from the item → its first linked plan → that plan's release stamp (WI: … · Plan: … · Release (version)); idempotent per work item.updateCapability/removeCapability(tombstone; reason appended to the description as**Removed:**).getAssetRecord(org-scope guarded): capabilities incl. tombstones, derived known issues (open bug/ux), debt register (open tech_debt), and graduation candidates.UI
New Record tab on asset detail: a candidates banner ("N resolved features can join this asset's record" with one-click graduation), capability rows with lineage chips + verification freshness dots + expandable markdown, edit and remove-with-reason dialogs, derived Known issues / Debt register cards, and a struck-through Previously card for tombstones.
MCP & activity
get_asset_record(read) andgraduate_work_item(write) — 41 tools total.capability_graduated/capability_removed.Seed, tests, docs
tests/lib/db/asset-record.test.ts(graduation validation/lineage/idempotency, record composition, org scope, tombstones) — 198 total, all passing; typecheck and production build clean.package.json→ 0.4.4; spec Phase A marked shipped.🤖 Generated with Claude Code
https://claude.ai/code/session_01Y7FhGxYjnJHJ7m9MpH2dgJ
Generated by Claude Code