workgraph-workflowlisted

# WorkGraph Workflow Use WorkGraph when work must survive sessions, compaction, restarts, schedules, or coordination between agents. It is the shared commitment graph, not private scratch space and not semantic memory. ## Operating Rules - Use `workgraph_create` for a new durable commitment. Keep related work in the same namespace; omitted namespace means `default`. - Use `workgraph_ready` to find eligible work. Do not infer readiness from item fields, blocker counts, due times, or edges yourself. - Claim an item before doing durable or shared work with `workgraph_claim`. Include your typed owner and the current `expected_revision`. Choose either `lease_seconds` or `lease_expires_at`, never both. - If a write fails with a stale revision, reload the item with `workgraph_get` or `workgraph_snapshot`, reconsider the current state, then retry only if the work still makes sense. - Every successful mutation advances the item revision. Use the returned item, not an older cached revision, for the next claim, update, evidence, release, block, or close operation. - Use `workgraph_link` for real dependencies and relationships. Use `blocks` only when the target should not be ready until the source is terminally resolved. - Attach evidence with `workgraph_add_evidence` for artifacts, PRs, logs, summaries, external tickets, or other proof that the work changed state. - Close with `workgraph_close` only when terminal truth exists. Use `completed`, `failed`, or `ca