openmerit 0.1.12 → 0.2.0

package/CHANGELOG.md

@@ -1,5 +1,13 @@
 # Changelog
 
+## 0.2.0 — 2026-11-04
+
+- Add `openmerit scout`, a conversation with Scout from the terminal: clarifying questions answered with `--brief` or `--skip`, then up to five models per task, cheapest first among models that reach Scout's quality bar. When you ask for the fastest or newest model, the output names that order and shows each model's time per task or release date. It uses this device's Claude Code or Pi key and limits new conversations to the endpoint IDs in `.openmerit/scout.json`.
+- The installed Scout instructions for Claude Code and Pi tell the agent to relay Scout's questions to the user and to read `tasks[].models`. This needs the matching hosted Scout release, whose `scout_models` MCP tool now runs the Scout agent.
+- **Breaking:** remove the `openmerit`, `openmerit/core` and `openmerit/protocol` package exports, along with the evaluation coordinator, harness protocol, Pareto conformance rules and the repository's `npm run demo` sandbox. The package keeps `openmerit/pi` and the `openmerit` command: `openmerit dash`, `openmerit scout`, Scout setup commands and `openmerit eval`.
+- Remove the hosted Inference Terminal sample at `dash.openmerit.ai`, its `/demo` before/after comparison and the opt-in `?map=flow` map experiment. The local terminal, including its fictional sample (`--demo`), is unchanged.
+- Remove the retired demo guides and the guides that documented only the coordinator: architecture, adapter development, Pareto specification, first trial, metrics and evidence, comparisons and swaps, automatic checks, budgets and permissions, and project files and logs.
+
 ## 0.1.12 — 2026-11-03
 
 - Replace the obsolete Pi 0.87 evaluation adapter with native Scout support for Pi 1.5.0. Share browser device approval, private client/scope/project credentials, installer lifecycle and Scout instructions with Claude Code; keep Pi's native MCP, tools, model, permissions and session ownership intact.

package/README.md

@@ -2,7 +2,7 @@
 
 OpenMerit provides a local Inference Terminal for understanding an application's models, services, recorded activity, and compute, plus Scout guidance for application-model choices.
 
-The terminal reads existing evidence; Scout recommends candidates to evaluate. Neither is a request router or proof of application-quality improvements. A separate standalone evaluation CLI and reusable core coordinator support explicit evaluation workflows.
+The terminal reads existing evidence; Scout recommends candidates to evaluate. Neither is a request router or proof of application-quality improvements. A separate standalone evaluation CLI supports explicit evaluation workflows.
 
 ## Open the terminal
 
@@ -16,9 +16,9 @@ openmerit dash
 
 No Pi installation or provider API key is needed. The terminal opens a browser connected to a read-only loopback service. Supported source/configuration declarations establish inventory; existing application logs or exports supply request history. Prompts, responses, and credentials are not retained by terminal collection. Unsupported or missing evidence remains unknown.
 
-The terminal and hosted dashboard follow the device's light/dark preference without a theme control. CLI and terminal product analytics are off unless explicitly enabled; see [the analytics contract](docs/inference-terminal.md#optional-cli-product-analytics).
+The terminal follows the device's light/dark preference without a theme control. CLI and terminal product analytics are off unless explicitly enabled; see [the analytics contract](docs/inference-terminal.md#optional-cli-product-analytics).
 
-Explore the [hosted sample](https://dash.openmerit.ai/) or [before/after dashboard demo](https://dash.openmerit.ai/demo). Both use fictional data and make no inference calls. See [the terminal guide](docs/inference-terminal.md) for configuration, discovery, diagnostics, history limits, and agent access.
+Run `openmerit dash --demo` to explore a fictional sample workspace. See [the terminal guide](docs/inference-terminal.md) for configuration, discovery, diagnostics, history limits, and agent access.
 
 ## Connect Scout to Claude Code
 
@@ -42,17 +42,14 @@ Package publication and website deployment are separate releases. Pi setup requi
 
 The standalone `openmerit eval` CLI is unchanged by the Pi replacement. Evaluate Claude Code, Codex and OpenCode with explicit tasks, model scope, budget and graders. Freeze Scout's shortlist and compare fresh repeated attempts after source changes. Budget and sandbox blocks stay separate from task scores; unknown costs stay unknown. See [agent evaluations](docs/agent-evaluations.md) for setup, graders, budgets and availability.
 
-The core coordinator remains available for custom harnesses: task profiles, controlled experiments, baseline and frontier validation, evidence contracts, budgets, approvals and rollback requests. The harness performs the work and supplies evidence; core validation does not establish that external measurements are truthful. The older Pi lifecycle walkthroughs are retained as historical/core references, not supported commands in the new Scout adapter.
-
 ## Documentation
 
-The [documentation overview](docs/index.md) links current guides and historical references. The website at [openmerit.ai/docs](https://openmerit.ai/docs/) is deployed separately from the package and this checkout.
+The [documentation overview](docs/index.md) links the current guides. The website at [openmerit.ai/docs](https://openmerit.ai/docs/) is deployed separately from the package and this checkout.
 
 - [Getting started](docs/getting-started.md) and [troubleshooting](docs/troubleshooting.md)
 - [Scout](docs/scout.md) and [Pi adapter](docs/pi-extension.md)
 - [Inference Terminal](docs/inference-terminal.md) and [agent evaluations](docs/agent-evaluations.md)
 - [Security and data handling](docs/security.md)
-- [Architecture](docs/architecture.md), [adapter development](docs/adapter-guide.md), and [Pareto specification](docs/pareto-spec.md)
 - [Testing](docs/testing.md) and [current limitations](docs/roadmap.md)
 
 ## Development
@@ -63,6 +60,6 @@ npm run verify
 npm run dash -- /path/to/application
 ```
 
-`packages/terminal` contains the CLI, collectors, hosted sample, and browser interface. `packages/protocol` and `packages/core` provide evaluation contracts and coordination; `packages/pi` supplies only the native Scout adapter. The package exports `openmerit/core`, `openmerit/protocol`, and `openmerit/pi`. See the [Pi package README](packages/pi/README.md) for bounded adapter tests. Provider credentials belong to the harness or its environment and must never be committed.
+`packages/terminal` contains the CLI, collectors and browser interface. `packages/eval` contains the standalone `openmerit eval` runner, and `packages/pi` supplies only the native Scout adapter. The package exports `openmerit/pi` and the `openmerit` command. See the [Pi package README](packages/pi/README.md) for bounded adapter tests. Provider credentials belong to the harness or its environment and must never be committed.
 
 Edit documentation in `docs/`, then run `npm run check:docs`. The website is generated from those Markdown files. See [documentation maintenance](docs/site-documentation.md) and the [production-source reconciliation note](docs/site-domain-migration.md) before deployment; a local build does not publish changes.

package/dist/pi/scout-extension.mjs

@@ -46,6 +46,8 @@ count as model choices, not implementation details. Identify this decision befor
 writing model-specific code, installing a model package or downloading weights.
 
 Follow the skill's project access policy. If it is missing, ask and save it first.
+Scout may answer with clarifying questions: relay them to the user and continue
+the same Scout conversation with their answers before choosing.
 If Scout is unavailable, fails or has no suitable evidence/candidate, disclose the
 gap and pause the model decision; do not fall back to a remembered or SDK-default
 model. You may continue work that does not commit to a model.
@@ -92,17 +94,28 @@ is not permission to search all models.
 
 ## Searching
 
-Call \`scout_models\` with a non-confidential task description and
-\`endpointIds\` set to the saved inventory, including \`[]\` when empty.
-Existing-only never broadens. For existing-first, if no existing candidate fits,
-explain the gap and ask before a separate search without \`endpointIds\`. Send
+Call \`scout_models\` with a non-confidential task description as \`prompt\` and
+\`endpointIds\` set to the saved inventory, including \`[]\` when empty. Send
 only task requirements, never source files, secrets or real customer records.
-
-Compare model AND endpoint, evidence, reference cost/time, unknowns and
-warnings. For multiple tasks read \`tasks[].slots[0].recommendations\`; the
-top-level list is empty. Prefer the cheapest usable option the quality evidence
-supports, without claiming benchmarks prove application accuracy. Use the
-returned provider model ID and the project's actual SDK and protocol.
+If the MCP tool is unavailable, run
+\`npx -y openmerit@latest scout "<task>" --json\`; it applies the saved inventory.
+
+Scout is a conversation with the agent behind openmerit.ai/scout. When
+\`status\` is \`needs_answers\`, fill in what the user or project already states,
+show the user Scout's brief and remaining questions, and wait for their answers.
+Then call again with the returned \`conversationId\` and \`brief\` set to the
+rewritten components, or \`skip: true\` if the user wants Scout to assume. Never
+answer Scout's questions with guesses. Send later refinements to the same
+\`conversationId\`. A call with only a \`conversationId\` reads an interrupted turn.
+
+When \`status\` is \`recommended\`, Scout has split the work into \`tasks\`, one
+per model, each with up to five ranked \`models\`; cover every task. Each
+model's \`cost\` names the \`endpointId\` and \`providerModelId\` to call.
+Existing-only never broadens. For existing-first, if no existing candidate fits a
+task, explain the gap and ask before a new conversation without \`endpointIds\`.
+Compare quality evidence, reference cost/time and watch-outs. Prefer the cheapest
+usable option the evidence supports, without claiming benchmarks prove
+application accuracy. Use the project's actual SDK and protocol.
 
 ## Boundaries