docs: map foundation to integrated rewrite baseline

docs/plans/CURRENT.md

@@ -7,11 +7,101 @@ update this file to the next action). No ambiguity, no re-planning.
 
 ## Next action
 
-Review `docs/plans/2026-09-03_auth-provider-harness-registry.md` against its ten review gates; revise until owner-approved. No implementation starts before approval.
+Owner review of the completed technical map and separate authorization of a
+non-author review. Handoff: `docs/plans/2026-09-06_foundation-map-handoff.md`
+(MAP-HANDOFF-2); map: `docs/plans/2026-09-06_foundation-technical-map.md`.
+Source/accepted-plan baseline: `d4696d09eb1b5dcf1028f30db2cd63735f51cb16`,
+parent `44f257cb06484feda3412d9382e3587393796353`. Mapping documents are pinned by
+the separate commit containing this checkpoint, not falsely attributed to d4696d09.
+
+Dewey's MS55-DW-3 commit, 43-path scope, parent and index release were verified.
+Jason's conditional resumption authorization is satisfied. R1-R34 coverage,
+reconciled package/source ownership, source identities and the bounded inspector
+recommendation are ready for owner review. Preparing that handoff does not imply
+independent approval. No implementation, migration, source moves, push or issue
+closure is authorized. No involvement in the reported ~/.mosaic failure.
+
+The extension owns the active mapping goal's lifecycle; this file records task
+progress and the next approval gate. Earlier phase-2 acceptance remains valid.
+
+## Earlier owner and source checkpoints
+
+Historical context below; the current candidate and live goal checkpoint supersede
+the earlier partial-draft descriptions.
+
+The prior hands-on checkpoint demonstrated launch, workspace listing, and conversation resume from Jason's supplied output. Fresh context and mission recovery were not tested. The owner redirected to this planning exercise; no broad foundation acceptance is inferred.
+
+Owner ruling recorded 2026-09-06 as R16-R17: current approved SOUL on launch, stable per-execution inputs, and a shared launch/configuration hash reference for TUI/GUI/WUI mismatch notices recommending Fresh. D10 is partly resolved. Q20/Q21 now settle broad fingerprint categories and automatic non-blocking notices plus on-demand checks; exact field/dependency hashes and delivery mechanics remain D16. This does not advance the phase or authorize implementation.
+
+Interview round 1 recorded: Q1 permits linked project/workspace missions, Q2 permits bounded system registration/assignment authority, and Q3 limits visibility to shared project information and explicitly permitted workspaces. Q4 clarification A creates and announces the first conversation without an offer; later default launches resume, while missing/damaged established sessions cause an error. Round 2 Q5-Q9 confirms single-parent hierarchy, the Fresh recovery information set, delegated within-plan non-destructive decisions and routine reviewer acceptance, assignment-only default Abandon, and explicit authorization for prerequisite work. Delegated authorization need not prompt the user each time; user phase checkpoints remain. Round 3 Q10-Q14 permits unassigned discussion/inspection with recorded assignments for changes, requires an interactive active-session conflict notice and offer to connect, separates shared work records from transcript grants, chooses concise audit metadata with controlled evidence, and scopes membership revocation to affected executions. Round 4 Q15-Q19 requires explicit service conflict handling, one controlling interface with authorized observers, controlled Fresh replacement, delegated evidence-based recovery without blind replay, and affected-execution blocking on audit failure. Round 5 Q20-Q24 extends fingerprints to shared behavior-affecting configuration, requires automatic non-blocking notices plus on-demand checks, scopes personal context, retires closed workspaces without deletion, and requires explicit reviewed legacy adoption. Round 6 Q25/Q26 pauses affected work for reconciliation after approved plan changes and chooses standard scope roles with registration-specific narrowing. Jason subsequently confirmed shared understanding of intended behavior. Jason then authorized phase 2. A tool-free source-analysis run, r-20260906T024609Z-68ee7f, succeeded; pinned 0.84.4 documentation was extracted from the existing image without starting its extraction container. These are source/document findings, not runtime feature tests or independent approval. The first contract candidate is partial. Q27 A now settles command-audit granularity; dependent schema and enforcement drafting may continue within phase 2. Full schema/plan approval remains pending.
+
+## Accepted phase-2 checkpoint (historical)
+
+- Goal: issue-53-phase2. Objective: an owner-reviewable contract for agents,
+  projects, workspaces, sessions, permissions, and audit evidence. Completion
+  owner: Jason. Author/workspace/session remain those recorded below.
+- State: satisfied. Jason explicitly accepted phase 2 after the plain-language
+  explanation of the planning baseline and separate later gates. P2-7 is complete.
+  REVIEW.md retains D1-D16 and the unproved implementation mechanisms. This is
+  owner plan acceptance, not independent technical or security certification.
+- Acceptance: repair/check schemas and fixtures, complete the operation/recovery
+  contract, resolve material behavior decisions, prepare a review package and
+  one user-testable increment recommendation, then obtain owner acceptance.
+- Evidence: `python3 docs/plans/foundation-v1-candidate/check.py` passes 38 command
+  and 38 record shape cases, 16 path cases, 7 restricted-domain hash vectors,
+  155 runtime/control/artifact cases and 35 synthetic rule-model cases. Ten
+  deliberately shape-valid forgeries still require trusted runtime rejection.
+  These are not runtime security tests or independent acceptance.
+- Reboot fixture defects were repaired, not discarded. Eleven positive records
+  now include their common envelope; negative mutations were preserved. Required
+  calendar/UTF-8/control-character checks are explicit in the author checker.
+- Next gate: separate owner authorization for mapping, not more phase-2 approval.
+  No mapping or implementation started. This session continues the
+  file-based goal and has not configured an extension/timer for it. Separate #54
+  work subsequently added/tested a project-local goal extension, as recorded in
+  the shared logs; that work and its state were left untouched. This session has
+  not migrated issue-53-phase2 into that runtime. Elapsed time never grants approval.
+- No new worker dispatch, external reply obligation, or uncertain external action
+  initiated by this phase-2 session is outstanding. No numeric work budget supplied;
+  aggregate usage remains unavailable.
+- Authority remains phase-2 planning and read-only investigation. No runtime
+  implementation, mapping, migration, commit, push, or issue closure.
+
+## Prior recovery checkpoint, 2026-09-06 03:42 UTC
+
+Historical snapshot below; the live goal checkpoint above supersedes its pause
+and unfinished-fixture status.
+
+- Goal: issue-53-phase2. State: paused by owner steering. Writer: darkwing,
+  pi session `01a06e48-0718-71f2-a889-c263c4800fb9`, explicit working directory
+  `/home/jwoltje/src/mosaic-stack-dev-test`, project `mosaicstack/stack-v2`.
+  This is the existing single-writer planning assignment, not a runtime claim.
+- HEAD remains `69d1bb3`. Preserved all uncommitted planning and unrelated skill
+  work. No reset, cleanup, commit, push, or implementation occurred.
+- Five planning artifacts survived in `docs/plans/foundation-v1-candidate/`:
+  command schema/fixtures, `check.py`, and record schema/fixtures. The three
+  command-check file hashes match the pre-reboot checksums.
+- `python3 docs/plans/foundation-v1-candidate/check.py` passes 38 shape fixtures
+  and 5 deliberate shape-valid forgeries. This does not prove runtime security.
+- The unfinished record checker is NOT integrated into check.py. A read-only
+  diagnostic found 13 expectation mismatches: all 11 positive record fixtures,
+  plus unicode-byte-limit and bidi-control. The first positive lacks five common
+  envelope fields, indicating fixture generation is incomplete. Do not count
+  negative cases as meaningful until positive fixtures are repaired and rerun.
+- System config validates, Docker responds, and the pinned image ID and prior
+  research result hash still match the phase-2 evidence. No Mosaic worker
+  container was running at inspection. Pinned temporary docs remain available.
+- Next work after explicit resume: repair record fixtures, enforce/test UTF-8
+  byte and control-character path checks, integrate both schema suites, then
+  complete the remaining phase-2 record/permission/lifecycle work and owner gate.
+- No outstanding assistant-initiated external action or reply is known. Wake is
+  manual: Jason sends a resume instruction. No timer or automatic continuation
+  is registered. Aggregate usage is unavailable; no numeric budget was supplied.
 
 ## Queue (ordered per docs/plans/ROADMAP.md)
 
-1. Deferred by owner: CI runners (Gitea hardware slow); second real adapter; push automation
+1. Paused for owner alignment: review `docs/plans/2026-09-03_auth-provider-harness-registry.md` and reconcile later owner decisions and #53's workspace-session model. Gate 7 remains unresolved. No registry implementation is approved, and this work does not resume automatically after the planning exercise.
+2. Deferred by owner: CI runners (Gitea hardware slow); second real adapter; push automation
 
 ## Rules