docs(runtime): record FlowMonk runtime drill-in
This commit is contained in:
parent
e3f72fa22d
commit
1addccfeb5
@ -270,11 +270,11 @@ These should be resolved before claiming the ecosystem docs are fully implementa
|
||||
|
||||
### 6.1 Remaining Direct Runtime TODOs
|
||||
|
||||
- FlowMonk: decide whether the next runtime UI slice should prioritize run/action drill-in or resume controls.
|
||||
- FlowMonk: decide whether the next runtime UI slice should prioritize checkpoint resume guidance or replay affordances.
|
||||
|
||||
### 6.2 Explicit Blockers And Questions
|
||||
|
||||
- Question: should FlowMonk runtime UX go deeper on replay/action visibility next, or on checkpoint resume guidance?
|
||||
- Question: should FlowMonk runtime UX go deeper on checkpoint resume guidance next, or on replay affordances?
|
||||
|
||||
---
|
||||
|
||||
|
||||
@ -114,15 +114,16 @@ Observed baseline:
|
||||
- `32b46f0` cowork-service runtime mapping for enriched checkpoint refs and IPC event IDs
|
||||
- `6b1e52c` FlowMonk direct user-managed runtime todo and approval editing surfaces
|
||||
- `da2db8e` FlowMonk dedicated runtime review web UI
|
||||
- `19fd4e1` FlowMonk runtime run and action drill-in
|
||||
|
||||
## 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.
|
||||
- Cowork session and task IPC projections now also expose canonical event IDs directly, and checkpoint summaries preserve artifact IDs plus 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, direct PATCH editing surfaces, and a dedicated runtime review web UI for approvals, todos, and checkpoints.
|
||||
- FlowMonk now emits direct runtime projections for planning sessions, tasks, todos, runs, approvals, actions, and checkpoints with persisted native runtime records, direct PATCH editing surfaces, and a dedicated runtime review web UI for approvals, todos, checkpoints, runs, and recent actions.
|
||||
- remaining follow-through is now evolutionary rather than blocking:
|
||||
- FlowMonk can later deepen the runtime view with run/action drill-in if needed
|
||||
- FlowMonk can later add stronger checkpoint resume guidance or replay affordances if needed
|
||||
|
||||
## 8. Explicit Blockers And Questions
|
||||
|
||||
- Question: should the next FlowMonk runtime slice focus on run/action drill-in or checkpoint resume controls?
|
||||
- Question: should the next FlowMonk runtime slice focus on checkpoint resume guidance or replay affordances?
|
||||
|
||||
@ -25,6 +25,7 @@
|
||||
- [x] document the rule for when a scheduled entry becomes a new run under an existing session
|
||||
- [x] add runtime approvals and todos direct user-managed editing surfaces
|
||||
- [x] add a dedicated runtime review UI for approvals, todos, and checkpoints
|
||||
- [x] add runtime run and action drill-in inside the review UI
|
||||
|
||||
Commits:
|
||||
|
||||
@ -34,3 +35,4 @@ Commits:
|
||||
- `86470b2` persisted native runtime todo, approval, and checkpoint records
|
||||
- `6b1e52c` added direct user-managed runtime todo and approval editing surfaces
|
||||
- `da2db8e` added the FlowMonk runtime review web UI
|
||||
- `19fd4e1` added FlowMonk runtime run and action drill-in
|
||||
|
||||
Loading…
Reference in New Issue
Block a user