docs: mosaic on PATH can be the pinned copy wrapper (row 70, #1564)
Sage's row 70 round 2 candidate (agents/sage/work/queue-70/r2, manifest
098b9aef...604e), approved by Filbert in comment 28602. Landing gate on
4a34fb0d6 with rows 133 and 70 applied: all 24 suites passed, 0 failed.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
This commit is contained in:
1 parent
a622f426c0
commit
73fa83a08b
4 files changed
+34
-12
No files matched your search
+11
-4
@@ -171,10 +171,17 @@ leaves one registration record at `<dataRoot>/seats/<layout>/<seat>/registration
|
||||
that the control board reads: seat, project, task, workspace, tmux session,
|
||||
harness, start time, pid. Rewritten on every launch. `seat task` changes the
|
||||
task field only. The four repository seats (`agents/*/launch.sh`) register
|
||||
themselves through this path unless called with `--check`. Not the
|
||||
npm-global `mosaic` CLI; run by path. Exit codes: the launch script's own
|
||||
once it runs; before that 1 could not start, 2 invalid config or seat, 4
|
||||
usage. Details and the record's fields: `packages/seat/README.md`.
|
||||
themselves through this path unless called with `--check`. Run it by
|
||||
path from the checkout. On a pinned host, `mosaic` on PATH is a wrapper
|
||||
around a pinned copy's `scripts/mosaic`
|
||||
([Stack copies](#stack-copies-scriptsstack-copysh)) and carries the human
|
||||
commands; on Jason's host the estate CLI it replaced is `mosaic-old`.
|
||||
Queue commands stay on `scripts/mosaic queue` in the canonical checkout,
|
||||
because a copy refuses them ([One pinned
|
||||
copy](../packages/cli/README.md#one-pinned-copy-row-85-1579)). Exit
|
||||
codes: the launch script's own once it runs; before that 1 could not
|
||||
start, 2 invalid config or seat, 4 usage. Details and the record's
|
||||
fields: `packages/seat/README.md`.
|
||||
|
||||
## Work queue (`scripts/mosaic queue`)
|
||||
|
||||
|
||||
Reference in new issue
Block a user