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]>
3.3 KiB
Repository-native development bootstrap
Tracking: #1510, created and read-back verified as Darkwing. Branch refactor.
Observed shared HEAD after initial checks: dc5902aafded4042b6a919d9a6aec9f78febe935.
Other owners have dirty shared docs and active work; they are not adopted here.
Owner-authorized source work. Jason directs Darkwing to coordinate development
through Darkwing, Dewey, Filbert, Rocko and Researcher in the canonical checkout,
/mnt/storage/src/mosaic-stack. No ~/.mosaic launcher/provisioning changes.
No live fleet stop or migration. This assignment supersedes fleet expansion as
the current development priority, not the retained foundation's worker policies.
Delivery boundary
Darkwing authors; Filbert independently reviews. Keep other agents' existing changes and completed records, including Dewey's UI work and Sage's DYOR scope.
Allowed source work is the internal team documentation and Researcher's missing native entry/context/recovery files, the existing native launcher regression suite, and scoped queue/current/session/build tracking. Preserve agent.json and roles/contracts; explicit host mode does not widen a managed worker's authority. No new engine installation, credentials, home-directory launcher, native process launch, fleet task dispatch, deployment or unrelated runtime change.
Researcher uses the validated configured Pi model, the smallest consistent choice rather than a new provider/model decision. Darkwing/Dewey defaults, Filbert's pinned Codex configuration and Rocko's Sonnet wrapper are unchanged.
Acceptance
- All five internal agents have repository launch entry points and current coordination guidance. Researcher has the same per-agent validation and recovery behavior as the existing native Pi seats.
- Offline fake-engine tests cover context, registration, first/fresh/resume, malformed history, missing configuration/resources and duplicate-instance refusal. All data and registrations stay in test fixtures.
- Real launcher
--checksucceeds without a TUI, authentication/model request, seat registration or home-directory writes. This is configuration evidence, not actual engine/provider interoperability. - No managed role/config/contract changes, no edits to
~/.mosaic, and no migration or interruption of live seats. Existing unrelated diffs remain. - Independent exact-candidate review before claiming source readiness. No deployment or unapproved publication follows automatically from this task.
Current source checkpoint
Researcher previously had only a managed agent.json and fleet-labelled SOUL. Added native launcher, CONTEXT, README and the existing session validation behavior; changed its persona to the internal research role. Added Researcher to the existing isolated Pi launcher suite. All four Pi seats and Rocko's offline suite pass, six tests total. No real engine launched.
All five real launcher --check calls pass with no TUI, authentication request,
model call or seat registration. Next: obtain internal Filbert's independent
exact-candidate review. New launches read the
updated source context; existing running sessions do not reload it implicitly.
The approved CHAT-01C local commit and its Git receive-pack authorization gate remain separate. Do not use this assignment to modify external provisioning or publish unrelated local commits.