CodeNomad/docs/help/site.json
Pascal André b1e1618b6b
feat(missions): explain every playbook in help and a See details reader (#1226)
Playbooks were opaque: the Mission editor showed one sentence per playbook,
and nothing told users which steps and roles a playbook runs, when they are
asked something, what CodeNomad actually enforces, or which instructions
the agents receive.

A new help page, playbooks.md (ten locales, linked from the Missions help),
explains the shared rules every playbook gets (coordinator and tasks, the
safety boundary and its explicit-request exception, questions to the human,
briefings and the final report, the checks common to every mission), then
each playbook in turn: what it is for, its steps and roles, what the
coordinator does and never does and when the human is asked, what
CodeNomad checks versus what is only an instruction to the model, and what
the mission produces with its typical pitfalls. Every statement was checked
against the recipes and the server checks; decision tags and the
Coordinator decision / Your answer labels are scoped to Native subagents.

"See details" under the playbook description in the editor's Options opens
a read-only view in the Mission reader, beside the editor: steps, roles
with their localized labels, and, folded per recipient, the complete
English texts each agent receives. They come from a new read-only route,
GET /api/missions/playbooks?taskMode=, built by missionPlaybookDetails()
from the real prompt builders (buildAssignmentPrompt, buildActorContext)
with placeholders, so the view cannot drift from what agents get. The
button is disabled while a creation request is in flight and opening the
reader no longer cancels the editor's pending creation. A failed load
offers Retry, and a saved playbook reader is restored, with unknown ids
dropped.

Tests: a drift guard comparing whole sent texts with the export for native
and independent assignments, independent session context, and one-time and
daily coordinators of every playbook, with a negative check and a test
placing each question/safety rule on the right recipients; a route test;
browser tests for See details (including a delayed response) and for
opening it during a creation answered 200 and 400; view-state restoration.
Server, UI unit, mission browser, help structure and help browser tests and
the typechecks pass.
2026-10-31 04:50:52 +01:00

13 lines
766 B
JSON

{
"locales": ["en", "fr", "de", "es", "he", "ja", "ne", "ru", "tr", "zh-Hans"],
"sections": [
{ "id": "start", "pages": ["index", "download", "install", "server"] },
{ "id": "workflows", "pages": ["projects", "conversations", "history", "files", "permissions", "missions", "playbooks"] },
{ "id": "opencode-setup", "pages": ["opencode", "providers", "integrations"] },
{ "id": "remote-access", "pages": ["remote-control", "remote-access", "security", "mobile"] },
{ "id": "customize", "pages": ["settings", "shortcuts", "voice"] },
{ "id": "extensions", "pages": ["extensions"] },
{ "id": "desktop", "pages": ["desktop", "browser-sidecars", "updates"] },
{ "id": "help", "pages": ["troubleshooting", "support", "sponsor"] }
]
}