graph-executionlisted

# Graph execution Every technical event is persisted in a new `TASK-GRAPH.md` revision before it is reported: dispatch/start, material progress, dependency changes, block/unblock, remediation, completion, lease/context changes, and newly ready nodes. Never record technical movement only in `PENDING.md`; revise pending state only for a related human action or macro outcome and backlink the new graph revision. For a first-call status or resume, follow `../../../harness/playbooks/status-resume.md` before any broad scan. `PENDING.md` owns human actions and macro incomplete areas; `TASK-GRAPH.md` owns technical order, dependencies, and execution. For user-pending questions, report human-owned items first and group human/technical pending items by workstream. Otherwise select the relevant neutral playbook: discovery-to-graph, task-dispatch, context-routing, model-routing, or parallel-execution. Load only pinned context, pending-work authority, the local graph neighborhood, task brief, scoped rules, approved capabilities, approved model-routing revision, and linked execution budget. Prefer the node's `read_set` over a broad scan, lease only its `write_set`, and use its `impact_set` for proportional regression checks. Verify derived relationships in source and record `context_provenance`; an approved, fresh Graphify index may enrich these fields but never becomes a second operational graph. Keep different workstreams in distinct execution contexts except a bounded integration node;