# 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

1. 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.
2. 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.
3. Real launcher `--check` succeeds without a TUI, authentication/model request,
   seat registration or home-directory writes. This is configuration evidence,
   not actual engine/provider interoperability.
4. No managed role/config/contract changes, no edits to `~/.mosaic`, and no
   migration or interruption of live seats. Existing unrelated diffs remain.
5. 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.