# Darkwing — relocation handoff Recorded 2026-09-07 17:43 UTC. Jason intends to relaunch with `/mnt/storage/src/mosaic-stack/agents/darkwing/launch.sh`. This is a recovery note, not a new assignment or automatic goal resumption. ## Read first 1. Root `AGENTS.md` and `docs/plans/CURRENT.md`. 2. This note, then `git status --short` and `git log --oneline -5`. 3. Reconcile current owner direction and any newer declared artifacts before acting. ## Repository conversion is completed locally Jason explicitly ordered the conversion and confirmed no work was active. - Canonical checkout: `/mnt/storage/src/mosaic-stack`. - Origin: `https://git.mosaicstack.dev/mosaicstack/stack`. - Branch: `refactor`. - Conversion commit: `127a54fdff1fe6ae56c3197edddf957481465db4`. - New foundation is at root. `v1/` is legacy archival source, NOT current code. - Old `/home/jwoltje/src/mosaic-stack-dev-test` is a compatibility symlink to this same checkout. Do not recreate a second working copy there. - Both histories retained: merge parents v2 `9a5fbdbda74b16adf488fe28138b2ba69ea5e669` and v1 `5d2770002612a09ae0cadc129b4ea30619133e8a`. - Exact 3,507-file v1 tracked tree imported; v1 refs under `refs/archive/v1/`. - Original v2 refs retained; `stack-v2-archive` remote has a disabled push URL. - Only legacy tracked tree and four conversion docs committed. All earlier uncommitted/untracked/ignored work preserved. Index was verified clean. - Issue https://git.mosaicstack.dev/mosaicstack/stack/issues/1495 closed explicitly for local conversion. No push, PR/trunk merge or live-service change occurred. Record: `docs/plans/2026-09-07_repository-consolidation-completed.md`. Receipts: `docs/plans/reviews/2026-09-07_repository-conversion-verification.json` and `2026-09-07_repository-conversion-postcommit-verification.json`. Verified rollback copies, NOT development roots: - `/mnt/storage/src/.mosaic-stack-conversion-20260907T172430Z/` - `/home/jwoltje/src/.mosaic-stack-dev-test.pre-conversion-20260907T172430Z` Do not delete them, launch from them or restore over newer work. ## Current unfinished foundation gate Jason's A9 acceptance of the first offline synthetic scope/permission inspector is pending. Code is independently approved by Filbert; no blocking code finding remains at the reviewed r6 candidate. Owner acceptance is not inferred from tests. - Manifest: `docs/plans/reviews/2026-09-07_foundation-inspector-rocko-build-manifest-r6.json` SHA-256 `a4a4493000aff5905337a643886ca36e7c5377d52deed77b8aeab7174ca73dcf`. - Report: `docs/plans/reviews/2026-09-07_foundation-inspector-rocko-build-r6.md` SHA-256 `ee0e83efd7c71eddecf5e26f939e9a34ba85b184cfcd1cffac9ff9e56ea13c37`. - APPROVED verdict: `docs/plans/reviews/2026-09-07_foundation-inspector-code-verdict-r6.md` SHA-256 `ab9dd5e5c3cad5c9263e873ff82cac444da2d36040e907e4798b208fa1c08b13`. - Guide: `docs/plans/reviews/2026-09-07_foundation-inspector-demo.md`. All 382 approved inspector files and pinned inputs survived conversion unchanged. Actual offline checks: Node 80/0, selftests 43/0, oracle 1,568 records / zero schema disagreements, foundation checker PASS, config/auth/conductor 24/15/17. Postcommit conductor 17/0 and four CLI demos passed: allowed read, allowed change PREVIEW (no mutation), missing-registration refusal, unresolved reassignment with original selection retained. Demo inputs are separate synthetic scenarios. `test-task.sh` and `test-release.sh` remain NOT RUN / DEFERRED under Jason's bounded offline-demo ruling. No deployment/native/live/provider/security certification. Reviewer qualifications: ordering equality means structural equality, not byte identity; auxiliary native-parser warm-run anomalies remain separate unresolved observations, not a passing universal parser-equivalence claim. Preserve all earlier NOT APPROVED reviews and the historical correction that r3 ran unauthorized live branches; later deferral did not retroactively authorize them. ## Ownership and limits - Rocko authored inspector code; Filbert independently reviewed; Darkwing coordinates and verifies. Keep the approved candidate frozen unless a new fix is authorized. - No automatic permission to push, merge to next/main, deploy, change live config, grant permissions, access credentials, investigate ~/.mosaic, or start new runtime work. Local conversion authority is not authority for those activities. - Preserve unrelated pending work. In particular `scripts/agent.sh`, `docs/TOOLS.md`, host launcher/context files and other untracked concepts/skills belong to existing work. Do not blanket-stage/reset/clean. Root logs and CURRENT remain uncommitted. - Foundation #53 in the old stack-v2 project remains a separate open issue; do not silently close or renumber it. Accepted historical SHA/path citations remain valid. - Rocko's Archify C1 remains HELD for owner T2/T3 decisions. No lane reassignment. - Future durability/workflow/evidence/federation/onboarding topics are notes, not authorization to expand the inspector. ## Communications Use only `tools/tmux/agent-send.sh`; sender `dragon-lin:darkwing`. Rocko: `-L mosaic-fleet -s '=rocko'`; Filbert/Dewey: `-L default -s '=filbert'` / `'=dewey'`. Conversion notice delivered to Rocko. Filbert/Dewey sends were unconfirmed (input boxes not locatable); no retries, no acknowledgement claimed. Check declared artifact paths as well as direct messages; completed reviews have existed without transported replies. Do not inspect private panes or blindly resend. ## Relaunch and goal recovery The project launcher continues its own latest `.pi/state/darkwing/sessions/` conversation by default. Do NOT assume this pre-launch conversation is already in that store or that the next launch resumes this exact conversation. This handoff is the durable bridge. No session-tree migration or launch was performed here. The goal extension owns lifecycle. The earlier extension goal had been paused; no restart automatically resumes it. Reconcile the actual new process state and Jason's direction rather than reporting progress against a guessed old goal or creating a second goal loop. Launch alone grants no new assignment. This handoff and its CONTEXT pointer are documentation-only. Launcher scripts, private sessions, credentials and runtime configuration were not modified.