Tianyi Cui
2faeabb05a
Name the runnable leaf for the line-oriented front door it owns, matching the existing tui-agent and acp-agent organization. Move the complete config, Code Mode overlay, tests, metadata, and generated composition graph together, then update every loader path and repository reference. Keep the shared model identity independent of its terminal front door by phrasing the persona as a coding-agent role rather than retaining the retired leaf name. Regenerate graph and tool catalogs and re-record each affected bilingual pair so derived documentation cannot point at the removed path.
1.9 KiB
1.9 KiB
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 / services catalogs, tool-catalog.md, and core-data-structures/.
The process decision behind this index is recorded in the documentation graph RFC.
| Graph | Mode |
|---|---|
| module dependency graph | generated |
| tool schema catalog and package map | generated |
| capability seams and core services | hybrid generated |
| echo-agent app composition | hybrid generated |
| repl-agent app composition | hybrid generated |
| tui-agent app composition | hybrid generated |
| cordis-agent app composition | hybrid generated |
| acp-agent app composition | hybrid generated |
| event producer/consumer matrix | hybrid generated |
| agent turn and step lifecycle | curated |
| tool execution pipeline | curated |
| ACP snapshot replay | 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.