Files
stack/agents/darkwing/work/task-attribution/live-test-envelope.md
T
jason.woltjeandClaude Opus 5.5 af4203ca92 feat(board): session attention, Discord rows, task attribution and relaunch activity (rows 18, 22, #1511, #1512)
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]>
2026-09-26 14:54:18 -05:00

2.2 KiB

Proposed #1511 local test envelope

Original proposal retained below. Jason authorized the backend update, completed 2026-09-15. Rocko's stale registration blocked that target before mutation. Jason then explicitly authorized Filbert instead and confirmed Claude console integration remains separate. The Filbert metadata update and live API checks passed; operator visual acceptance is pending. Receipt: live-test.jsonl. No Rocko registration or process was changed.

  • Reverify the approved R2 pins and current backend PID/start/command/config. Record the five native agent identities and connector service identity.
  • Restart only the control-board backend on loopback 7331, using its existing command/config. Do not restart agents, WebUI or the Discord connector.
  • Verify health and that the updated reader accepts existing records. Check actual asset loading before claiming either presentation loaded R2.
  • For the visual test only, update the repository-native Rocko registration's task to '#1511 task attribution user test', with explicit setter darkwing. Use the reviewed seat task command and explicit repo layout. First verify the registration matches the intended native session; a mismatch blocks the write.
  • Preserve the original registration privately outside the repository. Never print its contents. Assert only task, taskSetBy and updatedAt change, with all identity fields and startedAt preserved. No other registration may change.
  • Verify API selection and ask Jason to inspect the 'set by darkwing' tag and caller-claim wording. Legacy registered attribution remains unknown; inferred and connector tasks remain not applicable. Agent/connector identities unchanged.

Rollback: before any attribution write, an incompatible old reader can be restored only from the retained prior artifact. After the one authorized write, restoring an old reader requires restoring that record's original task metadata first, with an exact unchanged-current-record check. If anything else changed, stop rather than overwrite it. Keep the compatible reader while resolving the conflict. No broad metadata migration or automatic rollback over concurrent edits.

This envelope does not authorize publication or the later Filbert behavior task.