The plan for Mos's A4 window: stopped-bus backup with sha256, rehearsal on
disposable copies, live migration with migrate-schema.mjs, NEW units and
wrapper, verify-new.sh and check-launch.mjs for the NEW copy (read_spec now
required), and restore steps A and B. Nine scripts committed with
SCRIPTS.sha256 so Mos can check the scratch copies before running. Not run.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
Row 145 BUILD.md records both review rounds, the gate on 9357baac9
(GATE_PASSED, 24 steps) and the landed commits 92938ab43..fba879f6a.
q167/ holds the issue receipts for rows 135-143 and 146-147.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
The update was stamped 19:10Z by estimate. Commit f365a1da9 that
carries it is 19:07:47Z, so the stamp becomes 19:07Z.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
SESSIONS: Darkwing 18:54:54Z and its 18:56:04Z correction, Dewey
19:00:29Z, Sage's landing line. The schema window plan records row 121
landed 2c16d6b93, a rehearsal of the migration on a copy of the backup
(row 121 gate condition 4), and a role_claims check for an open assistant
claim. P19 task 311 holds row 121's follow-ups (sage-0369).
Co-Authored-By: Claude Opus 5.5 <[email protected]>
Darkwing's row 121 round 2 gate left 201 mosaic-business-* directories.
Filed as a follow-up, not in row 121.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
Researcher's round 1 patch applied unchanged on 73fa83a08. Only
packages/bus/src/broker.mjs differs from the approved manifest, because
row 133 (a622f426c) landed on it. Full landing gate passed, 24 suites.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
F1: the scripts/mosaic header names mosaic-old. Both doc-only follow-ups
are done too, plus the test comment wording. Same base, same 4 files.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
Candidate 1126314bd522de838aad03689bed41f6b12a33c2d7f30b2eff1b38653f559ae0,
4 files on 48b893871. The first gate stopped at script-queue: the pre-A2
fixture check pinned the old header comment. The check now skips comment
lines (brief amended in 06e964026). Second gate: 24 suites, 0 failed.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
The window plan records row 49 landed and row 121's round 1 changes, and
adds Darkwing's 28587 note 2: the first start reads every comment list.
Task 304 is Darkwing's note 1, push a task's comment cursor only when
consider runs for it.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
The window plan records Filbert's row 49 note 2 (28579): land-work refuses
the live 3b bus from the row 49 landing until Mos migrates. Task 300 is
note 1, the duplicate comment cursor in one pass. Task 299 is row 123's
consume follow-up (28578). Also the row 121 and 131 filing script and
its record.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
The launch line's manifest field is a path, so l.manifest.typed threw a
TypeError in the 2026-10-15 window. Mos caught it.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
Darkwing asked how land-work reads the decision. The Console's path is
human-only (human-cli refuses agent environments, #225), so the
conductor can't use it. land-work now opens bus.sqlite readOnly, runs
SELECTs only and refuses bus-schema on a digest mismatch. The brief
records what f71c73c9 holds: task_ref is null, the raise's target and
approvalChoice give the branch and the merge option, and the work ref
comes from the question. agents/sage/work/row116/live-rows.json holds
the live rows for the replay fixtures.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
Mos sage-0088, fact-finding only. Filed with Sage's own key (user 13)
and read back with the sync key.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
Mos sage-0086: bot-mosaic-stack-sage is user 13 with key 13 and
bot-mosaic-stack-ops-01 is user 14 with key 14, both with key 11's
scopes (Q61a cut). Neither reads a project until ops-01 adds them to
team 1 under Mos's go.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
mint-bot.mjs generalizes mint-mos.mjs (user, name and key title as
arguments; slot written without a trailing newline). bot-launchpad-pm is
user 12, key 12, scopes identical to key 11 (Q61a cut). The key reads no
project until ops-01 adds user 12 to team 1.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
tick-62.mjs runs the candidate's discover(), reconcile() and tick()
against tasks.woltje.com with the sync key, a real Store and Broker in a
scratch root, and a fetch guard that refuses anything but GET. The
startup scope probes are not sent. Reconcile 15 GETs, 42 snapshots; tick
8 GETs, 0 snapshots; 18, 20 and 21 watch-only. A missing view id on #18
answers 404 code 3014 while #18 reads 200 (the fake says 13001).
Co-Authored-By: Claude Opus 5.5 <[email protected]>
Mos amended ruling (2): with no environment location for
MOSAIC_LEASE_VERSION_PROBE_COMMAND, the wrapper sends only
`__lease-capability` to ~/.npm-global/bin/mosaic-old, so the old CLI's
lease gate still gets its answer. Every other subcommand reaches the
pinned worktree; undo removes the forward with the wrapper. update now
rewrites the wrapper, and status flags a wrapper that differs from what
the script writes. Checked live at 21:17:58Z: the probe answered
{"name":"lease-runtime-activation","version":1}, exit 0.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
agents/sage/work/q81/mosaic-cli.sh does install, update, undo and status.
~/.npm-global/bin/mosaic is now a wrapper that execs scripts/mosaic in a
detached worktree at ~/.local/share/mosaic-cli/stack, pinned to pushed
ee129aa6. The estate CLI symlink was renamed in place to mosaic-old.
Only commits on origin/refactor can be pinned. `mosaic queue` refuses
from the worktree (the queue runs only in the canonical checkout), so
queue work stays on scripts/mosaic. status flags a wrapper replaced by
`npm i -g --force`.
lease-gate-notes.md: no single environment location for
MOSAIC_LEASE_VERSION_PROBE_COMMAND exists outside fleet state, so the
old-path lease gate fails closed, as Mos ruled for that case.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
Jason: "Q80: Have the PM decide. Then fix". project-manager decided to
delete all four and moved their tasks to todo. Mos ruled no standing
delete scope on any bot key. svc-mosaic-stack minted key 10 for the pm
user with only projects.views_buckets_delete and a 30-minute expiry,
held in memory only. The pre-read showed all four buckets empty. Four
DELETEs answered 200, and key 10 was revoked (204) at once. The pm user
now lists only key 8. The read-back shows buckets 57 done, 159 todo
(default), 161 in-progress, 248 in-review and 162 blocked, with task
counts unchanged.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
GETs only, sync key 9. Project list 200, total 30 (31 with archived #15).
#18, #20 and #21 have parent 19, none archived. GET /tasks with
filter project in 19, 18, 20, 21: 200, 42 tasks across all four. The
per-project open reads give 18, 4, 3 and 1. A follow-up row moves a tick
to the single read after row 62 is done.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
install-19.mjs renames 57 done, 159 todo, 161 in-progress, 162 blocked,
adds 248 in-review and moves the default to 159; no task moved. Writes go
to /api/v1 (v2.7.0 405s bucket writes under /api/v2). create-33.mjs adds
#35 and #36 under #33. Records hold no secret; shares-read titles removed.
Co-Authored-By: Claude Opus 5.5 <[email protected]>