aming-claw-hn-demo-after-worklisted

## REQUIRED FIRST READ Before any response that uses this skill, in this exact order: ListMcpResourcesTool() ReadMcpResourceTool(uri="aming-claw://current-context") ReadMcpResourceTool(uri="aming-claw://skill") ReadMcpResourceTool(uri="aming-claw://graph-first") current-context anchors project_id, governance URLs, and 3 guardrails. skill is the operating contract (Start Sequence, Observer Operating Modes). graph-first has copy-pasteable graph_query payload examples. Common failures when these are skipped: - Bootstrapping the wrong project (workspace_match auto-detected aming-claw) - Calling task_create dev/pm (V1 default is observer-led mf_parallel.v1) - Using Grep on the aming-claw codebase instead of graph_query - Fabricating trace_id strings (audit ledger is server-resolvable, will fail) - Running Execution Supervisor mode by default (Design Alignment is default) # HN Demo: After Work Show how Aming Claw keeps docs, tests, and config from becoming invisible collateral damage after code changes. ## Fear Code changes land, but related docs, tests, or config are stale, orphaned, or accepted as true without review. ## Evidence To Collect - Asset Inbox: changed, orphaned, candidate, or bound doc/test/config assets. - Binding state: accepted, candidate, orphan, unbound, or source-controlled hint state. - Baseline/Possible drift: whether related assets are known clean, suspected, or pending impact review. - Review Queue: proposal review boundary for AI or we