Files

T

jason.woltjeandClaude Opus 5.5 5175ca10f2 docs(plans): Vikunja probe record; lead decision 51

Researcher ran P1-P7 on a scratch Vikunja 2.7.0. Scope names in
addendum A are wrong, polling on updated misses column moves and
deletions, and If-Match isn't enforced. Decision 51 rules on each.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

2026-10-04 18:31:47 -05:00

work

docs(plans): Vikunja probe record; lead decision 51

2026-10-04 18:31:47 -05:00

agent.json

feat(agents): agent seats - per-agent SOUL, role, definitions dir (#36 )

2026-09-03 11:56:38 -05:00

CONTEXT.md

docs(agents): seats read the queue, not CURRENT.md (row 10, #1508 )

2026-09-26 20:23:20 -05:00

launch.sh

feat(board): session attention, Discord rows, task attribution and relaunch activity (rows 18, 22, #1511 , #1512 )

2026-09-26 14:54:18 -05:00

README.md

feat(agents): Sage launch files, lead text across seat personas, lead decision record

2026-09-26 15:11:10 -05:00

SOUL.md

feat(agents): Sage launch files, lead text across seat personas, lead decision record

2026-09-26 15:11:10 -05:00

validate-sessions.mjs

feat(board): session attention, Discord rows, task attribution and relaunch activity (rows 18, 22, #1511 , #1512 )

2026-09-26 14:54:18 -05:00

README.md

Researcher

Repository-native technical research seat, coordinated by Sage. Uses Pi and the validated bootstrap provider/model defaults; no fleet provisioning is needed.

From /mnt/storage/src/mosaic-stack:

agents/researcher/launch.sh --check
agents/researcher/launch.sh
agents/researcher/launch.sh --fresh

--check validates configuration/context and the pinned local Pi version without launching a TUI, registering a seat, requesting authentication or calling a model. Normal launch registers the repository seat through scripts/mosaic, then uses the existing host-development helper. It resumes validated per-agent conversation state under .pi/state/researcher; --fresh starts another conversation without deleting history. Existing launcher locking prevents duplicate native instances.

This is the same explicit native mode as Darkwing/Dewey/Filbert, not a fallback from a container policy refusal. The retained agent.json describes the separate managed-mode definition; no managed role or capability policy is changed here.

Bootstrap configuration remains authoritative. Missing config, context or pinned dependencies fails closed. No configuration or credentials are copied from a fleet seat. No files under ~/.mosaic are modified by this source setup. Use the existing bootstrap/build workflow documented in the repository, rather than installing an unversioned engine or modifying a home-directory launcher.

No engine was launched to verify this source change. Offline launcher tests use a fake Pi and isolated registration/session directories. Live startup and external provider authentication are separate observations, not implied by passing tests.