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.1 KiB
Relaunch activity, row 6 behavior assignment
Jason confirmed the #1511 table tag and inspector wording. The code phase's bounded local delivery is accepted. Under his standing continuation mandate, start Piece 5's already-specified first Filbert assignment from the control-board MVP plan: Relaunched seat shows the old last message.
Filbert is sole source author. Darkwing independently reviews backend and tests; Dewey reviews presentation. Work in the canonical refactor checkout. Preserve accepted attention, Discord and task-attribution changes and all other owners' changes. Frozen prior candidates remain unchanged.
Scope: minimal packages/control-board scanner/presentation/tests/docs changes and corresponding WebUI presentation/tests when needed. If a live matching registration's startedAt is newer than recorded session activity, show 'relaunched at X, no messages since' instead of presenting an old message as current activity. Preserve historical transcript data. After new session activity, normal presentation resumes. Stale/dead registrations must not assert a relaunch. No effect on connector owner identity or fixed connector task.
Prove the old behavior first with isolated fixtures. Cover newer launch vs old activity, equality, subsequent new activity, stale registration and unknown/missing activity. Preserve attention/Seen, task attribution and reply authorization. Do not silently redesign those semantics. Return an exact frozen candidate, changed/inherited pins and reproducible tests for both independent reviewers.
No launcher, Claude discovery, credential, role, home, live registration or service changes by the author. No commits/push or shared tracking edits by the author. No real seat relaunch is needed for the source fixture tests. Darkwing owns tracking and any separately authorized integration.
Publication remains a separate gate, including prior unpublished dependencies. Do not claim Gate F or issue closure from fixture tests. Its eventual evidence must use the actual assignment dates and demonstrate no direct Jason-to-Filbert work messages; never backdate the old plan's anticipated 2026-09-13 metric.