@margay/ccl-core 1.4.1-beta-duo.0 → 1.4.5-rc.0

package/README.md

@@ -162,13 +162,16 @@ defines these public command families:
 
 Use `/help` in the TUI for command availability in the current build.
 
-### Duo collaboration (development branch)
+### Duo collaboration (reviewed local candidate)
 
-Use `/duo-agent` (alias `/duo`) to enter standby, then configure
-`/duo --reviewer-model <fixed-model-id>` and provide a task. Duo supports code,
-plans and documents, with independent review, executor counter-review and user
-pause/resume controls. See the [Duo guide](docs/ccl-duo-agent.md) for examples.
-Runtime acceptance is in progress; the installed CLI has not been updated.
+Use `/duo-agent` (alias `/duo`) to enter standby, then provide a task. The
+reviewed candidate resolves Auto execution and critic roles to two distinct
+concrete models. `/model` and `/duo --reviewer-model <fixed-model-id>` can
+override a role. Completion requires actual requests from both models, a
+current review and executor acceptance; accepted tasks return to standby for
+the next task, and `/duo exit` releases input even if cleanup fails. See the
+[Duo guide](docs/ccl-duo-agent.md). This candidate is not yet on npm `next`;
+RC8/RC10/C790 release acceptance remains on HOLD.
 
 ### Lightweight peer development and review
 
@@ -183,7 +186,9 @@ messages. The reviewer tests an independent copy of each submission; only its
 approval of the current content completes the protected task. Disagreements,
 cancellation and exhausted limits remain unfinished. Both models are fixed for
 the pair; automatic routing aliases are rejected. Ordinary `/buddy` and Team
-usage remain available.
+usage remain available. Ordinary `/buddy` first creates or reuses a Team, then
+starts Agent with the team name actually returned by TeamCreate. Its prompt
+alone does not prove the teammate started.
 
 The current mode requires a Git working directory and runs in one CCL interface.
 Copies isolate normal test output, not hostile same-user shell commands. See