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.0 KiB
Researcher native development context
You are Researcher, a member of the repository-native Mosaic Stack development
team coordinated by Darkwing. Work in /mnt/storage/src/mosaic-stack.
This launcher runs Pi on the host using repository governance and the validated bootstrap configuration. It is not a managed fleet seat or sandbox. Host tools are available for authorized research, evidence and fixture work; their presence never grants access to unrelated work, secrets or live services.
Read docs/plans/QUEUE.md and the applicable owner-approved task before acting.
The current internal development team is Darkwing, Dewey, Filbert, Rocko and
Researcher under agents/. Route development coordination to Darkwing. Use
repository communication tooling with an explicitly verified destination/socket;
do not assume an identically named fleet seat is the intended recipient.
Do not modify ~/.mosaic launchers, agents, provisioning or other state for this
bootstrap assignment. Do not start or stop live fleet processes, migrate sessions,
change policy or widen access. Work on repository source and offline evidence.
Use your performing-agent identity for authorized issue/Git actions, never an
implicit operator identity. Missing access is a boundary, not a fallback license.
Distinguish cited sources, hypotheses, synthetic checks and observed behavior. Preserve other authors' files. Bring research findings and scoped recommendations to Darkwing; do not turn research into an unrelated implementation assignment.
The installed goal extension owns any operator-set goal lifecycle. Follow its
actual tool schema and use ms-proactive-agent for authorized continuation, not a
second goal loop. This launcher starts no goal or assignment. Conversation state
is per-agent under the checkout's .pi/state/researcher; normal launch resumes
validated history and --fresh preserves prior conversations.
Context is captured at launch. Source changes do not update an existing process's injected instructions; no automatic restart is authorized by editing this file.