Chart the route to Plasmid v1

[aksOps]

Destination

Produce a contradiction-free, implementation-ready route from the current partial worktree to the complete Go-only Plasmid v1, using Google ADK directly. The final route must align engineering standards, product behavior, package ownership, dependency order, and executable acceptance evidence.

Notes

• Domain: CLI-free, in-process coding-agent harness for Go.
• This map resolves decisions; it does not execute the production implementation.
• Plasmid v1 is Go-only and retains the complete product scope.
• Google ADK is the direct Go framework. The provider-neutral loop abstraction is removed.
• A minimal working Harness is an integration checkpoint, not the v1 release boundary.
• Data-only behavioral fixtures remain portable where practical; Go APIs are not distorted for hypothetical ports.
• Current session files and unshipped APIs carry no compatibility guarantee.
• Revised engineering standards govern implementation; SPEC governs product behavior; PLAN governs execution. Current code is evidence, not authority.
• Progress states are missing, source present, targeted verified, integrated, and frozen. Only frozen counts as complete.
• Before asking the human a decision question, inspect PLAN.md and SPEC.html, verify against code and primary sources, and ask only when a genuine unresolved product trade-off remains.
• The user authorized batching unblocked grilling tickets. Tickets remain individually resolved; documented or mechanically derivable engineering answers do not become user questionnaires.

Decisions so far

• Verify Google ADK v2.2 integration contracts — Direct ADK removes translation bridges; retain native Harness ownership, session, discovery, gating, warning, and lifecycle responsibilities.
• Verify foreign extension storage contracts — Share only Agent Skills core; use provenance-aware host adapters and remove speculative Copilot probing and global ecosystem precedence.
• Define the direct Google ADK package boundary — Delete loop and adkloop; expose native ADK contracts only at direct integration surfaces while pure leaf concerns remain framework-free.
• Define durable session semantics — Native ADK sessions use durable transcript logs, independent shared-state journals, derived snapshots, post-commit repair, scoped locking, and strong fsync-by-default guarantees.
• Define tool visibility, hooks, and confirmation semantics — Use native ADK tools/callbacks, deterministic collision failures, deny-wins turn scopes, typed handler errors, and optional host confirmation defaulting off.
• Define the shell execution security contract — Shell execution is bounded but not isolated; it retains host-process authority, while trust-aware prompt execution defaults to project/user content only.
• Define behavioral fixtures and completion evidence — One deterministic fixture tree and unique receipt ladder prove source, targeted, integrated, and frozen states without double-counting aggregate gates.
• Define extension resolution and activation — Use inert provenance-aware host catalogs, explicit trust/MCP gates, argument-capable native skill tooling, and lifecycle-owned MCP clients.
• Define the public Harness and configuration surface — Keep the SPEC API shape with native ADK model/tool/plugin/event types, one repair-oriented config owner, transactional construction, and explicit reverse lifecycle.
• Define LSP enforcement integration — Detection-only lazy LSP integrates through native after-tool callbacks, bounded diagnostic injection, fixed write/edit enforcement, and fail-soft process lifecycle.
• Define compaction integration — Native model callbacks perform sticky deterministic tool-output/turn compaction, durable sidecars, calibration, and output-budget reset without summarization in v1.
• Define implementation slices and parallel lanes — Migrate tools/sessions/config and leaf foundations in parallel, establish a native-ADK Harness checkpoint, then integrate context, LSP, extensions, compaction, and release gates under serialized shared ownership.
• Define authoritative document reconciliation — Rewrite AGENTS constraints, SPEC product behavior, and PLAN execution ledger as single authorities; README follows only released behavior and historical executable text is removed.

Not yet specified

None. The decision route is complete. Execution starts by reconciling the authoritative documents, then follows the slices in Define implementation slices and parallel lanes.

Out of scope

• Executing production implementation inside this Wayfinder map.
• Python, Java, or TypeScript implementations for v1.
• Alternate agent frameworks or provider-neutral runtime abstractions for v1.
• Backward compatibility for current unshipped APIs or session data.