Plan mode's stage 2 (RFC 2026-07-07-plan-mode). The exit tool: one required plan argument (the durable log artifact), execute re-checks the folded mode, then conducts the review over the user-interaction seam — one single-select question (Approve / Keep planning) with free text open — so an approval appends mode/set back to default in-turn and every other outcome (keep-planning feedback verbatim, aborted, no provider) returns the corrective isError with the mode unchanged. presentCall is a generic card titled by the plan's first heading carrying the plan markdown; over ACP the review rides the ask_user elicitation flow, in the terminal the stdio prompt queue — no approval-seam dependency. The ACP bridge maps the picker 1:1 onto ctx.modes (opportunistic, a type-only peer edge): session/new + session/load advertise availableModes/currentModeId, session/set_mode validates through set() and echoes an optimistic current_mode_update (the pending mode IS the selection; the logged mode/set lands at the boundary and, matching, is not re-sent), and a session/event listener re-notifies on each logged flip that differs from the last sent — the tool-driven exit updates the picker. The feature matrix rows move from 'not modeled' to the picker-to-modes / knobs-to-config-options division, with the ACP v2 removal direction recorded as a mechanical-migration risk. The snapshot harness gains the setMode/setModeExpectError ops and a scripted elicitationAnswers FIFO (cancel on exhaustion; a stray choice string reaches the agent verbatim as a non-consenting custom answer, so a scenario bug fails safe). The suite factory's header-pin requirement now applies only to model-turn scenarios — a protocol-only suite has no header content to anchor. examples/plan-acp-agent is the live composition; its keyless modes-advertise scenario pins the wire surface (advertisement, both set_mode round-trips, unknown-id rejection). The recorded plan-mode approve/reject arc awaits a with-key recording session; its texts are pinned at the unit tier meanwhile. examples/AGENTS.md ceiling 653 → 680: the new example's required smoke row does not fit the old budget.
28 lines
1.9 KiB
Markdown
28 lines
1.9 KiB
Markdown
<!-- Generated by scripts/gen-doc-graphs.ts - do not edit by hand.
|
|
Run `pnpm run gen-doc-graphs` to regenerate. -->
|
|
|
|
# Documentation Graph Index
|
|
|
|
These diagrams are the relationship layer above the generated catalogs. Use them to navigate package topology, capability seams, event flow, model-facing tools, app composition, and runtime lifecycle paths. Exact signatures and type shapes still live in the generated [events](cordis-catalog/events.md) / [services](cordis-catalog/services.md) catalogs, [tool-catalog.md](tool-catalog.md), and [core-data-structures/](core-data-structures/core.md).
|
|
|
|
The process decision behind this index is recorded in [the documentation graph RFC](rfc/implemented/process/2026-07-03-documentation-graph-atlas.md).
|
|
|
|
| Graph | Mode |
|
|
| --- | --- |
|
|
| [module dependency graph](module-graph.md) | `generated` |
|
|
| [tool schema catalog and package map](tool-catalog.md) | `generated` |
|
|
| [capability seams and core services](capability-seams.md) | `hybrid generated` |
|
|
| [echo-agent app composition](../examples/echo-agent/composition.md) | `hybrid generated` |
|
|
| [coding-agent app composition](../examples/coding-agent/composition.md) | `hybrid generated` |
|
|
| [cordis-agent app composition](../examples/cordis-agent/composition.md) | `hybrid generated` |
|
|
| [acp-agent app composition](../examples/acp-agent/composition.md) | `hybrid generated` |
|
|
| [../examples/plan-acp-agent/composition.md](../examples/plan-acp-agent/composition.md) | `generated` |
|
|
| [event producer/consumer matrix](event-producer-consumer.md) | `hybrid generated` |
|
|
| [agent turn and step lifecycle](agent-lifecycle.md) | `curated` |
|
|
| [tool execution pipeline](tool-execution-pipeline.md) | `curated` |
|
|
| [ACP snapshot replay](../packages/ui/acp/snapshot-replay.md) | `curated` |
|
|
|
|
Regenerate with `pnpm run gen-doc-graphs`; verify freshness with `pnpm run verify-doc-graphs`.
|
|
|
|
Maintenance mode: mixed: each linked page declares generated, hybrid, or curated mode.
|