docs(runtime): reconcile checkpoint refs and editing surfaces

docs/ecosystem/ECOSYSTEM_AGENT_RUNTIME_CONTRACT.md

@@ -359,11 +359,13 @@ Current state:
   `cowork-service`
 - todos and checkpoint summaries now come from persisted Cowork checkpoint records
 - replay anchors now use canonical Rust audit `event_id`
+- checkpoint summaries now preserve artifact, memory, and approval refs when Cowork provides them
+- Cowork session and task IPC projections now expose canonical runtime event IDs directly
 
 Next conforming steps:
 
-1. preserve canonical event IDs anywhere approval/audit state crosses service boundaries
+1. document which Cowork transitions are direct observations versus projections derived by `cowork-service`
-2. document which Cowork transitions are direct observations versus projections derived by `cowork-service`
+2. decide whether session/task IPC should eventually expose first-class checkpoint artifact IDs in addition to refs
 
 Conformance bar:
 
@@ -392,11 +394,12 @@ Current state:
 - sessions, tasks, todos, runs, approvals, actions, and dispatch validation are exposed through the backend
 - approvals, todos, and checkpoints are now persisted as native runtime records in FlowMonk
 - run/session rollover rule: one planning workspace session exists per user, and each schedule entry becomes a new run inside that session
+- runtime todos and approvals now have direct end-user PATCH surfaces that update both the runtime record and the source task or schedule entry
 
 Next conforming steps:
 
-1. decide whether approvals and todos will eventually gain direct end-user editing surfaces or remain runtime-managed records
+1. preserve richer artifact and memory refs in checkpoint summaries once downstream runtime producers are connected
-2. preserve richer artifact and memory refs in checkpoint summaries once downstream runtime producers are connected
+2. decide whether FlowMonk should expose a richer UI for editing approvals and todos beyond the current backend surface
 
 Conformance bar:
 

docs/ecosystem/ECOSYSTEM_IMPLEMENTATION_TRACKER.md

@@ -270,12 +270,12 @@ These should be resolved before claiming the ecosystem docs are fully implementa
 
 ### 6.1 Remaining Direct Runtime TODOs
 
-- Cowork: enrich checkpoint summaries with artifact and memory refs when those runtime links are available.
+- Cowork: decide whether checkpoint summaries should grow first-class artifact IDs in addition to the new artifact and memory refs.
-- FlowMonk: decide whether runtime approvals and todos should gain direct user-managed editing surfaces or remain runtime-managed records.
+- FlowMonk: decide whether the new backend editing surfaces need dedicated product UI affordances now or can remain API-first.
 
 ### 6.2 Explicit Blockers And Questions
 
-- Question: should Cowork eventually expose canonical event IDs directly on session/task IPC projections too, or is the audit/action surface enough for the current roadmap?
+- Question: should Cowork eventually expose first-class checkpoint artifact IDs on session/task IPC projections, or are the current ref arrays enough for the current roadmap?
 
 ---
 

docs/ecosystem/PHASE5_AGENT_RUNTIME_CONTRACT_EXECUTION_PLAN.md

@@ -110,15 +110,19 @@ Observed baseline:
 - `34c9b78` Cowork persisted checkpoint IPC surface
 - `9aeb9bb` shared checkpoint schema plus cowork-service checkpoint and todo review routes
 - `86470b2` FlowMonk native runtime todo, approval, and checkpoint persistence
+- `4ff578e` Cowork checkpoint refs plus canonical session/task IPC event IDs
+- `32b46f0` cowork-service runtime mapping for enriched checkpoint refs and IPC event IDs
+- `6b1e52c` FlowMonk direct user-managed runtime todo and approval editing surfaces
 
 ## 7. Remaining Gaps
 
 - Cowork now emits shared runtime projections from cowork-service, preserves Rust-side canonical event IDs on approval/audit records, and exposes persisted checkpoint-driven todo and resume review surfaces.
-- FlowMonk now emits direct runtime projections for planning sessions, tasks, todos, runs, approvals, actions, and checkpoints with persisted native runtime records.
+- Cowork session and task IPC projections now also expose canonical event IDs directly, and checkpoint summaries preserve artifact and memory refs when present.
+- FlowMonk now emits direct runtime projections for planning sessions, tasks, todos, runs, approvals, actions, and checkpoints with persisted native runtime records plus direct PATCH editing surfaces for approvals and todos.
 - remaining follow-through is now evolutionary rather than blocking:
-  - Cowork can later expose richer checkpoint artifact and memory refs
+  - Cowork can later expose first-class checkpoint artifact IDs beyond the current ref arrays
-  - FlowMonk can later add direct user-managed editing surfaces for runtime approvals and todos if desired
+  - FlowMonk can later add richer UI affordances on top of the new backend editing surfaces
 
 ## 8. Explicit Blockers And Questions
 
-- Question: should Cowork eventually expose canonical event IDs directly on session/task IPC projections too, or is the audit/action surface enough for Phase 5?
+- Question: should Cowork eventually expose first-class checkpoint artifact IDs on session/task IPC projections, or are the current artifact/memory ref arrays enough for Phase 5?

docs/ecosystem/adoption/learning_ai_claw-cowork.md

@@ -44,6 +44,8 @@ Current runtime adoption state:
 - audit/action surfaces preserve canonical Rust `event_id`
 - approvals and action logs can participate in ActionTrail replay
 - persisted checkpoint records now back runtime todo review and runtime checkpoint summaries
+- checkpoint summaries now preserve artifact, memory, and approval refs when Cowork provides them
+- session and task IPC projections now expose canonical event IDs directly
 
 Remaining follow-up:
 
@@ -57,3 +59,4 @@ Remaining follow-up:
 
 - existing producer surface predates Phase 3 baseline
 - `34c9b78` added persisted checkpoint IPC summaries for runtime todo and resume review
+- `4ff578e` added checkpoint runtime refs plus canonical session/task IPC event IDs

docs/ecosystem/adoption/learning_ai_flowmonk.md

@@ -23,7 +23,7 @@
 - [x] persist native runtime todos, approvals, and checkpoints
 - [x] expose product-facing checkpoint summaries for planning-session resume
 - [x] document the rule for when a scheduled entry becomes a new run under an existing session
-- [ ] decide whether runtime approvals and todos need direct user-managed editing surfaces
+- [x] add runtime approvals and todos direct user-managed editing surfaces
 
 Commits:
 
@@ -31,3 +31,4 @@ Commits:
 - `1ccafa7` implemented direct runtime sessions, tasks, runs, actions, and dispatch validation
 - `faf93ec` implemented direct runtime approvals and todos
 - `86470b2` persisted native runtime todo, approval, and checkpoint records
+- `6b1e52c` added direct user-managed runtime todo and approval editing surfaces