planr 1.6.0 → 1.7.1

package/docs/planr-spec/TECH_ARCHITECTURE.md

@@ -1,143 +0,0 @@
-# Technical Architecture
-
-## Architecture Goals
-
-- REQ-ARCH-001: Keep item state, picks, worker runtime state, approval gates, links, log, reviews, and events in one local SQLite source of truth.
-- REQ-ARCH-002: Keep rich product and build plan context in repo-local Markdown files that remain useful without Planr installed.
-- REQ-ARCH-003: Support CLI, MCP, and optional HTTP/SSE as lenses over the same core engine.
-- REQ-ARCH-004: Make Codex, Claude Code, Cursor, and generic MCP clients first-class integration targets.
-- REQ-ARCH-005: Avoid provider-specific logic in the core graph engine.
-
-## System Context Diagram
-
-```text
-Developer
-  -> planr CLI
-     -> Core engine
-        -> SQLite graph database
-        -> .planr Markdown project
-        -> Git repository
-
-Agent clients
-  -> MCP stdio / MCP HTTP
-     -> Core engine
-        -> SQLite graph database
-        -> .planr Markdown project
-
-Optional dashboard
-  -> Local HTTP/SSE server
-     -> Core engine
-```
-
-## Component Boundaries
-
-- `core`: map graph operations, state machine, item readiness, worker runtime state, approval gates, log, reviews, contexts, search.
-- `storage`: SQLite schema, schema upgrades, transactions, FTS indexes.
-- `planpack`: `.planr` project pack, plan parsing, Markdown frontmatter, review artifacts.
-- `cli`: user commands and deterministic output.
-- `mcp`: tools, resources, prompts, capability negotiation.
-- `server`: optional local REST/SSE API.
-- `agents`: integration helpers for Codex, Claude Code, Cursor, and generic clients.
-- `git`: worktree, branch, diff, and changed-file log.
-- `recovery`: stale-pick detection, timeout handling, retry policy, and manual condition reporting.
-- `review_workspace`: local browser review HTML and workspace JSON projection.
-- `packages`: reusable JSON export/import packages with plan snapshots, logs, contexts, and review artifacts.
-
-## Client Architecture
-
-- CLI is the primary client and must be scriptable.
-- TUI/dashboard are optional clients over the same API.
-- MCP clients must receive concise, structured responses optimized for LLM context.
-- All client layers must call core services, not mutate database or Markdown directly.
-
-## Backend Architecture
-
-V1 is a local backend packaged into the CLI binary:
-
-- SQLite database at `.planr/planr.sqlite` by default.
-- WAL mode enabled for concurrent readers and serialized writers.
-- Local service optional for dashboards and long-running agent orchestration.
-- Local review workspace is served from the same localhost HTTP boundary as the REST/SSE API.
-- No cloud backend in V1.
-
-## Data Architecture
-
-- Map state, worker heartbeats, progress, stale ownership data, and approval gates: SQLite.
-- Rich product plans, build plans, and project context: `.planr/*.md`.
-- Live status summaries: SQLite.
-- Search: SQLite FTS over items, contexts, plan metadata/frontmatter/headings, logs, and review summaries.
-- Large artifacts: paths and metadata by default; inline content only for small explicitly provided artifacts.
-
-## AI Architecture
-
-Planr does not call model providers by default. It guides external agents through:
-
-- MCP tools for map, plan, log, and review operations.
-- MCP prompts for `plan`, `work`, `review`, `map`, and `summary` workflows.
-- Client-specific install snippets for Codex, Claude Code, and Cursor.
-- Optional runner wrappers for local Codex/Claude/Cursor CLIs when explicitly configured.
-
-## Auth And Identity
-
-- V1 local mode uses OS user access and file permissions.
-- Worker identity is an explicit `worker_id` string, not an auth boundary.
-- HTTP server binds to localhost by default.
-- Remote HTTP mode is post-V1 and must require authentication.
-
-## Integrations
-
-- Codex: CLI instructions, MCP registration, optional `codex exec` runner, optional `codex review` integration.
-- Claude Code: `.mcp.json` or CLI-based MCP registration guidance.
-- Cursor: `.cursor/mcp.json` project config and global config guidance.
-- Generic MCP: stdio first; streamable HTTP optional.
-- Git: worktree isolation and scoped diff log.
-
-## Security Architecture
-
-- No shell hooks by default.
-- Any command runner must show command, cwd, environment policy, and worker id.
-- Secrets must not be stored in database, plans, logs, or analytics.
-- MCP tools that mutate state must be separated from read-only resources/prompts.
-- Destructive graph operations require preview or explicit flags.
-
-## Privacy Architecture
-
-- Local-only by default.
-- No provider telemetry by default.
-- No content logging by default.
-- Export and delete commands must remove Planr database state and `.planr` artifacts when requested.
-
-## Observability
-
-- Local structured event log in SQLite.
-- Optional JSONL debug log with content scrubbing.
-- `planr doctor` for installation, database, MCP, and client integration checks.
-- `planr trace item <id>` for item lifecycle debugging.
-
-## Deployment Environments
-
-- Local development: source checkout and debug binary.
-- Local production: installed binary via package manager or release asset.
-- CI: headless CLI mode with explicit db/path.
-- Hosted/team: out of scope for V1.
-
-## Failure Modes
-
-- Database locked: retry bounded writes, then return actionable diagnostic.
-- Corrupt Markdown plan: preserve file, mark parse status degraded, keep map usable.
-- Missing MCP client support: print manual CLI instructions.
-- Agent run interrupted: keep item picked/running with heartbeat timeout and release/re-pick command.
-- Recovery sweep interrupted: preview is non-mutating; apply mutates only listed recoverable work and records events.
-- Review fails: create fix item chain instead of closing the parent.
-- Package import cancelled: preview leaves database and `.planr` files unchanged.
-
-## Scalability Assumptions
-
-- V1 target: hundreds of projects, tens of thousands of items, thousands of plan files per machine.
-- SQLite and FTS are sufficient for V1.
-- Remote multi-user concurrency is post-V1.
-
-## Open Technical Decisions
-
-- OD-ARCH-001: Whether to implement worktree management in core V1 or as an extension.
-- OD-ARCH-002: Whether dashboard uses server-rendered HTML, TUI, or a small SPA.

package/docs/planr-spec/UX_FLOWS.md

@@ -1,235 +0,0 @@
-# UX Flows
-
-## Navigation Model
-
-Planr V1 is CLI-first with optional TUI/dashboard. Public commands use Planr-native vocabulary:
-
-- `planr project`: setup and integration.
-- `planr plan`: reviewable Markdown plans for product specs, build contracts, and review packages.
-- `planr map`: live graph inspection and mutation.
-- `planr item`: item creation and detail.
-- `planr pick`: atomically pick the next ready item.
-- `planr log`: record files, commands, tests, and handoff proof.
-- `planr review`: review/fix/approval loop.
-- `planr close`: close an item with log.
-- `planr doctor`: diagnostics.
-
-## Screen Map
-
-### CLI
-
-- Project status.
-- Item detail.
-- Ready queue.
-- Critical lane.
-- Plan list/detail.
-- Map summary.
-- Log detail.
-- Doctor report.
-
-### Optional TUI/Dashboard
-
-- Project overview.
-- Graph view.
-- Ready/running/blocked map lanes.
-- Plan viewer.
-- Item detail.
-- Log/review panel.
-- Agent runs panel.
-- Diagnostics panel.
-
-## State Machine
-
-```text
-NO_PROJECT -> INITIALIZED
-Trigger: planr project init
-Guard: repo path writable
-Side effects: create database and .planr pack
-Failure behavior: report blocked path and no partial overwrite
-
-INITIALIZED -> PRODUCT_PLANNED
-Trigger: planr plan new
-Guard: project exists
-Side effects: create product plan package
-Failure behavior: show validation errors
-
-PRODUCT_PLANNED -> BUILD_PLANNED
-Trigger: planr plan split
-Guard: product plan has selectable slice
-Side effects: create focused build plan
-Failure behavior: show missing decisions
-
-BUILD_PLANNED -> MAPPED
-Trigger: planr map build --from <plan>
-Guard: plan acceptance criteria are parseable
-Side effects: create linked map items
-Failure behavior: show unmapped requirements
-
-MAPPED -> ITEM_PICKED
-Trigger: planr pick
-Guard: at least one ready item
-Side effects: atomic pick, start run context
-Failure behavior: show blockers or no-ready status
-
-ITEM_PICKED -> EVIDENCE_RECORDED
-Trigger: planr log add
-Guard: log fields valid
-Side effects: write log and attach to item/run
-Failure behavior: keep item running/blocked with diagnostic
-
-EVIDENCE_RECORDED -> ITEM_CLOSED
-Trigger: planr close
-Guard: required log and reviews are satisfied
-Side effects: close item, promote downstream items
-Failure behavior: keep item running/blocked with diagnostic
-
-ITEM_CLOSED -> REVIEW_READY
-Trigger: review policy requires review
-Guard: code item completed
-Side effects: create or unlock review item
-Failure behavior: parent stays incomplete
-```
-
-## Onboarding Flow
-
-1. User runs `planr project init`.
-2. Planr detects repo, Git state, old `.planr` artifacts, and available agent clients.
-3. Planr creates project pack and database.
-4. Planr offers integration commands:
-   - Codex MCP/config.
-   - Claude Code MCP config.
-   - Cursor `.cursor/mcp.json`.
-5. User runs `planr doctor --client all`.
-
-Acceptance criteria:
-
-- REQ-UX-001: Init output must clearly distinguish created files, detected files, and skipped files.
-- REQ-UX-002: Doctor output must show each agent integration as pass, fail, warning, or not installed.
-
-## Product Plan Flow
-
-1. User runs `planr plan new "App idea"`.
-2. Planr captures product intent, platform, users, data sensitivity, AI, monetization, integrations, and launch constraints.
-3. Planr creates a Markdown plan package: product spec, UX, architecture, ADRs, safety/privacy/security, API/data model, implementation specs, QA, release, and task checklist.
-4. Planr marks assumptions and open decisions explicitly.
-5. User runs `planr plan check`.
-
-Acceptance criteria:
-
-- REQ-UX-010: A created plan must include product, UX, architecture, safety/privacy/security, data/API, QA, release, and task files unless explicitly scoped down.
-- REQ-UX-011: Plan checks must report missing required sections, open decisions, and validation warnings.
-
-## Implementation Plan Flow
-
-1. User or agent runs `planr plan split <plan> --slice "MVP backend"`.
-2. Planr creates a focused Markdown plan with source, scope decision, ownership target, phases, verification, and acceptance criteria.
-3. Planr links the build plan to source product plan requirement IDs.
-4. User runs `planr plan check`.
-
-Acceptance criteria:
-
-- REQ-UX-012: A build plan must be narrow enough to seed executable map items.
-- REQ-UX-013: Plan linking must show source plan id, requirement ids, derived plan path, and relationship.
-
-## Map Seeding Flow
-
-1. User runs `planr map build --from <plan>`.
-2. Planr creates candidate map items and links.
-3. User accepts, edits, or rejects candidates.
-4. Accepted items enter the map as pending/ready.
-
-Acceptance criteria:
-
-- REQ-UX-014: Plan work lists must not silently become live map work without acceptance.
-- REQ-UX-015: Seeded items must retain links to their source product or build plan requirements.
-
-## Agent Execution Flow
-
-1. Agent calls `planr_pick_item` or `planr pick`.
-2. Planr returns item, linked plan context, upstream handoff, relevant contexts, and conflicts.
-3. Agent works in repo.
-4. Agent records log.
-5. Agent closes the item when log and reviews allow it.
-6. Planr promotes downstream items.
-7. If review is required, a review item becomes ready.
-
-Acceptance criteria:
-
-- REQ-UX-020: The pick response must fit in an LLM context window by default and include links for deeper reads.
-- REQ-UX-021: Closure must show unlocked items and remaining blockers.
-- REQ-UX-022: Agents must treat parent gate items as completion gates and work executable child items when a child implementation or test item exists.
-
-## Parent Gate Flow
-
-1. User or agent creates a parent item for the material change.
-2. User or agent breaks the parent into implementation or test child work with `planr item breakdown`.
-3. User or agent requests review on the implementation or test child after evidence exists.
-4. Downstream top-level work depends on the parent gate when review cleanliness matters.
-5. Parent closes only after child work closes and review findings have either passed or been converted into fix/follow-up review work.
-
-Acceptance criteria:
-
-- REQ-UX-025: Parent item detail must make clear whether open children or reviews block closure.
-- REQ-UX-026: Recovery views must show the child implementation, review, logs, and blockers needed to continue safely.
-
-## Review/Fix Flow
-
-1. Review item is picked.
-2. Reviewer inspects linked plan, log, and scoped Git diff.
-3. Reviewer returns verdict:
-   - complete;
-   - not complete with findings;
-   - unclear/partially verified.
-4. Findings create fix item and follow-up review item.
-5. Parent closes only when review chain passes.
-
-Acceptance criteria:
-
-- REQ-UX-030: Review findings must be visible in item detail and log detail.
-- REQ-UX-031: Parent completion must explain which review item blocks it.
-
-## Handoff And Story Flow
-
-1. Agent records proof with `planr log add`.
-2. Agent records reusable discoveries with `planr context add`.
-3. Agent records task-local coordination with `planr note add`.
-4. If the decision chain is too long for logs and contexts, the operator creates or updates a story log.
-
-Acceptance criteria:
-
-- REQ-UX-035: Logs must remain the proof surface for closure.
-- REQ-UX-036: Context entries must be searchable and safe to expose to future agents.
-- REQ-UX-037: Story logs must be documented as narrative memory and must not override map state.
-
-## Error, Empty, Offline, Loading States
-
-- No project: show `planr project init`.
-- No ready item: show blockers and critical lane.
-- Database locked: show retry and owning process if known.
-- Plan parse error: show file path, line if available, and keep graph usable.
-- MCP client missing: show manual config.
-- Agent command failed: record failed run and keep task recoverable.
-
-## Settings, Export, Delete, Account Flows
-
-- No account settings in V1.
-- Settings live in `.planr/config.toml` or user config.
-- Export includes database dump, plan files, reviews, and references.
-- Delete requires explicit project id or path and confirmation.
-
-## Accessibility Behavior
-
-- CLI output must support `--json` and no-color mode.
-- TUI/dashboard must support keyboard navigation, visible focus, screen-reader labels, and reduced motion.
-
-## Localization Behavior
-
-- V1 command output is English.
-- User-authored plan content may be any language.
-- Error codes are stable and machine-readable.
-
-## Acceptance Criteria
-
-- REQ-UX-900: Every primary flow must be executable without a web UI.
-- REQ-UX-901: Every mutation must have a JSON mode for automation.
-- REQ-UX-902: Every blocked state must show the next actionable command or reason.

package/docs/release-candidates/planr-v1.5.2.md

@@ -1,164 +0,0 @@
-# Planr v1.5.2 Release Candidate Evidence
-
-Candidate produced on 2026-07-20 in an isolated local workspace:
-
-- Workspace: `/Users/kregenrek/projects/planr-dogfood/release-v1.5.2`
-- Source clone: `/Users/kregenrek/projects/planr-dogfood/release-v1.5.2/release-candidate-src`
-- Local bare remote: `/Users/kregenrek/projects/planr-dogfood/release-v1.5.2/local-origin.git`
-- Config-proof rerun source clone: `/Users/kregenrek/projects/planr-dogfood/release-v1.5.2/config-proof/release-candidate-src`
-- Config-proof rerun local bare remote: `/Users/kregenrek/projects/planr-dogfood/release-v1.5.2/config-proof/local-origin.git`
-- Config-proof hash snapshots: `/Users/kregenrek/projects/planr-dogfood/release-v1.5.2/config-proof/evidence`
-- Public side effects: none. The candidate clone's `origin` points to the local bare remote, and the public `origin` check from this repository returned no `v1.5.2` tag.
-
-## Identity
-
-- Upstream release-scope base commit: `f7763c6197ddf8cdd93227b9aa320f2b168a0523`
-- Clean pre-release source commit: `9390af541ca51755e585bf3c1a652717997daeca`
-- Clean pre-release source tree: `2569374e6321a88b812cc706257bbda086101437`
-- Release commit: `678038db4536723867fc96b0cd0af703fda43ef1`
-- Release tree: `80324b8afef14d7d7bd97950eb8352cd9c667e6a`
-- Annotated tag object: `12c78b7a870552361b11c5de768a6c5da7c8f115`
-- Tag target: `678038db4536723867fc96b0cd0af703fda43ef1`
-- Config-proof rerun release commit: `0d6bab060793fd52a5e144b9862c1fbc77d10ec3`
-- Config-proof rerun release tree: `80324b8afef14d7d7bd97950eb8352cd9c667e6a`
-- Config-proof rerun annotated tag object: `78c6c99afbca24803d58abb7d9a507cafde40741`
-- Config-proof rerun tag target: `0d6bab060793fd52a5e144b9862c1fbc77d10ec3`
-
-## Version Checks
-
-Both runtime entry points reported `planr 1.5.2`:
-
-- `target/release/planr --version`
-- `node npm/bin/planr.js --version`
-
-All release manifests carried `1.5.2`:
-
-- `Cargo.toml`
-- `package.json`
-- `plugins/planr/.codex-plugin/plugin.json`
-- `plugins/planr/.claude-plugin/plugin.json`
-- `.cursor-plugin/plugin.json`
-
-## Artifact Digests
-
-- Native binary `target/release/planr`: `e91917be04e84f97c5d515e673f829c33b21f5128dae87ce836e3721ece50473`
-- npm tarball `planr-1.5.2.tgz`: `33df443e6ec20d6d44fcf05469efe56eb75b192c826467c33d47d44672297a34`
-- Native archive `dist/planr-darwin-arm64.tar.gz`: `6fdaf803073d99bdb02522100e50094fb277409d52fc3a0c33e9d8bd6707d8ac`
-- Archive checksum file `dist/SHA256SUMS`: `6347103b757e5045aef9a83a311ae2bcc43de5b6e9ada8a9efa2d52b84e3359b`
-- Payload checksum file `dist/planr-1.5.2/SHA256SUMS`: `d8ac952c247706bb328e1539583b87e55f9e2b211b89c134aab08357d0cc665c`
-- Config-proof rerun native binary `target/release/planr`: `00c1b3b46f66563dfe4c909e2ecb75dc448e72bfe75b6cb7d56d86c6539b5d6c`
-- Config-proof rerun npm tarball `planr-1.5.2.tgz`: `33df443e6ec20d6d44fcf05469efe56eb75b192c826467c33d47d44672297a34`
-- Config-proof rerun native archive `dist/planr-darwin-arm64.tar.gz`: `dbba6abece2cc37d1b7e038094b8b7483ce79e5c770f8ed64048c84446d17681`
-- Config-proof rerun archive checksum file `dist/SHA256SUMS`: `1d77872f58c8ef8877cbed11b16ab0ea30524a6b2a9565f5190dfd059d69416c`
-- Config-proof rerun payload checksum file `dist/planr-1.5.2/SHA256SUMS`: `ce2adbe238c9fe27838c11f3a89195d9eb8b262411c86d3a8b02304ee14eaec6`
-
-`dist/SHA256SUMS` records:
-
-```text
-6fdaf803073d99bdb02522100e50094fb277409d52fc3a0c33e9d8bd6707d8ac  planr-darwin-arm64.tar.gz
-```
-
-`dist/planr-1.5.2/SHA256SUMS` records:
-
-```text
-e91917be04e84f97c5d515e673f829c33b21f5128dae87ce836e3721ece50473  planr
-a1e27e1cfb3d9d540dfe05f5d1212ee98be97b1f48e203d48209e31243383ba3  README.md
-61a9b281d04d62cdea4bef57d5e0b702c191b3219456409ac5ed651569228a30  LICENSE.md
-```
-
-## Gates Run
-
-- `scripts/release.sh 1.5.2 'standalone Planr core with optional Switchloom handoff'`
-  - `cargo test`: 71 unit tests, 67 e2e tests, and 3 routing ownership tests passed.
-  - `npm pack --dry-run`: reported `planr@1.5.2`, 65 files, shasum `a3903ce5658be6f6140321232885f86f6515ae70`.
-  - `scripts/security-local.sh`: betterleaks found no leaks; Trivy reported 0 vulnerabilities for `Cargo.lock` and `pnpm-lock.yaml`.
-  - Pushed `main` and `v1.5.2` only to `/Users/kregenrek/projects/planr-dogfood/release-v1.5.2/local-origin.git`.
-- `scripts/build-release.sh`: built `dist/planr-darwin-arm64.tar.gz`.
-- `npm pack`: created `planr-1.5.2.tgz` locally; no npm publish was run.
-- Config-proof rerun:
-  - `scripts/release.sh 1.5.2 'standalone Planr core with optional Switchloom handoff'`: 71 unit tests, 67 e2e tests, and 3 routing ownership tests passed; betterleaks found no leaks; Trivy reported 0 vulnerabilities; pushed only to `/Users/kregenrek/projects/planr-dogfood/release-v1.5.2/config-proof/local-origin.git`.
-  - `scripts/build-release.sh`: built `dist/planr-darwin-arm64.tar.gz`.
-  - `npm pack`: created `planr-1.5.2.tgz` locally; no npm publish was run.
-  - `target/release/planr --version` and `node npm/bin/planr.js --version`: both reported `planr 1.5.2`.
-- `git tag -l v1.5.2`: returned no local tag in `/Users/kregenrek/projects/planr`.
-- `git ls-remote --heads --tags origin 'v1.5.2'`: returned no public remote ref.
-- Candidate clone artifact inventory: no Switchloom files, no legacy routing-owner directories, and no routing manifests were present.
-
-## User Config Hash Proof
-
-No release command targeted user/global host config files. The config-proof rerun captured hashes immediately before and after each release-owned run, stored without file contents:
-
-- `scripts/release.sh`
-  - Before: `/Users/kregenrek/projects/planr-dogfood/release-v1.5.2/config-proof/evidence/config-before-release-sh.txt`
-  - After: `/Users/kregenrek/projects/planr-dogfood/release-v1.5.2/config-proof/evidence/config-after-release-sh.txt`
-  - Equality proof: `/Users/kregenrek/projects/planr-dogfood/release-v1.5.2/config-proof/evidence/config-release-sh-equality.txt` records `config hashes unchanged across scripts/release.sh`.
-- `scripts/build-release.sh`
-  - Before: `/Users/kregenrek/projects/planr-dogfood/release-v1.5.2/config-proof/evidence/config-before-build-release.txt`
-  - After: `/Users/kregenrek/projects/planr-dogfood/release-v1.5.2/config-proof/evidence/config-after-build-release.txt`
-  - Equality proof: `/Users/kregenrek/projects/planr-dogfood/release-v1.5.2/config-proof/evidence/config-build-release-equality.txt` records `config hashes unchanged across scripts/build-release.sh`.
-- `npm pack`
-  - Before: `/Users/kregenrek/projects/planr-dogfood/release-v1.5.2/config-proof/evidence/config-before-npm-pack.txt`
-  - After: `/Users/kregenrek/projects/planr-dogfood/release-v1.5.2/config-proof/evidence/config-after-npm-pack.txt`
-  - Equality proof: `/Users/kregenrek/projects/planr-dogfood/release-v1.5.2/config-proof/evidence/config-npm-pack-equality.txt` records `config hashes unchanged across npm pack`.
-
-Every before/after snapshot contains the same hashes:
-
-- `/Users/kregenrek/.codex/config.toml`: `82224997e7d4d5147f892a8aa12f7f5f04e77c38267da6ba1274a9267b23f040`
-- `/Users/kregenrek/.claude/settings.json`: `99a0eb17993d0dd0c952df03bec38d284fd119a9b0ed928f3201b1792224049f`
-- `/Users/kregenrek/.claude.json`: `a5f901ce3b38943ed2591333b4cb6dbab0cab101f8d02ea348fc476021f55afb`
-- `/Users/kregenrek/.cursor/mcp.json`: `cf7217adfcb48b532dfdbced62ca68eab4c60996ef38d510a8efb3d286ce5baf`
-
-## Switchloom v0.2.1 Optional Dogfood Evidence
-
-Fresh non-replay dogfood ran on 2026-07-20 with the release-candidate Planr v1.5.2 binary and exact public Switchloom v0.2.1 bytes. The durable local audit receipt is:
-
-- Receipt: `/private/tmp/planr-switchloom-cross-product-QEvWps/oracle-receipt.json`
-- Receipt SHA-256: `c01f4b980977a15028f7a82cc6fc237aa50fb4b35310871ba3ad245ec1c699ee`
-- Mode/result: `live`, `ok=true`
-- Fresh root: `/private/tmp/planr-switchloom-cross-product-QEvWps`
-
-Replayable command:
-
-```bash
-PLANR_WORKER_ID=switchloom_optional_dogfood PLANR_BIN=/Users/kregenrek/projects/planr-dogfood/release-v1.5.2/release-candidate-src/target/release/planr SWITCHLOOM_TARBALL=/private/tmp/switchloom-public-0.2.1.MN008L/switchloom-0.2.1.tgz PLANR_ORACLE_TEMP_PARENT=/private/tmp node scripts/verify-switchloom-cross-product.mjs
-```
-
-Public Switchloom package identity:
-
-- Package: `switchloom@0.2.1`
-- Tarball: `/private/tmp/switchloom-public-0.2.1.MN008L/switchloom-0.2.1.tgz`
-- npm SHA-1 shasum: `e813283f54d0d64b5fd4835e17687aaaf3b0a6cb`
-- SHA-512 integrity: `sha512-vUKHxYXHt7Sx7MkYQz5MRZ0Ll544iHoadHGCgvJPUYkpUzQWtzjt1o3xhyeQwExCA6tuLQ5vZnLPz+fO5uMiXg==`
-- Local SHA-256: `028176063ce20b4981aa4e13199b25169b2f8296f648eeeec9291e6955e7549a`
-
-Host routing evidence from the receipt:
-
-- Codex CLI: `codex-cli 0.144.5`
-- Maker role/model/effort: `model_routing_terra_high`, `gpt-5.6-terra`, `high`
-- Reviewer role/model/effort: `model_routing_sol_high`, `gpt-5.6-sol`, `high`
-- `fork_turns_all_used`: `false`
-- Public Codex JSONL: `/private/tmp/planr-switchloom-cross-product-QEvWps/codex-live.jsonl`
-- Parent rollout: `/Users/kregenrek/.codex/sessions/2026/07/20/rollout-2026-07-20T20-05-19-019f80b4-2e89-7470-a432-6937ddcbc7ac.jsonl`
-- Maker rollout: `/Users/kregenrek/.codex/sessions/2026/07/20/rollout-2026-07-20T20-05-50-019f80b4-a7d3-73d1-bf34-9762ad7d9474.jsonl`
-- Reviewer rollout: `/Users/kregenrek/.codex/sessions/2026/07/20/rollout-2026-07-20T20-06-37-019f80b5-5d7f-7441-97f3-c743d97e0a8c.jsonl`
-
-Fresh Planr audit and uninstall evidence:
-
-- Fresh oracle plan: `pln-773f1d88`
-- Fresh oracle item: `i-build-first-slice-5c85`
-- Audit result: holds with clauses `items_settled`, `reviews_complete`, `approvals_clear`, and `verification_logged`.
-- Post-uninstall result: Switchloom uninstall removed only managed files and unrouted Planr still worked; the script reran the Planr audit after uninstall and required `holds=true`.
-- Requested-only routing metadata was rejected as effective proof: `/private/tmp/planr-switchloom-cross-product-QEvWps/requested-only-route-audit.json`.
-
-Protected configuration and source inventory proof:
-
-- `/Users/kregenrek/.codex/config.toml`: `82224997e7d4d5147f892a8aa12f7f5f04e77c38267da6ba1274a9267b23f040`
-- `/Users/kregenrek/.claude/settings.json`: `99a0eb17993d0dd0c952df03bec38d284fd119a9b0ed928f3201b1792224049f`
-- `/Users/kregenrek/.claude.json`: `a5f901ce3b38943ed2591333b4cb6dbab0cab101f8d02ea348fc476021f55afb`
-- `/Users/kregenrek/.cursor/mcp.json`: `cf7217adfcb48b532dfdbced62ca68eab4c60996ef38d510a8efb3d286ce5baf`
-- Switchloom source root: `/Users/kregenrek/projects/model-routing`
-- Switchloom source HEAD: `191f6aac91ff0f73fcae68ab269eb2d89c9e76e9`
-- Switchloom source status SHA-256: `2ca939e3e14ba8971210e93152120323641d21b0ac465b02a85335860b01758c`
-- Switchloom tracked files SHA-256: `0292bca86e80e9c63d5848984cab229b17df6e1162f1b0d8ec577474a9ac3591`
-
-This section records paths, digests, roles, and verification outcomes only. It does not copy rollout contents, prompts, responses, credentials, or user configuration contents into the repository.