openmerit 0.1.11 → 0.2.0

package/docs/security.md

@@ -1,5 +1,7 @@
 # Security
 
+**Pi adapter — npm 0.1.12 and later:** Pi 1.5.0 uses native MCP plus shared Scout rule/skill sections, not the former evaluation adapter. It never initiates login, changes the host model/tools/session, or provisions background jobs. Browser-approved credentials are independent per client/scope/project, stored privately outside the repository, and passed as MCP HTTP headers, never instructions. Pi's installed connection JSON contains only the private credential path. See [Pi paths and targeted removal](pi-extension.md). The standalone evaluation CLI remains separate.
+
 The [preview agent-evaluation runner](agent-evaluations.md) is a separate execution path: it runs trusted local agents/graders, passes only basic OS variables and explicitly named environment variables, and preserves agent-owned authentication. It sends task descriptions and optional model IDs to Scout. Local metric reports and budget reservations persist; temporary task outputs are removed. Fresh directories are not security sandboxes. Its budget admission controls do not enforce provider billing limits.
 
 The [budget selector](agent-evaluations.md#budget-selection) in `0.1.7-preview.2` requires an explicit $10, custom or no-fixed-cap choice after model scope. No fixed cap removes monetary admission limits, including Claude's per-attempt dollar flag, while retaining tasks, repetition bounds, timeouts, native permissions and accounting. Saved choices apply across reruns; a foreground watcher can incur further charges on each change until stopped. Provider limits remain independent.
@@ -8,27 +10,17 @@ The [budget selector](agent-evaluations.md#budget-selection) in `0.1.7-preview.2
 
 OpenMerit accepts no model-provider or Jev credential. Credentials belong to the coding harness, its environment, or an external secret store.
 
-Never place secrets in profiles, policies, intent constraints, summaries, evidence URIs, audit events, fixtures, traces, or committed environment files.
-
-## Mutation authorization
-
-Most intents carry `modelMutationAllowed: false`. Only application-target apply-swap and rollback intents can authorize a mutation, limited to the relevant proposal, prior configuration, and confirmed target ID. Pi's model is explicitly excluded. Automatic swaps require explicit policy opt-in and meeting the configured verified-swap threshold, which can be zero. Otherwise a proposal requires approval. Post-swap evaluation depends on the harness performing the checks and reporting their results. OpenMerit is not a sandbox around the harness's tools.
-
-Persistent wakeup provisioning is a separate authorization boundary. An adapter that needs to install a system scheduler, create a paid cloud agent, or change infrastructure must declare `wakeupProvisioning: "infrastructure_change"`; OpenMerit will not request that provisioning unless the confirmed check policy sets `infrastructureChangesAllowed: true`.
-
-The macOS Pi adapter installs a user LaunchAgent only under that authorization and persistent execution mode. The plist stores the project path, selected Pi model identifier, and executable paths, but no API key. It verifies that Pi authentication works without shell-only credentials before installing. The agent launches Pi headlessly only for due elapsed-time checks, so the configured model provider may receive project context and incur charges under the confirmed policy. Pause unloads the agent; already-running work is not cancelled.
-
-The background runner imposes a 15-minute wall-clock limit and records a nonzero status if Pi fails to complete a due intent. This is a safety bound, not a provider-spend cap. Unattended candidate discovery and model changes still need representative product validation.
+Never place secrets in evaluation configuration, task fixtures, Scout project policy, terminal configuration, activity exports, traces, or committed environment files.
 
 ## Local state
 
-`.openmerit/` may reveal task names, candidate identifiers, evidence locations, budgets, or model choices. Treat it as sensitive project metadata even though it must not contain credentials.
+`.openmerit/` may hold evaluation configuration, task fixtures, reports and budget usage, Scout project policy, and terminal configuration or activity exports. It may reveal task names, model choices, budgets or endpoint identifiers. Treat it as sensitive project metadata even though it must not contain credentials.
 
-Pi also records OpenMerit requests and results in its session history. Project context and evaluation data may be sent to the model providers, tools, and evidence systems configured in the harness. Local OpenMerit storage does not imply that all processing stays on your machine.
+With native Scout, Pi manages its own session/tool records and provider context; the adapter adds no separate evaluation-history store. Task descriptions sent to hosted Scout follow its data policy. Local OpenMerit storage does not imply that all processing stays on your machine.
 
 ## Evidence integrity
 
-OpenMerit validates structure and deterministic Pareto conformance, not the truth of arbitrary external evidence. Use authenticated observability, immutable artifacts, and digests where stronger provenance is required.
+OpenMerit does not establish the truth of imported or external evidence. Use authenticated observability, immutable artifacts, and digests where stronger provenance is required.
 
 Do not include credentials, private traces, or proprietary evaluation data in public issues.
 
@@ -55,6 +47,8 @@ The [coding-agent setup](scout.md#connect-a-coding-agent) in npm 0.1.7 uses host
 
 **Automatic instruction updates — version 0.1.10:** updater-enabled setup defaults on with an opt-out, installing asynchronous Claude Code startup/response-end hooks. Checks use npm's public stable registry without credentials, task content or installation IDs. SHA-512 verification checks package bytes against registry metadata; it does not defend against a compromised publisher/registry. The updater reads only a bounded instruction bundle, never executes downloaded code or package scripts, and leaves MCP configuration, keys, privacy settings and project policy unchanged. A supported release contract permits instruction updates; maintainers must change it when permissions or data handling change. This is a publisher assertion, not semantic validation of instructions. Edited files are retained, concurrent writes serialize, and journaled recovery stops on intervening edits. New sessions reliably load new instructions. See [automatic updates](scout.md#automatic-instruction-updates-version-0110) for cadence, offline retries, manual commands and the one-time bootstrap required for older installations. Availability follows npm publication independently of hosted releases.
 
+These update hooks are Claude Code only. The new Pi adapter installs none; updates require explicit targeted reinstall. Its `login`, `logout`, `status`, `remove` and `doctor` shell commands target the selected client/scope without revoking another installation's independent key.
+
 ### OpenMerit coding-agent reset — 23 October 2026
 
 **Historical reset, superseded by npm 0.1.7 and hosted device setup.** The reset temporarily removed the installer and MCP transport. The current [Claude Code setup](scout.md#connect-a-coding-agent) uses browser-approved, device-specific keys scoped to MCP recommendations, not pasted session tokens or agent OAuth. The key is stored locally in mode-600 credentials and Claude Code's plain-text MCP configuration. Setup installs an owned Scout skill; conflicts are not overwritten, and removal revokes the device key. Browser Google/GitHub sign-in remains separate.

package/docs/testing.md

@@ -1,5 +1,7 @@
 # Testing and validation
 
+**Pi adapter — npm 0.1.12 and later:** the Pi 1.5.0 adapter uses native Scout MCP and shared guidance only. Dated acceptance records below describe the packages tested at the time; some mention package exports that have since been removed. Standalone evaluation tests remain separate.
+
 ## Stable 0.1.7 acceptance — 24 October 2026
 
 Published `openmerit@0.1.7` to npm's `latest` channel after full repository verification: 757 passing tests, one existing skip, syntax/type checks, builds and documentation checks. The `preview` tag remains `0.1.7-preview.5`. A fresh registry installation on macOS ARM64 with Node.js 22.23.1 matched the tested 104-file tarball byte-for-byte. Packed core/protocol/Pi exports and the installed terminal runtime smoke checks passed, including passive collection, source removal, runtime outage/recovery and shutdown.
@@ -32,7 +34,7 @@ The final production deployment passed **203/203 VM assertions and 8/8 filter/am
 
 The published `0.1.7-preview.4` package passed the full repository verification, including 329 Scout tests and documentation checks. Its packaged runtime is byte-for-byte unchanged from preview.3; version metadata and public guides carry this release. Registry integrity matches the reviewed tarball, the `preview` tag resolves to this version, and stable `latest` remains `0.1.6`. Scout deploys independently and its UI files are unchanged. Broader evidence coverage, task calibration and complete quality/cost/latency validation remain follow-up work.
 
-The hosted beta's public post-deployment suite passed 9/11 cases. Explicit SVG generation returned no shortlist; a Qwen-family code-authoring request admitted tool-calling evidence. Restriction checks passed for creator, family, context and dates, including known matches and impossible-context no-match. The actual bird prompt also displayed five recommendations in a browser. Earlier candidate deadline and interpretation failures are retained in the [Scout validation record](scout.md#task-relevance-corrections-hosted-beta-17-october-2026). These checks do not establish universal semantic reliability or improved task accuracy.
+The hosted beta's public post-deployment suite passed 9/11 cases. Explicit SVG generation returned no shortlist; a Qwen-family code-authoring request admitted tool-calling evidence. Restriction checks passed for creator, family, context and dates, including known matches and impossible-context no-match. The actual bird prompt also displayed five recommendations in a browser. Earlier candidate deadline and interpretation failures were recorded separately at the time. These checks do not establish universal semantic reliability or improved task accuracy.
 
 Fresh registry installation in the existing Ubuntu ARM64 Lima VM verified all 101 packaged file hashes, registry integrity and public core/protocol/Pi exports. Seven workloads were sent through both HTTP and the official MCP SDK. Six of those fourteen requests failed their functional expectations: books/posters and invoice HTTP requests returned unavailable responses, while SQL generation and safety classification with rewriting returned empty shortlists through both interfaces. The matching MCP books/posters and invoice requests succeeded; bird identification, label-only classification and unsupported audio behaved as expected. The first harness stopped when it assumed SQL had returned an endpoint. A separate continuation tested exact endpoint scope using the successful bird result, request/protocol errors and installed CLI planning, preserving all original failures. Together the runs recorded 187 passing checks and nine failed assertions, including duplicate agreement failures caused by unavailable responses and an installed-CLI candidate check. Both CLI email and SQL plans were empty. Planning created no execution or spend state, and the existing global VM installation was retained. This is not a clean acceptance pass. The seven first HTTP workload requests had a median wall time of 4.924 seconds and a maximum of 6.229 seconds, including unavailable responses; repeated cached requests were faster.
 
@@ -58,14 +60,6 @@ npm pack --dry-run
 
 `verify` runs workspace tests, syntax checks, strict TypeScript checks and the TypeScript migration ratchet, the package build, demo tests, generated-documentation checks, and whitespace validation. It does not publish a package or deploy the website.
 
-## Coordinator and Pi coverage
-
-Automated tests cover protocol contracts, task-specific sampling, application-target binding, setup and post-build target detection, incumbent identity, deterministic baseline sufficiency, durable candidate/assessment handoffs, frontier conformance, approval, swap and rollback requests, persistence, evidence requirements, budget accounting, and audit redaction.
-
-Automation coverage includes task and elapsed cadence, signal idempotency, durable pending work, catalogue changes, regression thresholds, delayed post-swap checks, scheduler capability gaps, and persistent pause. Pi's own usage and coding checkpoints are not counted as application measurements.
-
-The disposable-project test in `packages/pi/test/live-wakeup.test.ts` verifies that a due, insufficient baseline is recorded without starting Pi. Scheduler tests validate managed LaunchAgent configuration and authorization boundaries. They do not establish reliable unattended candidate discovery, comparison, or swapping; those require a representative headless product trial.
-
 ## Inference Terminal coverage
 
 ```sh
@@ -74,35 +68,15 @@ npm test --workspace=@openmerit/terminal
 
 Tests cover metadata projection and redaction, source containment, recursive syntax indexing, phased worker progress, incremental reuse, coverage limits, endpoint classification, authorized loopback probes, supported request-log formats, UTF-8 boundaries, rotation/truncation, source reconciliation, historical ranges, unknown versus zero measurements, and the read-only API.
 
-Inventory and UI coverage includes model/service identity, explicit deployment and host links, shared capacity, stale/missing hardware, path classification, map completeness, search and filtering, preference-dependent demo decisions, and preservation of unknown costs. Runtime fixtures establish which endpoints collectors call; they do not prove compatibility with every external runtime version.
-
-The three fictional scenarios are separate:
-
-| Scenario | Agents | Tasks | Models / offers | Requests |
-| --- | ---: | ---: | --- | ---: |
-| Local sample (`--demo` or sample selector) | 40 | 140 | 21 models | 9,600 over 24 hours |
-| Hosted enterprise sample | 200 | 699 | 21 models | 9.6 million over 30 days |
-| Hosted before/after comparison | 280 | 980 | 26 reviewed offers across six services; assignments depend on preference | 9.6 million over 30 days |
+Inventory and UI coverage includes model/service identity, explicit deployment and host links, shared capacity, stale/missing hardware, path classification, map completeness, search and filtering, and preservation of unknown costs. Runtime fixtures establish which endpoints collectors call; they do not prove compatibility with every external runtime version.
 
-The comparison tests preserve workload and token volume across all six preferences, enforce service/output compatibility, disclose benchmark/efficiency overrides, and verify modeled costs. Sample tests exercise interface scale and arithmetic, not measured throughput, application quality, or hardware performance.
+The local fictional sample (`--demo` or the sample selector) has 40 agents, 140 tasks, 21 models and 9,600 requests over 24 hours. Sample tests exercise interface scale and arithmetic, not measured throughput, application quality, or hardware performance.
 
-Browser review covers the six views, inspectors, search, activity ranges, map and chart interaction, keyboard navigation, reduced motion, and desktop/narrow layouts. The source light/dark change has local browser verification; it is not yet published to npm or the hosted site. Browser checks are distinct from the committed unit suite.
+Browser review covers the six views, inspectors, search, activity ranges, map and chart interaction, keyboard navigation, reduced motion, and desktop/narrow layouts. Browser checks are distinct from the committed unit suite.
 
 ## Pi load and package smoke tests
 
-```sh
-./node_modules/.bin/pi --no-session --no-extensions -e ./packages/pi/src/index.ts --list-models
-```
-
-This checks extension loading and catalogue enumeration, not successful provider authentication or a completed product intent. CI also packs the package, installs it in a temporary directory, imports the core/protocol entry points, and loads the installed extension.
-
-## Experimental sandbox
-
-`npm run demo` builds a disposable sentiment-classification application through Pi and runs live provider calls. It requires Pi 0.87 with OpenRouter authentication and an application OpenRouter credential. It is separate from the fictional dashboard comparison and from the recorded website player.
-
-The runner collects a baseline, interleaves incumbent/challenger calls on the prepared cases, records cost/token/latency evidence, submits results to the coordinator, and exercises a change and fresh checks in the temporary app. Missing usage, invalid output, or exhausted allowance stops the run. The default application-spend threshold is $1, checked after responses; Pi's own coding-model spend is excluded. This is not an in-flight provider cutoff.
-
-The default models are `openai/gpt-4.1-mini` and `openai/gpt-4o-mini`. The runner supports `OPENMERIT_DEMO_BASELINE_MODEL`, comma-separated `OPENMERIT_DEMO_CANDIDATE_MODELS`, `OPENMERIT_DEMO_PI_MODEL`, `OPENMERIT_DEMO_REPETITIONS` (2–5), `OPENMERIT_DEMO_MAX_SPEND_USD` (up to $5), and `OPENMERIT_DEMO_SEED`. The printed temporary directory retains the app, plan, lifecycle state, per-call artifacts, comparison manifest, and summary. Small prepared examples do not establish representative product reliability.
+CI packs the package, installs it in a temporary directory, imports `openmerit/pi`, smoke-tests the installed terminal command, and loads the installed extension in Pi with `--list-models`. These checks establish packaging and loading, not successful provider authentication or Scout recommendations.
 
 ## What evidence establishes
 
@@ -111,7 +85,7 @@ The default models are `openai/gpt-4.1-mini` and `openai/gpt-4o-mini`. The runne
 - **Product trial verified:** a representative application completes the workflow with inspected evidence.
 - **Production verified:** repeated representative runs support the claimed operating conditions and reliability.
 
-Implementation checks, historical demo recordings, and public model benchmarks cannot substitute for target-product validation. See [current limitations](roadmap.md) before relying on unattended changes.
+Implementation checks and public model benchmarks cannot substitute for target-product validation. See [current limitations](roadmap.md).
 
 
 ## Agent-evaluation preview validation — 15 October 2026

package/docs/troubleshooting.md

@@ -1,55 +1,50 @@
 # Troubleshooting
 
-Start with the current status and the local audit trail. These show what OpenMerit requested, what the harness reported, and which evidence references were recorded.
+The Pi Scout adapter requires OpenMerit **0.1.12** or newer and targets Pi **1.5.0**. Check the resolved package version when using `@latest`. The removed Pi 0.87 `/openmerit` workflow is not a diagnostic path for the replacement.
 
-```text
-/openmerit status
-/openmerit doctor
-/openmerit logs
-```
-
-## The command is missing
+## Scout is missing in Pi
 
-Check that OpenMerit is installed and enabled in Pi:
+Run targeted checks in your shell:
 
 ```sh
-pi list
+npx -y openmerit@latest status --client pi --scope user --check
+npx -y openmerit@latest doctor --client pi --scope user
 ```
 
-The published extension targets Pi 0.87 and Node.js 22.19 or newer. Follow [getting started](getting-started.md) to install it, then start Pi in your product repository.
-
-## Setup did not begin
+Use `--scope project` from the original project root for project setup. Check Pi and Node.js versions against [setup](getting-started.md), complete browser device approval, then start a **new session**. Installing the npm package or reconnecting an old session does not load new extension instructions. For SDK embedding, load Pi's `createMcpExtension()` explicitly alongside `createScoutPiExtension`; the Scout factory alone is not an MCP runtime.
 
-Automatic setup requires an unconfigured project, an interactive Pi UI, and a bounded source-detection match for an application LLM call. Non-interactive runs do not start the confirmation flow, and a project without a detected target remains idle until `/openmerit setup` is requested. Existing project state or active work may also prevent a fresh setup request.
+## The connection configuration is invalid
 
-Inspect status first. If no intent is active, use `/openmerit setup` to request setup explicitly; this is also the supported correction path when source detection or a prior setup recorded the wrong incumbent. A new setup preserves audit history but replaces the active task profile, candidate/assessment handoffs, frontier, and baseline state after the new result is accepted. Do not delete `.openmerit/` as a routine reset: it contains your policy, lifecycle state, evidence references, and audit history.
+The installed extension reads `openmerit-scout.json` beside its bundle; that file points to a private credential file outside the repository. Do not put the key in the extension or prompt. Check the scope and configuration-directory overrides against [installed paths](pi-extension.md#installed-files-and-credentials). Reinstall explicitly to repair missing owned files:
 
-## Evidence is missing or incomplete
+```sh
+npx -y openmerit@latest install --client pi --scope user
+```
 
-A task profile is not the same as working telemetry. Ask Pi which required metrics are uncovered, where their measurements should come from, and which evaluation artifacts have been run. Normal coding checkpoints do not replace those measurements.
+Expired or revoked credentials require targeted `login` followed by reinstall. The adapter reports a sanitized setup diagnostic; it never starts sign-in on its own. Approve only a browser code you initiated.
 
-The [metrics guide](metrics-and-evidence.md) explains missing and insufficient evidence. More samples or instrumentation may be needed before a candidate can be compared.
+## Installation reports a conflict
 
-## A result was rejected
+The installer does not overwrite edited or unowned files. Inspect and preserve your changes before resolving the conflict. Also check for overlapping Pi user/project installations or an existing `openmerit` MCP entry. Remove the unwanted owned installation using its own scope; do not revoke a different client's key as a repair. Disable the old `npm:openmerit` Pi registration when migrating from 0.87.
 
-Read the validation error and audit event. Successful work needs evidence references and the output structure required by that intent. Frontier results must match the task and product revisions, identify their assessments, and satisfy the comparison rules.
+## The adapter did not update automatically
 
-Have the harness correct the measurement or output problem. Do not mark an intent successful merely to advance the workflow.
+That is expected. Pi has no OpenMerit auto-update hooks. Explicitly rerun `install --client pi` with the original scope, then start a new session. Claude Code's update settings do not configure Pi.
 
-## Work appears stuck after a restart
+## `/openmerit` or evaluation tools are missing
 
-Pending or active intent state is durable. Inspect `state.json` and `events.jsonl` using the paths from `/openmerit logs`, and ask the harness to reconcile that work with the current session before requesting another intent. The current adapter may need supervised recovery; automatic completion after a restart is not guaranteed.
+They were removed, not renamed. The Pi adapter now supplies only native Scout MCP and shared guidance. It does not set up evaluations, recover intents, schedule work, swap models, or install a LaunchAgent. Existing legacy background jobs must be removed separately; installing the new adapter is not evidence that they stopped. Preserve old evaluation state and audit files if needed. For new evaluations use [the standalone CLI](agent-evaluations.md).
 
-## Checks are not running while Pi is closed
+## Scout was not consulted or its evidence is insufficient
 
-On macOS, check that the confirmed policy requests persistent execution and allows infrastructure changes, that the Mac user is logged in, and that Pi authentication works without shell-only credentials. `/openmerit doctor` reports scheduler diagnostics; `.openmerit/scheduler-status.json` records completed wakeups and failures. An active pause unloads the managed LaunchAgent. Other platforms need an external scheduler. A successful schedule does not establish that model-driven work completed. See [automatic checks](automation.md).
+The rule and skill are model guidance, not a guaranteed tool gate. Confirm they loaded in a new session and that the host permits the MCP tools. When project model policy is missing, ask the user; when Scout is unavailable or lacks suitable evidence, pause the model choice rather than invent a result. Host model/tool/session restrictions remain authoritative. Scout candidates are not measurements of your application's quality.
 
-## Work continues after pausing
+## Evaluation or terminal problems
 
-Pause is durable and gates automatic work, but an already-active intent can continue and explicit commands remain available. Inspect the active intent and audit timestamps to distinguish prior work from a new automatic dispatch. `/openmerit cancel` records abandonment; it does not terminate a provider request or harness process. The standalone terminal is independent of Pi pause; stop its CLI with Ctrl+C to stop collection. If a new automatic intent starts while the persisted pause is active, record a sanitized reproduction and your installed version.
+The standalone products are separate from Pi setup. Use [agent-evaluation diagnostics](agent-evaluations.md) for tasks, graders, budgets and execution blocks, or [terminal diagnostics](inference-terminal.md) for missing inventory and request evidence. A populated dashboard is not proof of successful evaluations. Never mark missing or rejected evidence successful merely to advance a workflow.
 
 ## Report a reproducible problem
 
-Include the OpenMerit, Pi, and Node.js versions, the triggering command or signal, the lifecycle stage, and a sanitized error. Remove credentials, private traces, and proprietary evaluation data before sharing anything in a public issue.
+Include OpenMerit, Pi and Node.js versions, the client/scope, the triggering command, and a sanitized error. Remove credentials, private paths, prompts and proprietary data before sharing. Do not attach credential or connection files containing private configuration.
 
 [Open an issue on GitHub](https://github.com/laz-aslam/openmerit/issues)

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "openmerit",
-  "version": "0.1.11",
+  "version": "0.2.0",
   "description": "Evidence-driven model decisions for coding harnesses.",
   "type": "module",
   "bin": {
@@ -11,12 +11,9 @@
     "pi-package",
     "pi-extension",
     "model-routing",
-    "evaluation",
-    "pareto-frontier"
+    "evaluation"
   ],
   "files": [
-    "dist/core/",
-    "dist/protocol/",
     "dist/pi/",
     "dist/terminal/",
     "dist/eval/",
@@ -26,18 +23,6 @@
     "README.md"
   ],
   "exports": {
-    ".": {
-      "types": "./dist/core/src/index.d.ts",
-      "default": "./dist/core/src/index.js"
-    },
-    "./core": {
-      "types": "./dist/core/src/index.d.ts",
-      "default": "./dist/core/src/index.js"
-    },
-    "./protocol": {
-      "types": "./dist/protocol/src/index.d.ts",
-      "default": "./dist/protocol/src/index.js"
-    },
     "./pi": {
       "types": "./dist/pi/src/index.d.ts",
       "default": "./dist/pi/src/index.js"
@@ -77,7 +62,6 @@
     "deploy": "node scripts/deploy.ts",
     "deploy:status": "node scripts/deploy.ts status",
     "build": "node scripts/build.mjs",
-    "demo": "node scripts/demo.mjs",
     "predash": "node scripts/build-terminal.mjs",
     "dash": "node packages/terminal/src/cli.mjs dash",
     "build:docs": "node scripts/build-docs.mjs",
@@ -87,24 +71,19 @@
     "prepare": "npm run build",
     "verify": "npm test && npm run check && npm run typecheck && npm run check:typescript && npm run build && npm run check:demo && npm run check:scout && npm run check:docs && npm run build:scout && git diff --check",
     "prepublishOnly": "npm run verify",
-    "build:dash-preview": "node scripts/build-terminal-preview.mjs",
-    "deploy:dash-preview": "node scripts/deploy.ts terminal-preview",
     "scout": "node scout/dev.mjs",
     "scout:refresh": "node scout/refresh.mjs",
     "check:scout": "node --test scout/test/*.test.mjs scout/test/*.test.ts && node --check scout/worker.mjs",
     "build:scout": "node scripts/build-scout.mjs"
   },
   "dependencies": {
-    "@earendil-works/pi-ai": "0.87.0",
     "@iarna/toml": "2.2.5",
     "@lezer/javascript": "1.5.6",
     "@lezer/python": "1.1.19",
-    "hyparquet": "1.31.5",
-    "typebox": "1.3.27",
     "yaml": "2.9.1"
   },
   "peerDependencies": {
-    "@earendil-works/pi-coding-agent": ">=0.87.0 <0.88.0"
+    "@earendil-works/pi-coding-agent": "1.5.0"
   },
   "peerDependenciesMeta": {
     "@earendil-works/pi-coding-agent": {
@@ -112,16 +91,15 @@
     }
   },
   "devDependencies": {
+    "@earendil-works/pi-coding-agent": "1.5.0",
     "@clerk/backend": "3.26.1",
     "@clerk/shared": "4.41.0",
-    "@lezer/highlight": "1.2.5",
     "@resvg/resvg-js": "2.6.2",
     "@types/markdown-it": "14.1.2",
     "@types/node": "^22.18.6",
-    "@xyflow/react": "12.12.0",
-    "elkjs": "0.12.0",
     "esbuild": "0.28.2",
     "fflate": "0.8.2",
+    "hyparquet": "1.31.5",
     "liveline": "0.0.7",
     "markdown-it": "15.0.2",
     "miniflare": "5.20260921.0-alpha",
@@ -130,6 +108,7 @@
     "react": "19.3.0",
     "react-dom": "19.3.0",
     "torph": "0.1.3",
+    "typebox": "1.3.27",
     "typescript": "^5.9.3",
     "web-vitals": "6.2.3",
     "wrangler": "4.136.3"

package/dist/core/src/index.d.ts

@@ -1,101 +0,0 @@
-import type { AnyIntentResult, AutomationPlan, AutomationSignal, CandidateAssessment, FrontierSnapshot, HarnessCapability, HarnessDescriptor, HarnessDispatchReceipt, HarnessWakeupRequest, TaskProfile, ImprovementCycleState, IntentLifecycleUpdate, IntentKind, OpenMeritIntent, OpenMeritProjectConfig, OpenMeritProjectState, ObservabilityCoverage, JsonValue, SupervisedGraduationPolicy } from "../../protocol/src/index.ts";
-import type { OpenMeritStore } from "./store.ts";
-export { OPENMERIT_DIRECTORY, ProjectStore, type AuditEventExporter, type OpenMeritStore, type ProjectStoreOptions, } from "./store.ts";
-export interface HarnessAdapter {
-    readonly descriptor: HarnessDescriptor;
-    dispatch(intent: OpenMeritIntent): Promise<HarnessDispatchReceipt>;
-    scheduleWakeup?(request: HarnessWakeupRequest): Promise<HarnessDispatchReceipt>;
-}
-export interface IntentFactoryOptions {
-    readonly taskProfileId?: string | undefined;
-    readonly authorizationPolicyId?: string;
-    readonly policy?: SupervisedGraduationPolicy | undefined;
-    readonly id?: string;
-    readonly requestedAt?: string;
-    readonly evaluationSpend?: number | undefined;
-    readonly targetId?: string | undefined;
-    readonly additionalConstraints?: Readonly<Record<string, JsonValue>>;
-}
-export declare function createOpenMeritIntent(kind: IntentKind, options?: IntentFactoryOptions): OpenMeritIntent;
-export declare function missingHarnessCapabilities(descriptor: HarnessDescriptor, kind: IntentKind): readonly HarnessCapability[];
-export declare function validateHarnessDescriptor(descriptor: HarnessDescriptor): VerificationResult;
-export declare function dispatchToHarness(adapter: HarnessAdapter, intent: OpenMeritIntent): Promise<HarnessDispatchReceipt>;
-export declare function startedStage(kind: IntentKind): ImprovementCycleState["stage"];
-export declare function completedStage(kind: IntentKind, succeeded: boolean): ImprovementCycleState["stage"];
-export interface VerificationResult {
-    readonly valid: boolean;
-    readonly errors: readonly string[];
-}
-export interface ResultInterpretation extends VerificationResult {
-    readonly nextStage?: ImprovementCycleState["stage"];
-    readonly config?: OpenMeritProjectConfig | undefined;
-    readonly cyclePatch?: Partial<ImprovementCycleState> | undefined;
-}
-export declare function validateObservabilityCoverage(profile: TaskProfile, coverage: ObservabilityCoverage, requireReady: boolean): readonly string[];
-export declare function interpretIntentResult(intent: OpenMeritIntent, result: AnyIntentResult, cycle: ImprovementCycleState, config: OpenMeritProjectConfig): ResultInterpretation;
-export type OrchestrationDecision = {
-    readonly action: "issue_intent";
-    readonly intentKind: IntentKind;
-    readonly reason: string;
-} | {
-    readonly action: "await_user";
-    readonly reason: string;
-} | {
-    readonly action: "observe";
-    readonly reason: string;
-};
-export declare function nextImprovementAction(state: ImprovementCycleState): OrchestrationDecision;
-export declare function verifyFrontierSnapshot(profile: TaskProfile, assessments: readonly CandidateAssessment[], snapshot: FrontierSnapshot): VerificationResult;
-export interface IssuedIntent {
-    readonly intent: OpenMeritIntent;
-    readonly state: OpenMeritProjectState;
-    readonly receipt: HarnessDispatchReceipt;
-}
-export interface CoordinatorIssueOptions {
-    readonly additionalConstraints?: Readonly<Record<string, JsonValue>> | undefined;
-}
-export interface AcceptedIntentResult {
-    readonly intentKind: IntentKind;
-    readonly state: OpenMeritProjectState;
-    readonly interpretation: ResultInterpretation;
-    readonly automation: {
-        readonly plan: AutomationPlan;
-        readonly receipt?: HarnessDispatchReceipt;
-    };
-}
-export interface ObservationResult {
-    readonly state: OpenMeritProjectState;
-    readonly assessmentDue: boolean;
-}
-export interface CatalogChangeResult {
-    readonly state: OpenMeritProjectState;
-    readonly changed: boolean;
-    readonly reassessmentDue: boolean;
-}
-export interface AutomationSignalResult {
-    readonly state: OpenMeritProjectState;
-    readonly duplicate: boolean;
-    readonly decision: OrchestrationDecision;
-}
-export declare function buildAutomationPlan(state: OpenMeritProjectState, descriptor: HarnessDescriptor): AutomationPlan;
-/** Harness-neutral durable coordinator. Adapters transport jobs; this class owns lifecycle state. */
-export declare class OpenMeritCoordinator {
-    private readonly store;
-    private readonly adapter;
-    constructor(store: OpenMeritStore, adapter: HarnessAdapter);
-    issue(kind: IntentKind, options?: CoordinatorIssueOptions): Promise<IssuedIntent>;
-    reconcileAutomation(now?: string): Promise<{
-        readonly plan: AutomationPlan;
-        readonly receipt?: HarnessDispatchReceipt;
-    }>;
-    acceptResult(result: AnyIntentResult): Promise<AcceptedIntentResult>;
-    recordLifecycle(update: IntentLifecycleUpdate): Promise<void>;
-    recordTaskObservation(details?: Readonly<Record<string, JsonValue>>): Promise<ObservationResult>;
-    assessBaseline(now?: string): Promise<{
-        readonly state: OpenMeritProjectState;
-        readonly errors: readonly string[];
-        readonly decision: OrchestrationDecision;
-    }>;
-    recordAutomationSignal(signal: AutomationSignal): Promise<AutomationSignalResult>;
-    recordModelCatalogFingerprint(fingerprint: string): Promise<CatalogChangeResult>;
-}