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

package/README.md

@@ -162,6 +162,33 @@ defines these public command families:
 
 Use `/help` in the TUI for command availability in the current build.
 
+### Duo collaboration (development branch)
+
+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.
+
+### Lightweight peer development and review
+
+Select an explicit developer model with `/model`, then start a pair:
+
+```text
+/buddy --peer-review --reviewer-model <reviewer-model-id> <development goal>
+```
+
+The developer and reviewer keep separate contexts and use the existing Team
+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.
+
+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
+[usage and limitations](docs/peer-development-review.md).
+
 ## Models And Routing
 
 CCL accepts model aliases such as `sonnet` or `opus` and gateway model names such