jason.woltjeandClaude Opus 5.5
af4203ca92
One cumulative control-board, webui and seat state. The four rows edit the
same files (scan.mjs, page.html, README.md, app.js), so they land together,
each on its own receipt:
- Row 18, Discord connector rows on the board (#1509): R3 approved by
Darkwing and Dewey, Gitea comment 26257, manifest 254403b8. Jason
accepted the visual test.
- Row 22, board attention status (#1503): Filbert approved R1, comment
26248, manifest e40b58ec; restart receipt 26249.
- #1511, task attribution (row 6 code phase): R2 approved by Filbert and
Dewey, manifest d4c96395. docs/TOOLS.md carries the approved --by usage
line (tools-usage.patch 86bcba3c).
- #1512, relaunch activity (row 6 pilot): R1 approved by Darkwing and
Dewey, candidate manifest 47769fad. All seven source files match it.
Row 16, internal development bootstrap (#1510): the seven files outside
shared records match Filbert's R1 pins, receipt 26204 (agents/researcher/*,
scripts/test-darkwing-launch.mjs, the bootstrap plan).
packages/webui/src/public/app.js is committed at its #1512 R1 pin ce7d79a4.
The working copy holds Dewey's unreviewed return-flow candidate on top of
that, and it stays uncommitted.
Also: the four row briefs and Darkwing's evidence records under
agents/darkwing/work, including the 2026-09-26 tree manifest and the #1512
re-run against 21e3e908. Serial acceptance command: 397/397, three runs.
The failures that only show when tests run concurrently are in #1509 engine
tests, and they reproduce on clean HEAD.
Suites on the exact staged tree: config 24, task 90, foundation 43,
conductor 17, release 14, auth 15, discord 63; package union 397/397
(serial); test-darkwing-launch 5/5.
Shared records (BUILD-LOG, QUEUE, CURRENT, DEFERRED, SESSIONS, AGENTS.md,
agents/README.md) follow in Sage's records commit.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
2.8 KiB
Task attribution, row 6 code phase
Jason accepted row 18 and has explicitly required automatic continuation after accepted iterations. This starts the next already-briefed item, row 6 of QUEUE, under the existing control-board MVP plan's Piece 5. The newer standing start instruction replaces that piece's historical Sunday start-message scheduling; its ordering and protected-action gates remain. Use repository-native agents, not fleet launchers. Rows 9-13 still wait for row 6 completion.
Source assignment
Rocko implements the code phase from the internal agents/rocko profile in the canonical checkout, refactor. Filbert independently reviews backend/schema/tests; Dewey independently reviews presentation. Darkwing coordinates and owns tracking. The existing Rocko native process uses the older tmux socket; this is not a managed fleet worker assignment or authority to change its launcher.
Implement the already-approved taskSetBy requirement: mosaic seat task records an explicit --by NAME, otherwise MOSAIC_AGENT_NAME, otherwise unknown. Board serialization and both current board presentations display it by the task source. This is caller-supplied attribution, never authenticated identity or authorization.
Scope: packages/seat source/tests/docs, packages/control-board source/tests/docs, and minimal WebUI presentation/tests. Preserve existing attention and Discord-row changes exactly except the necessary additive integration. No launcher, connector, role, credential, home, live registration or service changes; no commits/push by the author. Use isolated fixtures, not actual seat task mutation during development.
Acceptance:
- Explicit --by wins over environment; absent/empty environment gives unknown. Invalid explicit input refuses before writing. Values are bounded and escaped.
- Existing registration records without taskSetBy still load, showing unknown. No breaking registration version change or implicit migration of old files.
- Preserve unrelated registration fields and original startedAt on task updates.
- Display attribution only for the task actually selected: no stale registration attribution on a transcript-derived task, and no borrowing native attribution for a Discord connector's fixed task. Attribution never enables replies/access.
- Isolated CLI/schema/scanner/browser regressions, exact frozen handoff and independent review. Existing accepted behavior remains covered.
This code phase precedes the plan's specified first Filbert behavior assignment, Relaunched seat shows the old last message. Do not start that concurrently. Gate F and its human-message evidence are not claimed by this code phase; record actual future dates, not the old plan's anticipated 2026-09-13 measurement. No live backend replacement or publication follows automatically from source tests.