@tablation/crew 0.59.0 → 0.61.0

package/README.md

@@ -181,6 +181,14 @@ reality: the checkouts, the tools on PATH, the agent binary, the repo's hooks,
 and whether the board answers. Nothing writes, wakes an agent or deploys until
 a route has `enabled: true`.
 
+Right after the project resolves, `crew connect` prints a capability checklist
+for the signed-in member (write the Crew and Ships tables, create Repos rows,
+mint agent keys, sync personas and skills): `ok`, or `missing — ask a workspace
+admin for <capability>`. With `--json` it is one `capabilities` event on stdout.
+Connect carries on for whatever is allowed; misses are stored in the route's
+resolved state and `crew doctor` repeats them until a re-connect finds the grant
+in place.
+
 A secondary workspace is addressed as `<primary>:<slug>`:
 `crew connect paradium:issues` (or `paradium:issues/<project>`, or
 `--workspace-id paradium:issues`) connects to it, and the route, keychain
@@ -255,6 +263,7 @@ crew inbox [--member NAME]    your tickets across every workspace
 crew connect WS[/PROJECT]     resolve a workspace/project's ids into the state tree
 crew repos add [ROUTE] [NAME] [PATH]  attach a local checkout to a route in crew.yaml, creating its Repos row if missing (--dry-run previews)
 crew repos list ROUTE         the checkouts a route has, and the tracker Repos row each matches
+crew repos hooks [ROUTE] NAME  suggest test/build hooks for a checkout (--write route|repo writes them, --json)
 crew install [--replace]     write and load this platform's scheduler unit (macOS: clears a crew installed from another path)
 crew uninstall [--all]        unload and remove it (--all: every crew launchd unit, whichever path it came from)
 ```