${x}
`).join("") + `${SIG}
`; +const TASKS = [ + { title: "I1 brief: containerize managed sessions by role (decisions 105-108)", due: DUE, + description: p("Sage writes the I1 brief on BRIEF-TEMPLATE.md from agents/sage/work/next-target/I1-review.md: two broker sockets with the human one only in the Console, a new via value in authenticateHuman, narrow per-run mounts, cap_drop ALL and limits, an internal network with one egress proxy, the rootless endpoint pinned with a refusal unless docker info lists name=rootless, and the subscription token as a read-only file secret. The survey's unverified items go in as spikes with tests. Owner Sage.") }, + { title: "M1 brief and queue row: chief-of-staff role (decision 104)", due: DUE, + description: p("Move agents/sage/work/next-target/M1-draft.md to docs/plans on BRIEF-TEMPLATE.md and open its queue row: owner Rocko, reviewers Darkwing and Filbert, gate Sage. The row ships roles/chief-of-staff.json and .md, fixture tests in packages/business/tests and the documented instance entry; it never writes Jason's business file. The instance name is #150. Owner Sage.") }, + { title: "Row 77 brief: Console service hardening (#1571)", due: DUE, + description: p("Write the brief for queue row 77 (Gitea #1571, owner Rocko), held until after the cutover, which is done (#152). Coordinate with #146 and #147, since all three change how the mosaic-webui unit runs. Owner Sage.") }, + { title: "Narrow the pi worker's dataRoot mount (compose.yaml:40)", + description: p("compose.yaml:40 mounts the whole dataRoot read-write into the pi worker as uid 1000, which includes bus/broker.sock. Narrow it to the worker's own run and workspace paths. This exposure exists today and doesn't wait on I1. Found in Sage's I1 review. Needs a queue row and brief.") }, + { title: "Stale docs: LAYERS.md L4 and CONDUCTOR.md lines 17 and 40", + description: p("LAYERS.md L4 and docs/plans/CONDUCTOR.md:17,40 say managed sessions run in containers. They run on the host today. Correct the docs, and point at I1 for the containerized design. Found in Sage's I1 review.") }, + { title: "Board Reply needs a delivery path that isn't tmux", + description: p("The control board's /api/reply pastes into a tmux pane, which can't cross a container boundary. It needs another delivery path before the board or the sessions containerize under I1. Found in Sage's I1 review.") }, + { title: "Console cosmetic follow-ups from rows 76 and 83", + description: p("Small fixes left after the cutover:", + "1. packages/webui/systemd/mosaic-webui.service.in lines 6-9 still say Jason starts the unit and cite decisions 62 and 94; decision 102 says Jason or Mos.", + "2. packages/webui/README.md line 106 is 102 characters; wrap it.", + "3. Row 76: Darkwing's spliced header-comment sentence at packages/webui/tests/send-browser.test.mjs line 4, and Filbert's two round 2 notes (Gitea #1570 comment 27685).", + "4. When a session has expired, the proxy redirects a Reply to sign-in, the fetch fails without a status, and the page says \"Delivery may be unknown\" (packages/webui/src/public/app.js:380). Nothing reached the Console, so it should say not sent and to sign in again.", + "Touches packages/webui, so decision 109's notice to Mos applies before landing.") }, + { title: "Console flag tests: allowed user starting with \"-\", and the [--send] usage text", + description: p("From the row 83 landing (1a8ba587): an --allow-user value beginning with \"-\" needs a decision and a test in both scripts/webui-service.sh and packages/webui/src/serve.mjs, kept consistent. Darkwing's review (#1576 comment 27721) left a surviving mutant on the [--send] usage text; add a test that kills it. Touches packages/webui, so decision 109's notice to Mos applies before landing.") }, + { title: "Row 67 test 4: assert its new decisions are listed (Dewey N1)", + description: p("Dewey's N1 on row 67 (#1560 comment 27452), which Darkwing repeated (27627): test 4 creates decisions but doesn't assert that the listing shows them. Add the assertion.") }, +]; +const key = readFileSync(KEY, "utf8").trim(), sync = readFileSync(SYNC, "utf8").trim(); +async function api(method, path, body, auth) { + const r = await fetch(ORIGIN + path, { method, headers: { Authorization: `Bearer ${auth}`, "Content-Type": "application/json" }, body: body === undefined ? undefined : JSON.stringify(body), redirect: "error" }); + const t = await r.text(); let json = null; try { json = JSON.parse(t); } catch {} + return { status: r.status, json }; +} +const list = (j) => j?.items ?? (Array.isArray(j) ? j : []); +async function existing() { + const out = []; + for (let page = 1; page < 20; page++) { + const r = await api("GET", `/api/v2/projects/${PROJECT}/tasks?per_page=50&page=${page}`, undefined, sync); + if (r.status !== 200) throw new Error(`list tasks: ${r.status}`); + out.push(...list(r.json)); + if (list(r.json).length < 50) return out; + } + throw new Error("more than 19 pages"); +} +const rec = { at: new Date().toISOString(), project: PROJECT, created: [], problems: [] }; +const save = () => { + const out = JSON.stringify(rec, null, 1) + "\n"; + if (out.includes(key) || out.includes(sync)) throw new Error("secret in the record; not written"); + writeFileSync(OUT, out); +}; +const before = await existing(); +const clash = before.filter((t) => TASKS.some((x) => x.title === t.title)); +if (clash.length) throw new Error(`exists: ${clash.map((t) => `#${t.id} ${t.title}`).join("; ")}; refusing`); +writeFileSync(OUT, "", { flag: "wx" }); + +for (const t of TASKS) { + rec.created.push({ title: t.title }); + save(); + const body = { title: t.title, description: t.description, ...(t.due ? { due_date: t.due } : {}) }; + const r = await api("PUT", `/api/v1/projects/${PROJECT}/tasks`, body, key); + if (r.status >= 300 || !Number.isSafeInteger(r.json?.id)) { + rec.problems.push(`create ${t.title}: ${r.status} ${r.json?.code ?? ""} ${r.json?.message ?? ""}`); + break; + } + Object.assign(rec.created.at(-1), { id: r.json.id, index: r.json.index, inverse: `mark done: POST /api/v1/tasks/${r.json.id} done true (pm); delete is Jason's or ops-01's` }); + const back = await api("GET", `/api/v2/tasks/${r.json.id}`, undefined, sync); + Object.assign(rec.created.at(-1), { readBack: back.status, project_back: back.json?.project_id, due_back: back.json?.due_date, done: back.json?.done }); + if (back.status !== 200 || back.json?.title !== t.title || back.json?.project_id !== PROJECT || back.json?.done) rec.problems.push(`${t.title} read-back differs`); +} +save(); +process.stdout.write(JSON.stringify(rec, null, 1) + "\n"); +if (rec.problems.length) process.exit(2); diff --git a/docs/SESSIONS.md b/docs/SESSIONS.md index 6e54c08d2..f812fcdd8 100644 --- a/docs/SESSIONS.md +++ b/docs/SESSIONS.md @@ -752,3 +752,4 @@ are never rewritten or removed; corrections are new entries. 2026-10-12T14:59:20Z | sage | decision 107, I1-3 deferred | Jason deferred Q104 via Mos sage-0077: no WebAuthn in the I1 brief; reopens only as a new question once containers run; a compromised Console holding human authority is recorded as open 2026-10-12T15:00:59Z | sage | decision 108, I1-4 answered | Jason chose Q105 A via Mos sage-0078: subscription token as a read-only file secret per session container, no API key or gateway; copy-out risk accepted, bounded by the egress allowlist; all four I1 items answered, brief is Sage's on 2026-10-13 2026-10-12T17:27:49Z | sage | cutover live, decision 109 | verified the mosaic.woltje.com Console read-only after Mos's 17:21Z start (status active, send on, healthz 200); decision 109: landings touching webui, bus or cli in the canonical checkout are live changes until the Console runs from a pinned copy; BUILD-LOG entry +2026-10-12T17:38:19Z | sage | decision 110, follow-ups to Vikunja | Jason's Q109 via Mos sage-0081: Vikunja project 19 holds Mosaic work items; filed #153-#161 with the pm slot, read back with sync; #146 and #147 cited for the 10-13 rows; queue and Gitea stay the review and landing record; BUILD-LOG entry diff --git a/docs/plans/2026-09-26_lead-decisions.md b/docs/plans/2026-09-26_lead-decisions.md index c7eb96bb9..e64b7575c 100644 --- a/docs/plans/2026-09-26_lead-decisions.md +++ b/docs/plans/2026-09-26_lead-decisions.md @@ -2437,3 +2437,28 @@ which stay with him. Each item names who decided it and what happened. being deploys. Pointing the unit at it is a reinstall, which is Mos's step under decisions 102 and 103. It goes in the same window as decision 101's uid reinstall. +110. **Vikunja holds Mosaic work items (2026-10-12, Q109).** Jason, relayed + by Mos in sage-0081: "Always use Vikunja for task tracking." Mosaic + work items live as tasks in project 19 (Mosaic Stack) on + tasks.woltje.com. Sage files each new one there when raising it and + stops keeping follow-up lists in BUILD-LOG, standups or decisions. + Those records cite the Vikunja id. + - Filed at 17:37:55Z with the pm token slot, as Mos filed #146 to + #152, since Sage has no key of its own: #153 I1 brief, #154 M1 + brief and row, #155 row 77 brief (all three due 2026-10-13), #156 + compose.yaml:40 mount, #157 stale LAYERS and CONDUCTOR docs, #158 + board Reply without tmux, #159 Console cosmetic notes from rows 76 + and 83, #160 Console flag tests, #161 row 67 test 4 (Dewey N1). + Each was read back with the sync key. No labels, assignees or + bucket moves. Evidence: + `agents/sage/work/vikunja-setup/2026-10-12_followups.json`. + - Decision 109's pinned-copy row is #146 and decision 101's uid + reinstall is #147. Both are due 2026-10-13, and the 10-13 rows + cite them. + - The queue and its Gitea issues stay the review and landing + record, because `queue review` and `verify-commit` gate landings + on them. When a row opens for a Vikunja task, the task names the + row and the row's brief names the task. Moving the queue itself + into Vikunja would be a separate change and goes to Jason first. + - If the pm slot fails for Sage, Mos files the task (sage-0081). + Agent key scopes are #151, owned by ops-01.