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]>
This commit is contained in:
@@ -4182,3 +4182,15 @@ Gate (Sage, scratch worktree of 64b0f9f1 plus the candidate, 12:32Z, Docker up):
|
||||
Not done yet: the brief's recorded run, in which the PM launches a coder and `mosaic agents` shows both. Filbert does it on a scratch data root against fe5c68fa. Row 41 stays in-review and #1523 stays open until then (comment 27223). Rows 57 to 61, 42 and 49 wait on row 41 done.
|
||||
|
||||
Decision 77 restart: mosaic-bus@mosaic-stack restarted at 2026-10-11T17:25:49Z on 558699bc (fe5c68fa plus the row 55 queue commit), PID 63113, "bus host up", no host refusal. The tracker didn't start: `tasks mosaic-stack startup tracker-project`. That isn't from S6. The previous process had logged `tick tracker-not-found` every 30 s since 17:19:41Z, after logging no tracker errors from 16:03:37Z. Probes at 17:26:40Z: the sync bot gets 404 and the pm bot 401 on project 32's tasks. Something on tasks.woltje.com changed at about 17:19Z. Reported to Mos with the Q53 reply. The bus needs a restart after the fix, because a `tracker-project` refusal holds until restart.
|
||||
|
||||
### 2026-10-11 — Sage, Q61a: shares read, keys re-minted, bus on #19, SetSpark and Launchpad (decision 86)
|
||||
|
||||
Before: the bus refused with `tracker-project` (project 32 deleted), the bots saw no project but #32, and #19 "Mosaic Stack" had a kanban with Jason's own buckets. After, in order, each with its record in `agents/sage/work/vikunja-setup/`:
|
||||
|
||||
- Shares (ops-01, team_projects 1-6, 18:12:52Z). `shares-read.mjs`: pm and sync each list 29 projects, with #3, #4 and #33 and their descendants (#19's children 18, 20, 21; #34 under #33). cto, coder and reviewer get 401 on `GET /projects`, by scope. The v2 list returns no permission level, so the share levels were not read back; no write was tried as a test. Record `2026-10-11_shares-read.json`.
|
||||
- Keys (`remint.mjs`, 80604260). pm key 8 adds projects create and the bucket and view writes; sync key 9 adds projects read_all. Keys 7 and 6 revoked, each answering 401. No key holds a task, project, view or bucket delete or a share route.
|
||||
- #19 board (`install-19.mjs`, pm writes, sync reads). Before-state `2026-10-11_before-19.json`: view 76, buckets 55 To-Do (0 tasks), 56 Doing (0), 57 Done (12, done), 158 Backlog (10), 159 To Do (3), 160 Pending (1), 161 In Progress (3), 162 Blocked (1). Renamed 57 to done, 159 to todo, 161 to in-progress, 162 to blocked; added 248 in-review between them; default 55 to 159, done stays 57. No task moved and none was deleted. 55, 56, 158 and 160 stay as extra buckets. Mos named To-Do and Doing for the rename; they're empty, and Jason's open work sits in To Do and In Progress, so those took the names. A first attempt (`2026-10-11_install-19-attempt1.json`) got 405 on its first write and changed nothing: v2.7.0 serves bucket and view writes under `/api/v1` only (`GET /api/v2/routes`). Record `2026-10-11_install-19.json`, problems [].
|
||||
- Bus. `.mosaic/project.json` tracker.project 32 to 19 (5628885a); restart at 18:19:28Z, PID 1242258. The first reconcile recorded 30 `task.changed.external` for vikunja:19/* and `task.missing` (not-found) for vikunja:32/144. No tasks line in the journal through 18:22:15Z, about five ticks, and no snapshot after the reconcile. Startup errors do reach the journal (17:25:50Z `startup tracker-project`), so the silence is a pass.
|
||||
- Projects (`create-33.mjs`). #35 SetSpark and #36 Launchpad under #33, no tasks, read back by the sync key through the #33 share. Vikunja gave each its default views and buckets; they are watch-only children and nobody touches them.
|
||||
|
||||
Rollback: renames back to the before-state titles and default back to 55 (pm can do both); bucket 248 and projects 35 and 36 need Jason or ops-01 to delete, or the pm archives the projects; project.json revert plus restart; shares are ops-01's DELETE of ids 1-6; keys can't be restored, only re-minted. Rows 62 and 63 carry the multi-project adapter work.
|
||||
|
||||
Reference in New Issue
Block a user