@margay/ccl-core 1.4.0-beta.0 → 1.4.5-rc.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +32 -0
- package/dist/cli.js +17309 -13121
- package/dist/sdk/errorDiagnostics.d.ts +82 -0
- package/dist/sdk/errorDiagnostics.js +140 -4
- package/dist/sdk/index.d.ts +1 -0
- package/dist/sdk/query.js +19 -2
- package/dist/sdk/types.d.ts +11 -1
- package/docs/ccl-duo-agent.md +132 -0
- package/docs/ccl-ide-usage.md +75 -0
- package/docs/dev-quickstart.md +105 -0
- package/docs/gateway-quickstart.md +122 -0
- package/docs/index.md +98 -0
- package/docs/peer-development-review.md +60 -0
- package/package.json +10 -2
- package/sdk/API.md +374 -0
- package/sdk/README.md +132 -0
package/README.md
CHANGED
|
@@ -162,6 +162,38 @@ defines these public command families:
|
|
|
162
162
|
|
|
163
163
|
Use `/help` in the TUI for command availability in the current build.
|
|
164
164
|
|
|
165
|
+
### Duo collaboration (reviewed local candidate)
|
|
166
|
+
|
|
167
|
+
Use `/duo-agent` (alias `/duo`) to enter standby, then provide a task. The
|
|
168
|
+
reviewed candidate resolves Auto execution and critic roles to two distinct
|
|
169
|
+
concrete models. `/model` and `/duo --reviewer-model <fixed-model-id>` can
|
|
170
|
+
override a role. Completion requires actual requests from both models, a
|
|
171
|
+
current review and executor acceptance; accepted tasks return to standby for
|
|
172
|
+
the next task, and `/duo exit` releases input even if cleanup fails. See the
|
|
173
|
+
[Duo guide](docs/ccl-duo-agent.md). This candidate is not yet on npm `next`;
|
|
174
|
+
RC8/RC10/C790 release acceptance remains on HOLD.
|
|
175
|
+
|
|
176
|
+
### Lightweight peer development and review
|
|
177
|
+
|
|
178
|
+
Select an explicit developer model with `/model`, then start a pair:
|
|
179
|
+
|
|
180
|
+
```text
|
|
181
|
+
/buddy --peer-review --reviewer-model <reviewer-model-id> <development goal>
|
|
182
|
+
```
|
|
183
|
+
|
|
184
|
+
The developer and reviewer keep separate contexts and use the existing Team
|
|
185
|
+
messages. The reviewer tests an independent copy of each submission; only its
|
|
186
|
+
approval of the current content completes the protected task. Disagreements,
|
|
187
|
+
cancellation and exhausted limits remain unfinished. Both models are fixed for
|
|
188
|
+
the pair; automatic routing aliases are rejected. Ordinary `/buddy` and Team
|
|
189
|
+
usage remain available. Ordinary `/buddy` first creates or reuses a Team, then
|
|
190
|
+
starts Agent with the team name actually returned by TeamCreate. Its prompt
|
|
191
|
+
alone does not prove the teammate started.
|
|
192
|
+
|
|
193
|
+
The current mode requires a Git working directory and runs in one CCL interface.
|
|
194
|
+
Copies isolate normal test output, not hostile same-user shell commands. See
|
|
195
|
+
[usage and limitations](docs/peer-development-review.md).
|
|
196
|
+
|
|
165
197
|
## Models And Routing
|
|
166
198
|
|
|
167
199
|
CCL accepts model aliases such as `sonnet` or `opus` and gateway model names such
|