@bjoernrochel/sevro 0.1.0-rc.12 → 0.1.0-rc.13

package/CONTRIBUTING.md

@@ -38,6 +38,13 @@ bun run test:docs-examples
 ```
 
 The second command checks the tutorial in fresh consumer/contributor directories.
+Its complete recipe checks also require UV, Python 3, mise, and an existing
+`mise install node@24.13.0` installation; see [recipe prerequisites](docs/recipes.md).
+CI explicitly provisions these tools. Missing prerequisites fail with a named
+setup instruction rather than skipping a recipe.
+To run recipe commands from this source checkout, set
+`export SEVRO_RECIPES="$PWD/examples/recipes"` from the repository root, then
+follow the [recipe commands](docs/recipes.md#prepare-a-recipe-project).
 Native model trials need their own [credentials and prerequisites](docs/native-hosts.md).
 
 ## Quality contract and checks
@@ -68,6 +75,10 @@ Before committing, use `bun run check:typescript --fast` after installing the
 locked dependencies. This runs inventory, schema, formatting, lint, typing and
 documentation checks; it does not replace full acceptance. CI retains machine-readable coverage
 reports under `.quality/` and exposes the stable `TypeScript quality` status.
+The complete command's `static`, `docs`, `tests` and `package` phases run as
+concurrent CI jobs. After frozen installation, use
+`bun run check:typescript --phase <name>` to run one phase locally; it does not
+replace acceptance across all four. See the [phase inventory](docs/typescript-quality.md).
 
 Run `bun run check:docs:external` separately and [triage network failures](docs/documentation-quality.md#external-links).
 Guide changes also need [native evals](docs/guide-evaluation.md).
@@ -84,8 +95,8 @@ repairing in-scope failures; it does not authorize merging or unrelated changes.
   non-root user, and isolation prerequisites. Reproducing that environment locally
   with Docker is optional for diagnosis and is not a publication prerequisite.
 - After the local pre-commit checks, publish the authorized candidate to its PR
-  and require `bun run check:typescript` to succeed in GitHub CI before reporting
-  delivery as complete. A local run, fast check, targeted suite, or historical
+  and require all four canonical `check:typescript` phases to succeed in GitHub CI
+  before reporting delivery as complete. A local run, fast check, targeted suite, or historical
   result does not establish that the current Ubuntu gate passes.
 - Keep the quality bar intact. Repair behavior or add meaningful coverage for
   accepted behavior; do not lower thresholds, exempt authored sources, skip tests,

package/README.md

@@ -40,6 +40,11 @@ Continue with [your first evaluation](docs/getting-started.md): the exact comman
 expected `passed` result, and retained evidence. Read [installation](docs/installing.md)
 for updates, removal, and source checkouts.
 
+The development checkout and freshly built packages provide a
+[demo-to-iteration workflow](docs/evaluation-workflow.md): initialize real
+assertions, prepare, execute, read progress and inspect the latest result.
+The published `rc.11` package uses the installed tutorial above.
+
 ## Find your next task
 
 The [documentation hub](docs/README.md) routes to running evaluations, authoring

package/docs/README.md

@@ -7,12 +7,15 @@ Start with the task you want to complete. These pages work without an agent.
 | I want to…                                     | Read                                                     |
 | ---------------------------------------------- | -------------------------------------------------------- |
 | Get a result without a model account           | [Your first evaluation](getting-started.md)              |
+| Initialize, prepare, run and iterate           | [Evaluation workflow](evaluation-workflow.md)            |
 | Install, update, remove, or use a checkout     | [Installation](installing.md)                            |
 | Run evaluations and select a host              | [Running evaluations](running-evaluations.md)            |
 | Create cases and reusable policy               | [Cases and extensions](creating-cases.md)                |
+| Copy a complete coding, skill or runtime setup | [Runnable recipes](recipes.md)                           |
 | Interpret verdicts, evidence, and comparisons  | [Reading results](reading-results.md)                    |
 | Run Codex or Claude with isolation             | [Native hosts](native-hosts.md)                          |
 | Reuse host tools or enable goals and hooks     | [Runtime configuration](runtime-v1.md)                   |
+| Save recurring evaluation selections           | [Run settings](run-settings-v1.md)                       |
 | Resolve a symptom                              | [Troubleshooting](troubleshooting.md)                    |
 | Trace runner lifecycle, ownership, and changes | [Architecture](architecture.md)                          |
 | Change Sevro or its documentation              | [Contributing](../CONTRIBUTING.md)                       |
@@ -35,6 +38,7 @@ There is no accepted Rust migration decision here;
 [issue #2](https://github.com/BjRo/sevro/issues/2) tracks research.
 
 Read [documentation quality](documentation-quality.md),
+[the usability study protocol](usability-study.md),
 [guide evaluation](guide-evaluation.md), [releases](releases.md), and
 [acknowledgements](acknowledgements.md) for maintenance.
 Return to the [Sevro introduction](../README.md).

package/docs/contracts.md

@@ -7,6 +7,7 @@ Read these human contracts and their schemas together:
 - [Report v1](report-v1.md): summaries and comparison limitations.
 - [Identity v1](identity-v1.md): versioned comparison dimensions and hashing.
 - [Runtime configuration v1](runtime-v1.md): environment, tools, private state, goals, and hooks.
+- [Run settings v1](run-settings-v1.md): recurring evaluation selections and CLI overrides.
 - [Built-in graders v1](builtin-graders-v1.md): output, shell, Git HEAD, and semantic checks.
 - [Schemas](../schemas/): machine-readable public forms.
 

package/docs/creating-cases.md

@@ -4,18 +4,25 @@ Start with a direct case for a prompt, fixture, and built-in success criteria.
 Copy [the basic graded case](../examples/basic/graded.json), give it a stable
 ID, and replace the prompt/check. Read [built-in graders](builtin-graders-v1.md)
 for regex, JSON, and bounded schema assertions. No criteria means `not_assessed`.
+For complete coding, repository-skill, runtime, semantic and extension projects,
+follow the [runnable recipes](recipes.md), including their deliberate failures.
 
 Run it with the [CLI](running-evaluations.md). Direct cases follow `ResolvedCase`
 in [the engine](../src/engine.ts). Fixtures can provide inline files, generated
 Git history, or a declared clean repository. The [CLI reference](development-cli.md)
 owns required source roots/maps; an arbitrary returned path does not grant access.
 
+Selecting `--project-root` identifies the project; it does not copy its contents
+into a participant fixture. Declare the files or repository source the participant
+should receive. The [run defaults reference](development-cli.md#run-defaults)
+explains how project identity, fixtures and CLI path resolution interact.
+
 ## Evaluate your repository skills
 
 Start with one representative task, your actual skill, and observable success
 criteria. This example evaluates a documentation guide's answer with Codex.
 Use [Sevro from `PATH`](installing.md#make-the-command-available).
-Live runs require the [native host prerequisites](native-hosts.md), macOS
+Live runs require the [native host prerequisites](native-hosts.md), supported
 isolation, an authenticated Codex installation, and your chosen model.
 They consume that account's model quota.
 
@@ -109,7 +116,7 @@ prepares skill mounts and interprets complete native host evidence. The
 [extension protocol](extension-protocol-v1.md) defines repository and plugin
 invocations; the checkout's [guide evals](guide-evaluation.md) demonstrate the
 approach. Check those capabilities against your exact installed release:
-this checkout contains [changes beyond published `rc.2`](installing.md#published-package-and-checkout).
+this checkout can contain [changes beyond its published version](installing.md#published-package-and-checkout).
 
 ## Reusable project policy
 

package/docs/development-cli.md

@@ -11,11 +11,99 @@ grading, evidence, and extension lifecycle.
 Examples assume [Sevro and Bun are on `PATH`](installing.md#make-the-command-available).
 For a contributor checkout, use `bun src/cli.ts` in place of `sevro`.
 
+Use `sevro --help`, `sevro run --help`, or `sevro report --help` for examples,
+required options, and defaults without preparing a run. `sevro --version` prints
+the installed package version. Invocation and configuration diagnostics go to
+stderr in both output modes; `--json` keeps one `sevro.cli-result.v1` document
+on stdout. Invalid case diagnostics name the input file and offending field.
+
+<a id="run-defaults-in-this-checkout"></a>
+
+## Run defaults
+
+`sevro demo` owns a deterministic case, fixture and adapter. It needs no model
+credentials and immediately prints an assessed verdict plus an evidence path in
+`.sevro/results` beneath the invoking directory. Its temporary project and
+configuration are independent of the caller's files and runtime policy.
+
+An ordinary run needs a case source and candidate route. For example:
+
+```sh
+sevro run --case-file ./case.json --adapter-module ./host-adapter.ts
+```
+
+| Setting                                                     | Default                                                                                                                 |
+| ----------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------- |
+| Condition                                                   | `passive`                                                                                                               |
+| Trial count                                                 | `1`                                                                                                                     |
+| Pass threshold                                              | `1`: all assessed trials must pass; any unassessed trial prevents a pass                                                |
+| Parallel trial limit (`--jobs`)                             | `3`                                                                                                                     |
+| Project root                                                | Invoking current directory                                                                                              |
+| Results root                                                | `<project-root>/.sevro/results`                                                                                         |
+| Configuration root                                          | Project root                                                                                                            |
+| Run-state root                                              | Results root                                                                                                            |
+| Runtime policy                                              | Discover `sevro.json` at project root; none when absent                                                                 |
+| Native binary                                               | Resolve only the explicitly selected `codex` or `claude` from `PATH`; `--codex-bin` / `--claude-bin` override it        |
+| Native execution timeout                                    | `600000` ms (10 minutes); Codex accepts `--codex-timeout-ms`                                                            |
+| Codex entrypoint                                            | `exec`; a native-goal runtime policy selects `app-server`                                                               |
+| Codex agent concurrency                                     | `agents.max_concurrent_threads_per_session` from `.codex/config.toml` at configuration root, otherwise the host default |
+| Shell-check expected exit                                   | `0` unless the check declares `expectedExitCode`                                                                        |
+| Shell-check timeout                                         | `30000` ms unless the check declares `timeoutMs` (maximum `120000`)                                                     |
+| Shell isolation, dry preparation, host diagnostic retention | Off                                                                                                                     |
+
+Every run file/directory option accepts a relative path based on the invoking
+current directory, including adapter modules, extension source files, native
+binary overrides and protected roots. Sevro resolves them to canonical absolute
+paths before constructing protection lists; missing output-directory suffixes
+resolve through their nearest existing parent. A different `--project-root`
+does not change that base. The default results directory is relative to the
+selected project root. Paths inside runtime policy files retain their
+[runtime-specific resolution rules](runtime-v1.md).
+Extension command JSON still requires an absolute executable argv; arbitrary
+argv entries are not treated as CLI path options.
+
+Sevro prints a whitelist of effective run settings and routes on stderr before
+candidate execution, including resolved storage paths, native executables,
+timeouts and concurrency. JSON stdout remains one result document. The preview
+does not print credential bytes, runtime environment values or native diagnostics.
+The resolved executable is retained as `sevro.host.executable` in each used native
+role's redacted host configuration; selecting a different path changes that
+configuration's identity.
+
+Use `sevro init` with `--template response`, `coding` or
+`repository-skill` and `--directory <new-path>`. It refuses existing destinations
+and writes runnable assertions, a manifest and template instructions. Follow the
+[demo-to-iteration workflow](evaluation-workflow.md) for preparation, execution
+and negative controls. Repository-skill requires explicit native model, effort
+and authentication; dry preparation does not establish dispatch.
+
+Actual preparation, candidate, grading and evidence-retention stage events use
+stderr. Human completion includes each trial's separate states, failed-check
+reasons, measured candidate time, known/unknown usage and retained paths. JSON
+stdout remains one result. Each retained CLI run writes `result.json` beside run
+evidence and `<results-root>/latest.json`. `sevro report --latest` reads the current
+directory's default results root; add `--results-root <path>` for another root.
+Dry and failed runs can be latest.
+
+Project root identifies the evaluated project and extension discovery. It does
+not populate the participant workspace: declare inline files, generated history
+or a repository source in the case's fixture. See [case authoring](creating-cases.md).
+Keep `.sevro/` out of Git. Results and run-state paths are excluded from project
+snapshots and untracked Git identity; tracked source changes still count.
+
+## Explicit run settings
+
+To repeat these selections, use the versioned [saved run settings](run-settings-v1.md)
+with `--run-manifest-file ./evaluation.json`. Built-in defaults are replaced by
+saved settings, then by explicit CLI options. `sevro.json` keeps its separate
+runtime scope. Saved file paths use the manifest's directory; explicit CLI
+paths use the invoking directory.
+
 An installed package records its name, version, and a digest of its packaged
 runtime and public contract files without reading runner Git metadata. The CLI
 derives the project digest from its revision and dirty patch, or from a bounded
 content snapshot when the project has no Git revision. Result and run-state
-directories are excluded from that snapshot. When running this source checkout
+directories are excluded from that snapshot and untracked Git identity. When running this source checkout
 for coordinated development, pass `--runner-checkout-root` with the absolute
 path to this checkout. Sevro verifies that it is the code actually running and
 records its revision and dirty-patch digest instead of package provenance.
@@ -67,8 +155,7 @@ Add `--retain-host-diagnostics` to a failing invocation to retain private
 diagnostics from bundled Codex and Claude hosts. The switch defaults to off,
 applies to every selected native role, and is independent of runtime
 `nativeTranscripts`. It does not enable transcript access or change the
-candidate's permissions. This switch is available in the development checkout;
-the published `0.1.0-rc.8` does not accept it.
+candidate's permissions.
 
 For example, add the switch to the Codex command above:
 
@@ -239,7 +326,8 @@ For cases with `sevro.semantic` checks, also pass
 explicit second `HostAdapter` for grading. Alternatively, select the bundled
 Codex route with `--semantic-host codex --semantic-model <model>
 --semantic-effort <effort>`. That route also requires `--codex-bin` and
-`--codex-auth-file`, shared with a Codex candidate route when present. The two
+`--codex-auth-file`, shared with a Codex candidate route when present. The binary
+defaults to the explicitly selected `codex` on `PATH`. The two
 semantic route options are exclusive. The candidate and semantic routes are
 recorded separately in evidence and evaluation identity. The semantic adapter
 runs after a complete candidate response in its own empty workspace; missing
@@ -293,7 +381,7 @@ verdict and rejects unsolicited recommendations.
 
 If the extension needs configuration, supply both
 `--extension-configuration-file` and
-`--extension-redacted-configuration-file` as absolute paths to JSON objects.
+`--extension-redacted-configuration-file` as paths to JSON objects.
 The latter replaces secret values for the retained configuration digest. Keep
 secrets out of the command argv and the redacted file.
 
@@ -421,6 +509,3 @@ Claude also advertises `sevro.host.native-goal`. Its observer binds one persiste
 transcript to the original successful native session and retains goal status
 and objective length. Missing, ambiguous, malformed or oversized evidence is
 unavailable; an unavailable observation cannot prove goal absence.
-
-These additions require the `0.1.0-rc.2` candidate. The published `rc.1` lacks
-the app-server selector and native goal observations.

package/docs/documentation-quality.md

@@ -14,6 +14,12 @@ Local checks need no network. Run `bun run test:docs-examples` for the exact
 marked tutorial commands in fresh consumer/contributor directories, including
 expected verdicts and saved evidence. Candidate and released-package runs are
 reported separately. These commands create and clean temporary directories.
+The [recipe verifier](../scripts/documentation-recipes.ts) runs the new packaged
+projects separately from the current published version. It executes actual
+isolated tool/check positive and negative controls and both native hosts' dry
+preparation; authenticated model, plugin-hook and goal behavior remain
+unexecuted by that check. Its [prerequisites](recipes.md#prepare-a-recipe-project)
+are mandatory, including UV and mise's declared Node installation.
 
 `package.json.version` is the authoritative current version. `bun run docs:sync`
 updates only the marked [Current release](installing.md#current-release) section
@@ -25,6 +31,10 @@ stale output. Run synchronization after a version bump and include the resulting
 documentation change. Link installation and update instructions to this section.
 Keep historical versions, licensing transitions, and minimum supported versions
 fixed and explain their purpose beside each reference.
+Link to the current-release section instead of repeating the current Sevro
+version elsewhere. Describe features for the latest version, using the installed
+`sevro` command in user workflows. Keep source-checkout instructions in contributor
+guidance and omit notes about feature unavailability in older releases.
 
 ## External links
 
@@ -38,8 +48,8 @@ make a network job green. External success does not establish a claim's truth.
 
 - Can a new user reach installation, first success, results, troubleshooting,
   architecture, and contributing without the guide?
-- Are supported environments, credentials, side effects, and current versus
-  released behavior explicit beside the relevant commands?
+- Are supported environments, credentials, side effects, and prerequisites
+  explicit beside the relevant commands?
 - Do descriptive links, meaningful headings, source order, readable tables,
   image alternatives, and words rather than color support accessibility?
 - Are current contracts, accepted choices, research, and past evidence distinct?

package/docs/evaluation-workflow.md

@@ -0,0 +1,107 @@
+# From a demo to your next evaluation
+
+Create an evaluation, prepare it, run its assertions, and inspect the latest
+result with the installed `sevro` command.
+
+## Try the demo and create a project
+
+You need Bun 1.3.13. [Install Sevro](installing.md) and
+[make its command available on `PATH`](installing.md#make-the-command-available),
+then run:
+
+```sh
+sevro demo
+sevro init --template response --directory ./response-evaluation
+cd response-evaluation
+```
+
+The demo returns an assessed `passed` task and evidence under `.sevro/results`,
+using its own temporary project without credentials. The initializer refuses
+existing destinations, including directories and symbolic links. It writes
+real assertions, a deterministic adapter, `run.json` and template instructions.
+[Saved settings](run-settings-v1.md) use their manifest's directory for paths;
+`sevro.json` retains its separate runtime scope. Keep private `.sevro/` out of Git.
+
+## Prepare before execution
+
+```sh
+sevro run --run-manifest-file run.json --dry
+```
+
+Stderr shows the whitelisted resolved settings before candidate execution:
+case/source selection, routes/model/effort, trials, threshold, concurrency,
+runtime selection and canonical storage paths. Invalid input names its option,
+file or field; missing executables name installation or explicit override paths.
+Correct the named prerequisite and repeat preparation.
+
+Dry preparation follows normal fixture, extension and check preparation without
+calling the candidate or graders. Expect
+`execution=not_run grading=not_requested task=not_assessed`. It does not establish
+authentication, provider model availability, native skill dispatch or model success.
+See [native prerequisites](native-hosts.md) and [troubleshooting](troubleshooting.md).
+
+## Run, read and change one thing
+
+```sh
+sevro run --run-manifest-file run.json
+sevro report --latest
+SEVRO_TEMPLATE_FAIL=1 sevro run --run-manifest-file run.json
+sevro report --latest
+```
+
+The first run's adapter returns exactly `ready`; its regex assertion must pass.
+The negative control returns `wrong`: expect exit `1`, completed execution and
+grading, task `failed`, and the named `ready` check's reason. Then edit `case.json`
+and `adapter.ts`, prepare again and rerun. Explicit flags override saved settings;
+`--trials 3` repeats the task without rewriting `run.json`.
+
+Progress uses stderr at actual preparation, candidate, grading and evidence
+retention boundaries. Trial numbers distinguish concurrent work, which may
+interleave. Stage `completed` means the attempt finished; the result states whether
+execution/grading succeeded. Dry runs explicitly skip candidate and grading;
+failed candidates skip grading. Failed preparation never prints candidate start.
+Evidence completion follows persistence. Optional synchronous engine observers
+cannot change the result through a thrown exception.
+
+Human completion shows per-trial states, failed/unavailable check reasons,
+measured candidate time, known/unknown usage/cost and `result=`/`evidence=` paths.
+Candidate time measures the host call, not total setup time. Absent metrics remain
+`unknown`; dry duration is unknown. Prompt-only completion stays `not_assessed`.
+Add `--json` to emit one `sevro.cli-result.v1` stdout document; progress remains on
+stderr. See [reading results](reading-results.md).
+
+Each retained CLI evaluation saves `result.json` beside its run evidence and
+atomically publishes `<results-root>/latest.json`. Latest is the last retained CLI
+result, including dry runs and failed assessments. Pre-run failures do not replace
+it. Concurrent runs publish in completion order. Output files stay under excluded
+results storage, preserving project identity. A latest-write failure cannot turn
+an earlier failed assessment into success.
+
+`report --latest` reads `<cwd>/.sevro/results/latest.json`. Use
+`report --latest --results-root ./other-results` for another output root or working
+directory. `--result-file ./path/to/result.json` selects older runs and accepts
+relative paths. Reports validate referenced evidence; missing/moved evidence
+produces a diagnostic. [Report v1](report-v1.md) defines fields and limits.
+
+## Choose another starter
+
+| Template           | Real assertions                                                                                                    | Prerequisites and interpretation                                                                           |
+| ------------------ | ------------------------------------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------- |
+| `response`         | Exact `ready` response; negative control returns `wrong`                                                           | Bun; no model credentials                                                                                  |
+| `coding`           | Edit `add.sh`; isolated checks test positive, negative and zero addition                                           | Bun plus `sandbox-exec` on macOS or `bubblewrap`/`socat` on Linux; negative control leaves subtraction bug |
+| `repository-skill` | Actual `.agents/skills/startup-guide/SKILL.md` mount; explicit invocation evidence; correct start command and port | Bun, Git, Codex, native isolation, explicit model/effort and readable auth file; dry is unassessed         |
+
+From a new parent directory, use `sevro init --template coding --directory ./coding-eval`
+or `sevro init --template repository-skill --directory ./skill-eval`. Read its generated
+README for controls and dry/live commands. Repository-skill `command.json` records
+absolute Bun/extension argv; regenerate it after moving the project.
+
+For model evaluations, replace a saved adapter route with explicit `--host`,
+`--model`, `--effort` and host authentication options. Candidate, semantic and
+advisory model choices remain independent. Deterministic adapters measure wiring;
+they do not measure model ability. Native runs may incur provider charges.
+Automated package checks run response/coding pass/fail and native skill preparation;
+authenticated native behavior and human usability remain unmeasured. The
+[study protocol](usability-study.md) records deferred human measurements.
+[Runnable recipes](recipes.md) cover Claude, plugins/hooks, goals, semantic grading
+and host tools.

package/docs/evidence/code-mode-programs-85.md

@@ -0,0 +1,64 @@
+# Template and batch inspection for issue 85
+
+On 2026-10-15, the implementation for [issue #85](https://github.com/BjRo/sevro/issues/85)
+replayed the two original Codex native transcript bundles through the changed
+Sevro observers and Darrow's checkpoint `67f4fcdb` extension. Bundle and decoded
+source SHA-256 values matched the issue before replay. Raw bundles and output
+remain private and outside Git.
+
+| Original case                     | Exec submissions | Complete receipts after replay | Regraded no-agent assertion |
+| --------------------------------- | ---------------- | ------------------------------ | --------------------------- |
+| goal-placement-direct-same-route  | 11               | 11                             | passed                      |
+| goal-placement-coupled-sequential | 10               | 10                             | passed                      |
+
+The five exact [retained program fixtures](../../tests/fixtures/code-mode-85/README.md)
+now preserve these native ordinals and ordered submission-local labels:
+
+- Direct 45: three `exec_command` calls.
+- Direct 69 and 77: `apply_patch`, then `exec_command`.
+- Coupled 30: three `exec_command` calls.
+- Coupled 68: two `exec_command` calls.
+
+Regrading replaced only the native-call and portable native-control observations
+with newly inspected observations and invoked the original case's extension
+checks. Both `darrow.evals.transcript.1` results changed from unavailable to
+passed. These are artifact rechecks, not new candidate runs or rewritten
+historical task verdicts. Deterministic consumer coverage separately confirms
+that a submitted `spawn_agent` fails the no-agent assertion even when the
+accepted-agent count is zero, and partial receipts remain unavailable.
+
+## Observed test-first slices
+
+1. Red — `bun test tests/codex-native-calls.test.ts -t 'retained direct ordinal 45'`: the template-command receipt was partial.
+   Green — `bun test tests/codex-native-calls.test.ts -t 'retained direct ordinal 45'`: 1 passed, with three bound call labels.
+2. Red — `bun test tests/codex-native-calls.test.ts -t 'retained coupled ordinal'`: both destructured batch receipts were partial.
+   Green — `bun test tests/codex-native-calls.test.ts -t 'retained coupled ordinal'`: 2 passed, with three and two bound call labels respectively.
+
+Additional regressions preserve submitted spawns inside interpolated and
+concatenated output, reject ambiguous bindings and composition, and keep
+private source bytes out of observations. The focused native-call/control
+suite passed 94 tests. These checks do not replace the full GitHub CI gate
+on the PR's exact published commit.
+
+## Fresh native trials
+
+Fresh trials use Darrow checkpoint `67f4fcdb`, native Codex 0.162.1 app-server,
+candidate and semantic grader `gpt-6-luna/medium`, passive ownership, N=1,
+jobs=1, threshold=1, and a 1,200,000 ms timeout with retained diagnostics.
+They explicitly select the changed Sevro source worktree through
+`SEVRO_CHECKOUT`; they are development evidence, not published-package trials.
+
+The direct trial, run `510f99df-882f-48fe-b893-d4b6fba8864d`, completed with
+9/10 checks passing and the no-agent assertion unavailable. Its new submission
+29 maps a callback that invokes tools over a command array; submission 74 uses
+an output callback with a conditional expression. Both forms remain outside
+the [bounded inspection contract](../native-controls.md) and correctly retain
+partial receipts. The five original programs no longer cause that limitation.
+
+The coupled trial, run `7f9f5d8a-641e-4744-a986-05298100541c`, completed with
+10/11 checks passing and the no-agent assertion unavailable. Submissions 29,
+45, and 68 each use a `for ... of` output loop with a conditional expression
+and `String(...)` conversion. That output body is also outside the bounded
+subset and remains partial. Neither fresh run is a passing placement trial;
+their unavailable verdicts are preserved rather than treating zero accepted
+agents as proof of absence.

package/docs/evidence.md

@@ -8,6 +8,7 @@ Keep their observations intact:
 - [Claude continuation](claude-continuation-validation.md)
 - [Concurrency](concurrency-validation.md)
 - [Code Mode control observations](evidence/code-mode-controls-71.md)
+- [Code Mode template and batch programs](evidence/code-mode-programs-85.md)
 - [Candidate Codex configuration and user-skill state](evidence/codex-state-73/README.md)
 - [Configuration roots](configuration-root-validation.md)
 - [Fixture cleanup](fixture-cleanup-validation.md)

package/docs/getting-started.md

@@ -5,6 +5,27 @@ Darrow checkout, Codex/Claude login, or model credentials are required. The
 adapter returns `ready`; Sevro grades that response against `^ready$`.
 This teaches the runner lifecycle, not the quality of an actual model.
 
+<a id="built-in-demo-in-this-checkout"></a>
+
+## Built-in demo
+
+With [Sevro installed and on `PATH`](installing.md#make-the-command-available), run:
+
+```sh
+sevro demo
+```
+
+It prints `execution=completed grading=completed task=passed` and an absolute
+`evidence=` path under `.sevro/results` in your current directory. The demo owns
+its packaged case and adapter, uses a separate temporary project, and ignores
+your project's `sevro.json` and native configuration. No credentials are needed.
+Effective run settings appear on stderr before evaluation. Add `--json` for one
+versioned result on stdout.
+
+Continue with [the initialized evaluation workflow](evaluation-workflow.md) to
+create response, coding or repository-skill assertions, prepare them, inspect
+progress and access the latest result without copying an evidence path.
+
 ## From an installed package
 
 Prepare a new directory:
@@ -16,8 +37,8 @@ bun init -y
 ```
 
 Install the [current release](installing.md#current-release) there, then return
-here to run the example. Read [version differences](installing.md#published-package-and-checkout)
-for the current docs, source-available license, and earlier BSL releases.
+here to run the example. See [licensing](licensing.md) for the current terms and
+the licenses retained by historical releases.
 
 Make the local installation available on `PATH` for this shell, then call
 `sevro` directly. Bun must also be on `PATH`.

package/docs/identity-v1.md

@@ -32,7 +32,10 @@ The CLI derives `runnerBuildDigest` from sorted packaged file paths and their
 SHA-256 bytes under `src/`, `schemas/`, `docs/`, and `examples/`, plus `README.md` and
 `package.json`. For a Git project, `projectDigest` binds the revision and dirty
 patch digest without the checkout path. Without a revision it hashes a bounded
-file snapshot, excluding `.git`, results, and run-state storage. A caller may
+file snapshot, excluding `.git`, results, and run-state storage. Results and
+run-state storage are also excluded from untracked Git identity, so repeated
+project-local output does not change the project digest. Tracked source changes
+remain included, even under a selected storage directory. A caller may
 provide explicit 64-character digests for controlled development runs.
 
 The prefix separates this digest from component digests and future identity
@@ -48,6 +51,17 @@ The effective positive trial job limit is retained as `configuration.redacted.jo
 and enters `configurationDigest`. Changing parallelism changes evaluation identity,
 even when the condition, host route, trial count, and assessment threshold match.
 
+CLI [saved run settings](run-settings-v1.md) resolve before evaluation. Equivalent
+manifest and explicit selections produce the same semantic inputs. CLI evidence
+also retains `configuration.redacted.runSettings` for shell isolation, explicit
+protected roots, deprecated runtime selections, selected native timeouts and
+Claude project-settings authority. These values enter the
+configuration digest. Optional `configuration.resolved` stores the whitelisted
+operator preview outside that digest, including operational paths and the
+selected manifest location. Relocating output storage alone does not alter
+identity. A tracked manifest remains project content under the normal project
+identity rules.
+
 Extension runs retain the operator-supplied redacted extension configuration
 under `configuration.redacted.extensionConfiguration`, alongside
 `extensionConfigurationDigest`. The retained copy is the same snapshot used

package/docs/installing.md

@@ -1,8 +1,9 @@
 # Install, update, or remove Sevro
 
 Use Bun 1.3.13 for this TypeScript/Bun CLI. Installation does not make it a
-Node-only executable. Full validation and native isolation target macOS;
-Linux and Windows are unverified.
+Node-only executable. Full validation and native isolation target macOS and
+Ubuntu 24.04 x64. See the [bounded platform evidence](native-hosts.md#validated-platform-scope);
+Windows remains unverified.
 
 ## Install locally
 
@@ -22,10 +23,10 @@ Local installation records the selected version in the project lockfile.
 
 ## Current release
 
-The current release is `0.1.0-rc.12`. Install this exact version:
+The current release is `0.1.0-rc.13`. Install this exact version:
 
 ```sh
-bun add --exact @bjoernrochel/sevro@0.1.0-rc.12
+bun add --exact @bjoernrochel/sevro@0.1.0-rc.13
 ```
 
 <!-- sevro-current-release:end -->
@@ -46,17 +47,16 @@ no adjustment is needed. Bun must also be on `PATH`: the executable uses
 
 ## Published package and checkout
 
-The [current release](#current-release) includes runtime
-configuration, native goals, selected plugin hooks, current onboarding, and
-[source-available licensing terms](licensing.md). Earlier `rc.1` and `rc.2`
-packages retain BUSL-1.1. The license transition began with `0.1.0-rc.3`.
-Source checkouts can include changes beyond their
-package version; compare the exact release tag when establishing provenance.
+See [licensing](licensing.md) for Sevro's source-available terms and historical
+licensing transitions.
 
-The candidate npm package contains sources, schemas, examples, documentation,
+The npm package contains sources, schemas, examples, documentation,
 LICENSE, and contribution guidance. It excludes tests, developer scripts, Git
 metadata, and repository guide mounts. Use a source checkout for the guide.
 
+Source checkouts can include changes beyond their package version; compare the
+exact release tag when establishing provenance.
+
 ## Work from source
 
 ```sh

package/docs/native-controls.md

@@ -22,10 +22,14 @@ one receipt per native `exec` submission, with its native `ordinal`, inspection
 The index is local to that submission; native ordinals are not synthesized.
 The original direct-call list and total `submittedExecCalls` stay unchanged.
 
-The current source checkout statically inspects bounded straight-line Code Mode
+Sevro statically inspects bounded straight-line Code Mode
 programs without executing them. It accepts literal tool calls, constant result
-bindings, direct `text`/`store` output, and literal `Promise.all`/`allSettled`
-batches with result-only `forEach(text)` or `for ... of` output. It requires one
+bindings, template interpolation and `+` composition of inspected expressions,
+direct `text`/`store` output, and literal `Promise.all`/`allSettled` batches.
+Batch results may use flat constant array bindings or result-only
+`forEach(text)` or `for ... of` output. Destructuring defaults, rest elements,
+holes, nested bindings, duplicate names, and shadowed globals remain unsupported.
+It requires one
 unique, later native completion for the same call ID with an intact successful
 script envelope. Tool argument strings, comments and printed tool-looking text
 do not become call labels. A rejected tool request returned by a completed

package/docs/native-hosts.md

@@ -6,6 +6,23 @@ Claude Code), a supported native CLI, and model
 authentication. Complete commands/rules live in the [CLI reference](development-cli.md)
 and [Codex host reference](codex-host.md).
 
+## Validated platform scope
+
+The full source quality gate has passed on macOS arm64 and Ubuntu 24.04 x64.
+Ubuntu evidence includes [the successful source CI run for `cd7542bf`](https://github.com/BjRo/sevro/actions/runs/38692971517).
+That run exercises deterministic native-host protocols and real filesystem,
+process, network and shell isolation with the pinned prerequisites in
+[the quality contract](typescript-quality.md#environment-and-ci). It does not
+establish authenticated model success for every host/model combination.
+This is prior source evidence; changed candidates still need their own green CI.
+Other Linux distributions and Windows are unverified.
+
+On Ubuntu, install `bubblewrap`, `ripgrep`, and `socat`. Unprivileged user
+namespaces must work; Ubuntu's AppArmor policy may need a `bwrap` profile.
+[CI's setup script](../scripts/setup-ci-linux.sh) supplies and probes the
+supported runner setup. Use it as an explicit development setup step where
+appropriate; do not assume all Linux hosts have that configuration.
+
 ## Codex
 
 Select `--host codex`, absolute `--codex-bin` and `--codex-auth-file` paths,