openmerit 0.1.12 → 0.3.0

package/docs/security.md

@@ -1,54 +1,29 @@
 # Security
 
-**Pi replacement — unreleased, unpublished source:** 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 and core coordinator remain separate.
+**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.
+**Retirement:** npm 0.3.0 removes the standalone [agent-evaluation runner](agent-evaluations.md), including planning; unreleased Scout source removes `/scout/api/recommend`. Existing local reports, budgets, configuration and host-agent instructions are not deleted; review them separately. No provider billing control or remote data deletion is implied.
 
-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.
+The Scout agent, MCP, publisher and account analytics/deletion capabilities remain. Historical analytics and stored catalogue/research data are not erased by endpoint retirement. Necessary provider processing for the agent and publisher continues under the [Scout data policy](scout-data-policy.md).
 
 ## Credential ownership
 
 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
-
-This section describes core/custom evaluation harness policy. Pi-specific lifecycle and background-runner behavior below is **historical Pi 0.87 functionality**, removed from the new Scout adapter. Installing the replacement does not establish that an old background job was removed; manage that job separately.
-
-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, 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, and Scout project policy, plus files left by the retired Inference Terminal (`terminal.json`, `inference.jsonl`), which upgrades do not delete. It may reveal task names, model choices, budgets or endpoint identifiers. Treat it as sensitive project metadata even though it must not contain credentials.
 
-The historical evaluation adapter also recorded OpenMerit requests and results in Pi history. 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.
+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.
 
-## Inference Terminal
-
-The terminal reads supported project metadata, request logs, explicit exports, and authorized loopback runtime inventory/metrics endpoints. It calls no inference endpoint and exposes no mutation API. A local syntax index reads supported Python, JavaScript/TypeScript, JSON, YAML, TOML, and project-local dotenv declarations. It does not execute or import project code, source shell files, or resolve arbitrary expressions. Known credential-variable presence can identify configuration; credential values are discarded and never used for provider calls. Endpoint addresses are sanitized before retention. Static URLs found by the syntax index never authorize network probes.
-
-Loopback runtime probes require supported project endpoint declarations or explicit terminal configuration. No standard ports, remote provider accounts, credential stores, running processes, or general home directories are scanned. Whole-machine readings are context, not per-request measurements; the compute view requires explicit links or supplied host evidence.
-
-Coding-harness histories are outside the terminal's application scope and are not scanned or imported. Application request logs and explicit exports retain only allowlisted metadata, without prompts or responses. Sources must belong to the selected application; the terminal cannot infer the purpose of an unlabeled API response. Records explicitly marked `scope: "development"` are rejected.
-
-The local web service binds to `127.0.0.1` and rejects unexpected Host, Origin, and cross-site browser requests. It only serves bundled assets and specific read-only JSON routes. It is not authenticated against other local processes or machine users. Model names, endpoint identifiers, and relative source paths can still be sensitive. Names and identifiers in imported metadata must be kept free of secrets.
-
-Repository metadata and usage caches live in process memory and disappear when the terminal exits. The terminal creates no persistent index or files in the application. Per-file/parser protections, request-log read limits, runtime inventory limits, and explicit coverage gaps still apply. See [terminal data handling and limits](inference-terminal.md) for supported sources, precedence, retention bounds, diagnostics, and sample-data separation.
-
-
 ## Hosted Scout authentication
 
 Hosted Scout uses Clerk Google/GitHub sign-in. The page and status are public; JSON recommendations require a valid Clerk session bearer token, not just a cookie. MCP methods require a device key from the setup below. Missing/invalid credentials return HTTP 401, and missing authentication configuration fails closed with HTTP 503. Clerk remains the identity system; the analytics integration below can synchronize selected profile fields to PostHog. Raw account IDs are used transiently for the per-user edge limiter and are not joined to historical Cloudflare prompt records. A prompt draft is temporarily stored in the current browser tab during sign-in. No Clerk Billing or automatic agent OAuth is included. See [Scout account sign-in](scout.md#account-sign-in-published-21-october-2026) for token lifetime, rate limits, data handling and the remaining real-login validation limits.
@@ -91,7 +66,7 @@ Historical records are accessible only through authenticated Cloudflare account
 
 ### Optional product analytics
 
-Scout has a visible privacy disclosure and controls. Public homepage/docs navigation events remain source-only; npm 0.1.7 includes opt-in local terminal/map events and aggregate counts. The terminal relay cannot mutate project or inference state, retains loopback Host/Origin guards, and forwards only bounded allowlisted telemetry. Terminal and CLI use a process-only random ID; website events use a separate tab ID. Neither is implicitly linked to Clerk. Application names, raw inputs/outputs, local identifiers and source files remain local. Sanitized error classes/categories (and Scout application file/line frames) exclude raw messages, credentials, source context, arbitrary URLs and filesystem paths. No replay is enabled. All expanded account-linked events pass the same preference/deletion gate as profile synchronization; ordinary event delivery remains best effort. New search details link to identified accounts when profile sync is active, unlike the legacy Cloudflare archive. No external retention setting is changed.
+Scout has a visible privacy disclosure and controls. Public homepage/docs navigation events remain source-only; npm 0.1.7 includes opt-in local terminal/map events and aggregate counts, which npm 0.3.0 removes with the [Inference Terminal](inference-terminal.md). The terminal relay cannot mutate project or inference state, retains loopback Host/Origin guards, and forwards only bounded allowlisted telemetry. Terminal and CLI use a process-only random ID; website events use a separate tab ID. Neither is implicitly linked to Clerk. Application names, raw inputs/outputs, local identifiers and source files remain local. Sanitized error classes/categories (and Scout application file/line frames) exclude raw messages, credentials, source context, arbitrary URLs and filesystem paths. No replay is enabled. All expanded account-linked events pass the same preference/deletion gate as profile synchronization; ordinary event delivery remains best effort. New search details link to identified accounts when profile sync is active, unlike the legacy Cloudflare archive. No external retention setting is changed.
 
 The [PostHog integration](scout.md#product-analytics) uses the EU ingestion endpoint; unconfigured deployments remain off. Verified Clerk user IDs become namespaced SHA-256 pseudonyms for cross-client account retention. Profile sync can associate those identities with names and verified email addresses, so they are identifiable personal data. No identity is added to the historical Cloudflare prompt archive. The browser retains an anonymous ID and hashed account/session transition markers in tab storage, rotating the anonymous ID on account changes. There is no autocapture, replay or visitor-IP forwarding. PostHog has its own retention/access policies, not Cloudflare's three-month policy.
 

package/docs/testing.md

@@ -1,6 +1,8 @@
 # Testing and validation
 
-**Pi source replacement — unreleased and unpublished:** the new Pi 1.5.0 adapter uses native Scout MCP and shared guidance only. The dated Pi 0.87 lifecycle/scheduler results below remain historical receipts, not proof of the replacement or supported current commands. Package, browser-approval, native Pi and SDK acceptance must be reported for the new build separately; a successful documentation build alone establishes none of them. Core coordinator and standalone evaluation tests remain separate.
+**Cleanup:** npm 0.3.0 retires the standalone evaluation CLI and the Inference Terminal; unreleased source also retires the legacy JSON recommendation pipeline and unpublished docs website shell. Dated evaluation/API acceptance records below describe historical releases, not current supported commands. Current verification retains agent, MCP, publisher, status, policy and protected-memo coverage; it does not publish or deploy anything.
+
+**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
 
@@ -34,7 +36,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,53 +60,11 @@ npm run verify
 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
-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 |
-
-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.
-
-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.
+`verify` runs workspace tests, syntax checks, strict TypeScript checks and the TypeScript migration ratchet, the package build, memo tests, policy/memo build and Markdown-guide checks, Scout tests/build, and whitespace validation. It does not publish a package or deploy the website. `npm run check:worker-types` separately checks generated Worker types; CI also performs packed-install, CLI help and Pi load smoke checks.
 
 ## 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`, checks the installed `openmerit --help`, 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
 
@@ -113,7 +73,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

@@ -33,15 +33,15 @@ That is expected. Pi has no OpenMerit auto-update hooks. Explicitly rerun `insta
 
 ## `/openmerit` or evaluation tools are missing
 
-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); custom harnesses may still use [the core coordinator](adapter-guide.md).
+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).
 
 ## Scout was not consulted or its evidence is insufficient
 
 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.
 
-## Evaluation or terminal problems
+## `openmerit dash` or `openmerit eval` is an unknown command
 
-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.
+Both are retired in npm 0.3.0; see the [Inference Terminal](inference-terminal.md) and [evaluation CLI](agent-evaluations.md) retirement notes. Existing local files are not deleted. Never mark missing or rejected evidence successful merely to advance a workflow.
 
 ## Report a reproducible problem
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "openmerit",
-  "version": "0.1.12",
+  "version": "0.3.0",
   "description": "Evidence-driven model decisions for coding harnesses.",
   "type": "module",
   "bin": {
@@ -11,33 +11,18 @@
     "pi-package",
     "pi-extension",
     "model-routing",
-    "evaluation",
-    "pareto-frontier"
+    "evaluation"
   ],
   "files": [
-    "dist/core/",
-    "dist/protocol/",
     "dist/pi/",
     "dist/terminal/",
-    "dist/eval/",
+    "!dist/terminal/src/*.ts",
     "docs/",
     "CHANGELOG.md",
     "LICENSE",
     "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"
@@ -70,6 +55,7 @@
   "scripts": {
     "check": "npm run check --workspaces --if-present",
     "test": "npm run test --workspaces --if-present",
+    "pretypecheck": "npm run build:site",
     "typecheck": "tsc -p tsconfig.json && tsc -p tsconfig.scout.json && tsc -p scout/agent/tsconfig.json",
     "check:typescript": "node scripts/check-typescript.ts",
     "types:workers": "node scripts/worker-types.ts",
@@ -77,31 +63,17 @@
     "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",
-    "check:docs": "npm run build:docs && node --test scripts/docs.test.mjs",
+    "build:site": "node scripts/build-site.ts",
+    "check:docs": "npm run build:site && node --test scripts/docs.test.ts",
     "memo": "node demo/memo/preview.ts",
-    "check:demo": "npm ci --ignore-scripts --prefix demo && npm run build:docs && tsc -p tsconfig.memo.json && node --test demo/test/*.test.mjs demo/test/*.test.ts",
+    "check:demo": "npm ci --ignore-scripts --prefix demo && npm run build:site && tsc -p tsconfig.memo.json && node --test demo/test/*.test.mjs demo/test/*.test.ts",
     "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": {
-    "@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": "1.5.0"
   },
@@ -111,26 +83,21 @@
     }
   },
   "devDependencies": {
-    "@earendil-works/pi-coding-agent": "1.5.0",
     "@clerk/backend": "3.26.1",
     "@clerk/shared": "4.41.0",
+    "@earendil-works/pi-coding-agent": "1.5.0",
+    "@lezer/javascript": "1.5.6",
     "@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",
-    "liveline": "0.0.7",
+    "hyparquet": "1.31.5",
     "markdown-it": "15.0.2",
     "miniflare": "5.20260921.0-alpha",
-    "minisearch": "7.2.0",
-    "morphdom": "2.7.8",
-    "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"
+    "wrangler": "4.136.3",
+    "yaml": "2.9.1"
   }
 }

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>;
-}