@tablation/crew 0.57.0 → 0.59.0

package/README.md

@@ -71,7 +71,11 @@ demand. `crew agents sync [route]` pushes both personas and skills in one
 run — "agents" here means every agent-shaped resource crew owns, not just
 the Agents table; `crew skills sync [route]` is the same create/update/
 diverged sync narrowed to skills alone, for when you've only touched
-`skills/`. Example use — a Pair session invoked via an Epic's
+`skills/`. `crew connect` runs this same sync (then the seat key mint) at the
+end for an admin key, so a fresh workspace needs no second command; a member
+key links seats to the existing rows and is told an admin has to run it once.
+`--no-agents-sync` skips it, and `--json` adds `agents_synced` and `seat_key`
+events on stdout. Example use — a Pair session invoked via an Epic's
 `grill_link` looks up the `Grill-Me` skill through the Tablation MCP tool
 `agent_skills_controller_get_skill` and follows it. `prompts/default/skills/
 grill-me.md` is one shipped example; the rest are the building lanes'
@@ -239,6 +243,7 @@ crew watch [route]             live view of what the crew is doing
 crew status [route]            paused/running state, led by what the operator owes (needs_info assigned to them, needs_planning, ships needing attention)
 crew doctor [route] [--fix]    preflight; --fix enables clean routes, offers crew install
 crew selftest [route] [--toolchain NAME] [--json]   launch each toolchain as a run would and prove it reaches the tracker
+crew sample-ticket [route] [--remove] [--dry-run] [--json]   file one ticket on a throwaway repo that walks the dev, QA and release loop
 crew ports [route]             which checkout owns which ports, and what is up
 crew reap [route]              kill servers left behind by removed worktrees
 crew drop [route] NNN          remove a merged ticket's worktree and branch