@tablation/crew 0.60.0 → 0.61.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 +8 -0
- package/dist/cli.js +441 -211
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -181,6 +181,14 @@ reality: the checkouts, the tools on PATH, the agent binary, the repo's hooks,
|
|
|
181
181
|
and whether the board answers. Nothing writes, wakes an agent or deploys until
|
|
182
182
|
a route has `enabled: true`.
|
|
183
183
|
|
|
184
|
+
Right after the project resolves, `crew connect` prints a capability checklist
|
|
185
|
+
for the signed-in member (write the Crew and Ships tables, create Repos rows,
|
|
186
|
+
mint agent keys, sync personas and skills): `ok`, or `missing — ask a workspace
|
|
187
|
+
admin for <capability>`. With `--json` it is one `capabilities` event on stdout.
|
|
188
|
+
Connect carries on for whatever is allowed; misses are stored in the route's
|
|
189
|
+
resolved state and `crew doctor` repeats them until a re-connect finds the grant
|
|
190
|
+
in place.
|
|
191
|
+
|
|
184
192
|
A secondary workspace is addressed as `<primary>:<slug>`:
|
|
185
193
|
`crew connect paradium:issues` (or `paradium:issues/<project>`, or
|
|
186
194
|
`--workspace-id paradium:issues`) connects to it, and the route, keychain
|