docs(ecosystem): reconcile runtime tracker follow-ups

docs/ecosystem/ECOSYSTEM_IMPLEMENTATION_TRACKER.md

@@ -221,7 +221,7 @@ These should be resolved before claiming the ecosystem docs are fully implementa
   - `3f2482b`
 - [x] add first runtime projection + dispatch validation API in `platform-service`
       Commits:
-  - `TBD`
+  - `fe36296`
     Status note:
   - `GET /api/agent-runtime/sessions` projects platform sessions into the shared `AgentSession` shape
   - `GET /api/agent-runtime/runs` projects platform runs into the shared `AgentRun` shape
@@ -230,6 +230,13 @@ These should be resolved before claiming the ecosystem docs are fully implementa
       Status note:
   - FlowMonk runtime-emitter implementation work was started, but this clone cannot currently verify it because the repo depends on a local npm registry at `http://localhost:3300` and backend dependencies are not installed
 
+### 6.1 Remaining Direct Runtime TODOs
+
+- Cowork: emit canonical `AgentSession`, `AgentTask`, `AgentRun`, and `AgentApprovalCheckpoint` objects from live task orchestration.
+- Cowork: attach canonical event IDs to approval and audit trails so ActionTrail lineage can stop using fallback/null semantics.
+- FlowMonk: finish direct runtime-emitter integration once the local npm registry and backend dependencies are available again.
+- Platform-service: refine the `queued -> paused` projection fallback once run-vs-session semantics are finalized.
+
 ---
 
 ## 7. Active Execution Plan

docs/ecosystem/PHASE5_AGENT_RUNTIME_CONTRACT_EXECUTION_PLAN.md

@@ -76,7 +76,7 @@ Observed baseline:
 ## 6. Commits
 
 - `3f2482b` runtime contract schema baseline
-- `TBD` platform-service runtime projection + dispatch validation
+- `fe36296` platform-service runtime projection + dispatch validation
 
 ## 7. Remaining Gaps