humanish 0.107.0 → 0.108.0

package/docs/architecture/terminal-product-route.md

@@ -1,20 +1,14 @@
-# Terminal-product real-agent route (issue #154)
+# Terminal-product route
 
-Date: 2026-06-16 (runtime-auth contract updated 2026-09-05)
-
-Status: live terminal-product route shipped in `0.8.0`. The in-sandbox backend,
-command-scoped credential placement, exact-id cleanup proof, an interventions ledger,
-cost/no-spend ledger, caps, and product scoring/feedback hooks are implemented;
-the kept 2026-07-09 live receipt verifies 15/15 checks and `share_ready` at a
-`$0` cap. That capability receipt is not adopter replacement: no deletion
-branch has yet removed the reference adopter's bespoke generic study harness.
-See the goal packet
-([`docs/goals/terminal-product-lane/goal.md`](https://github.com/danielgwilson/humanish/blob/main/docs/goals/terminal-product-lane/goal.md))
-for the full slice plan and the safety contract.
+The live terminal-product route has shipped since `0.8.0`, with the in-sandbox runtime,
+command-scoped credential placement, exact-id cleanup proof, an interventions ledger, a cost and
+no-spend ledger, caps, and product scoring and feedback hooks. The
+[original plan](https://github.com/danielgwilson/humanish/blob/main/docs/history/goals/terminal-product-lane/goal.md)
+holds the build order and the safety contract.
 
 ## What this is
 
-A lab route for **terminal-product real-agent studies**: a real autonomous coding
+A study route for **terminal-product real-agent studies**: a real autonomous coding
 agent (Codex) discovering and using a CLI/product from its **public surfaces
 only**, running **inside an E2B shell** with declared runtime-auth placement and
 spend/time caps, emitting durable terminal/substrate/cost/no-spend/cleanup/
@@ -23,26 +17,26 @@ routes. It tests whether an autonomous agent can discover and use a CLI/product
 surface from public materials. It does not test whether a browser can click a
 local web app.
 
-It rides the established route-addition pattern (proven by the scripted-browser
-and local-app routes): a new `subject.source` × `execution.target`, a routing
-predicate, a backend enum + dispatch, a registered actor that declares the run kind in its capabilities,
+It follows the pattern the scripted-browser and local-app routes added: a new
+`subject.source` × `execution.target` pairing, a `terminal` case in `routeOf(config)`
+and its dispatch, a registered actor that declares the run kind in its capabilities,
 fail-closed cross-validation, and forward-declared warnings.
 
 ## The composition
 
-| Axis                                  | Value                                                                                                                                                     |
-| ------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `subject.source`                      | `terminal-product`                                                                                                                                        |
-| `subject.product`                     | `{ name, publicSurfaces[], install?, workdir?, upload? }`: the only world the agent sees                                                                  |
-| `execution.target`                    | `e2b-terminal` (or absent → implied)                                                                                                                      |
-| `execution.terminal`                  | `{ transport: exec-stream, stdin: disabled }`                                                                                                             |
-| `execution.runtimeAuth`               | `openai-env` (default) or opt-in `openai-egress`; names-only durable evidence                                                                             |
-| `execution.runtime.version`           | Optional exact `@openai/codex` version; observed before keyed execution                                                                                   |
-| `actors[0].model` / `reasoningEffort` | Passed to Codex as `--model` (default `gpt-5.6-sol`) and `-c model_reasoning_effort`; declarations, not observed provider identity                        |
-| `scenario.caps`                       | `{ maxUsd, maxJobs, maxMinutes }`: the blast-radius budget; `maxUsd > 0` is refused unless a `costProbe` measures spend                                   |
-| `policies`                            | `allowPrivateRepoAccess` / `allowProviderCredentials` / `allowPaymentCredentials` / `allowGitHubMutation`, all DEFAULT FALSE                              |
-| `actors[0].type`                      | `codex-exec`: a registered terminal actor (`keyPlacement: in-sandbox-command-scoped`)                                                                     |
-| route                                 | `terminal` → `runTerminalProductLab` ([`src/routes/terminal/route.ts`](https://github.com/danielgwilson/humanish/blob/main/src/routes/terminal/route.ts)) |
+| Axis                              | Value                                                                                                                                                     |
+| --------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `subject.source`                  | `terminal-product`                                                                                                                                        |
+| `subject.product`                 | `{ name, publicSurfaces[], install?, workdir?, upload? }`: the only world the agent sees                                                                  |
+| `execution.target`                | `e2b-terminal` (or absent → implied)                                                                                                                      |
+| `execution.terminal`              | `{ transport: exec-stream, stdin: disabled }`                                                                                                             |
+| `execution.runtimeAuth`           | `openai-env` (default) or opt-in `openai-egress`; names-only durable evidence                                                                             |
+| `execution.runtime.version`       | Optional exact `@openai/codex` version; observed before keyed execution                                                                                   |
+| `actor.model` / `reasoningEffort` | Passed to Codex as `--model` (default `gpt-5.6-sol`) and `-c model_reasoning_effort`; declarations, not observed provider identity                        |
+| `caps`                            | `{ maxUsd, maxJobs, maxMinutes }`: the blast-radius budget; `maxUsd > 0` is refused unless a `costProbe` measures spend                                   |
+| `policies`                        | `allowPrivateRepoAccess` / `allowProviderCredentials` / `allowPaymentCredentials` / `allowGitHubMutation`, all default false                              |
+| `actor.type`                      | `codex-exec`: a registered terminal actor (`keyPlacement: in-sandbox-command-scoped`)                                                                     |
+| route                             | `terminal` → `runTerminalProductLab` ([`src/routes/terminal/route.ts`](https://github.com/danielgwilson/humanish/blob/main/src/routes/terminal/route.ts)) |
 
 Routing is `routeOf` (`src/lab/plan.ts`). It sends every `terminal-product` subject to
 this route, even with an unregistered actor, so this route refuses the actor.
@@ -52,10 +46,10 @@ warnings.
 ## Repeating a terminal study with the same runtime
 
 ```yaml
-actors:
-  - type: codex-exec
-    model: gpt-5.6-sol
-    reasoningEffort: low
+actor:
+  type: codex-exec
+  model: gpt-5.6-sol
+  reasoningEffort: low
 execution:
   target: e2b-terminal
   runtime:
@@ -75,7 +69,7 @@ the requested model and where it came from, declared effort, and the usage granu
 The observed executable version also appears as `providerVersion`.
 
 Codex's `--json` stream does not name the model it used, and its built-in default can change
-with any release. So the route always passes `--model`: the lab's `actors[0].model`
+with any release. So the route always passes `--model`: the study's `actor.model`
 (`modelStatus: declared`), or humanish's participant default `gpt-5.6-sol`
 (`modelStatus: humanish_default`). Bundles written before 0.107.0 record
 `runtime_default_unobserved` with no requested model.
@@ -87,7 +81,7 @@ requested model. Codex `turn.completed` usage sums every request in a turn, so n
 size is known and no per-request long-context tier can be applied. The estimate prices every token
 at the base tier, with cached input at the cached rate, and says so with
 `basis: aggregated_turns_base_rate`. It is an estimate, not a measurement. The cost ledger
-checked against `scenario.caps.maxUsd` keeps the provider line unmeasured, and the studied
+checked against `caps.maxUsd` keeps the provider line unmeasured, and the studied
 product's no-spend boundary still needs separate interpretation.
 
 ## Runtime auth: raw-key placement and remaining provider access
@@ -131,11 +125,11 @@ make authenticated requests to that host from sandbox creation until teardown,
 including bootstrap/setup commands and commands launched outside Codex. Calls
 made outside Codex may be absent from its usage ledger. This mode does not impose
 a provider-side spending limit, restrict models/API paths, or make
-`scenario.caps.maxUsd` a preventive provider budget. A hard provider budget needs
+`caps.maxUsd` a preventive provider budget. A hard provider budget needs
 a separately enforced control; do not infer zero spend from an unmeasured ledger
 line.
 
-Public internet discovery stays unrestricted unless the lab already declares
+Public internet discovery stays unrestricted unless the study already declares
 `execution.egressAllow`. The mode preserves that allowlist and its deny-all
 fallback without adding hosts. If an allowlist omits `api.openai.com`, provider
 requests can fail. E2B domain allowlists are routing controls rather than strict
@@ -155,7 +149,7 @@ and [E2B's CA installer](https://github.com/e2b-dev/infra/blob/main/packages/env
 E2B's installed
 SDK documents that transformed headers override request headers. Deterministic
 request/redaction tests do not establish live wire behavior. The [2026-09-05
-transport receipt](https://github.com/danielgwilson/humanish/blob/main/docs/goals/terminal-product-lane/receipts/2026-09-05-runtime-egress-auth.md)
+transport receipt](https://github.com/danielgwilson/humanish/blob/main/docs/evidence/terminal-product/2026-09-05-runtime-egress-auth.md)
 records the controlled live header/auth checks and their scope.
 
 ## Runtime prerequisite
@@ -180,7 +174,7 @@ checks Node/npm in both ordinary and sudo shells after installation. The existin
 runtime fast path preserves user-specific installations; a later sudo product
 install can still fail if that installation is absent from sudo's PATH.
 
-The [global executable receipt](https://github.com/danielgwilson/humanish/blob/main/docs/goals/terminal-product-lane/receipts/2026-09-05-global-npm-prefix.md)
+The [global executable receipt](https://github.com/danielgwilson/humanish/blob/main/docs/evidence/terminal-product/2026-09-05-global-npm-prefix.md)
 records the regression found after the initial runtime-only proof and its stock
 desktop checks. npm documents [global executable locations](https://docs.npmjs.com/cli/v10/configuring-npm/folders#executables)
 and the [distribution built-in configuration](https://docs.npmjs.com/cli/v10/configuring-npm/npmrc#built-in-config-file).
@@ -212,99 +206,65 @@ blast radius is bounded by key scoping and budgets, not by hoping._
 
 The inversion is declared as registry metadata, not a code convention: the
 terminal actor's capabilities carry `keyPlacement: "in-sandbox-command-scoped"`.
-SLICE 1 shipped the DECLARED field + value (the contract was honest about where
-the key would go); SLICE 2's engine added command-scoped injection (only into the
-per-command `envs` of the `codex` invocation, never `Sandbox.create({envs})`)
-keyed off that capability, plus the deny-by-default credential allowlist, the
-positive-allowlist sandbox metadata, the cleanup proof, the interventions ledger,
-and a minimal fail-closed cap.
-
-## Historical SLICE 1 scope (DRY-RUN only when shipped)
-
-At SLICE 1, `runTerminalProductLab` implemented only the dry-run path: it built a valid
-`humanish.run-bundle.v1` contract bundle, honestly labeled contract-only, with:
-
-- the subject declared as a terminal-product with its public surfaces, provenance
-  **UNPINNED** (the agent drives public surfaces, not a clone; invariant 5);
-- the author mission recorded as plaintext (public-safe committed lab text) + a
-  **digest** of the full composed prompt (nothing beyond the author mission goes
-  plaintext);
-- the caps / deny-by-default policies / runtime-auth channel recorded as
-  declarations (names only; invariant 1);
-- a terminal-kind stream that is an honest **contract placeholder**: stdin
-  disabled, empty tail, `transport: snapshot`, **not** `pty` (captured
-  non-interactive exec output is never an interactive PTY; invariant 6 + the
-  goal packet's PTY ruling). SLICE 2 later added redacted exec-stream capture;
-- empty/placeholder ledgers (substrate lifecycle, command log, terminal event
-  stream, interventions, cost) that SLICE 2/3 later filled.
-
-The dry-run bundle passed the existing `verifyRun`. Terminal-specific verifier
-checks (terminal/transcript presence, lifecycle, cleanup, interventions,
-metadata allowlist, no-credential-in-artifacts, no-spend) landed in SLICE 2/3.
-
-At SLICE 1, a non-dry-run call returned a structured
-`HUMANISH_TERMINAL_AGENT_NOT_IMPLEMENTED` failure before launch or spend.
-SLICE 2 implemented the real session.
-
-SLICE 1 declared the DI seams SLICE 2 needed (`loadModule`, `buildSandbox`,
-`runtimeAuthEnv`, `detachedTimers`) on a terminal hook bag; only the dry-run path was
-implemented in that slice. The bag is gone. The route reads `env` and `scorer` from its
-options (`src/routes/terminal/types.ts`), and a test passes its seams (`desktopModule`,
-`renderObserver`, `now`, `costProbe`) as `LabDeps` (`src/lab/lab-deps.ts`).
-
-## SLICE 4: the product-adapter extension seam (layer 6)
-
-This route is proof-roadmap **layer 6**: an adopter attaches product-specific
-scoring + feedback as a THIN in-repo extension WITHOUT forking core. SLICE 4
-ships the SEAM. Core ships no built-in product scorer; the adopter's scorecard
-lives in the adopter's repo:
+The route keys off that capability and injects the key only into the per-command
+`envs` of the `codex` invocation, never `Sandbox.create({envs})`. The route also
+has a deny-by-default credential allowlist, positive-allowlist sandbox metadata,
+the cleanup proof, the interventions ledger and a minimal fail-closed cap.
+
+## Test seams
+
+The route reads `env` and `scorer` from its options (`src/routes/terminal/types.ts`), and a test
+passes its seams (`desktopModule`, `renderObserver`, `now`, `costProbe`) as `LabDeps`
+(`src/lab/lab-deps.ts`).
+
+## The product-adapter extension seam
+
+An adopter attaches product-specific scoring and feedback as a thin in-repo extension, without
+forking core. Core ships the seam and no built-in product scorer; the adopter's scorecard lives in
+the adopter's repo:
 
 - **Exported contract types** a thin adapter types against from the package barrel
   (`humanish`) alone, never through a deep `src/` import: `RunBundle`,
   `RunFeedbackCandidate`, `RunAdapterScore`, `RunAdapterArtifact`, `ActorTrace`,
   `AdapterScorerModule` and `TerminalProductScoringContext`. The ledger, cost and
   no-spend shapes are reached through that context's fields, as
-  `TerminalProductScoringContext["ledgers"]`. Before this slice these were not
-  exported, which forced a fork (a thin adapter could not type against the bundle),
-  the gap issue #154 acceptance #8 names.
-- **A registrable scorer / feedback module**, `RunLabOptions.scorer` (an
+  `TerminalProductScoringContext["ledgers"]`.
+- **A registrable scorer / feedback module**, `RunStudyOptions.scorer` (an
   `AdapterScorerModule`): `score?(ctx) => RunAdapterScore | Promise<…>` and
   `deriveFeedback?(ctx) => RunFeedbackCandidate[] | Promise<…>`, where this route's
   `ctx` is a `TerminalProductScoringContext`. The older `terminalHooks.score` and
   `terminalHooks.deriveFeedback` were removed with the bag. The route calls the
-  hooks over the FULLY-ASSEMBLED, redacted evidence and attaches the results
-  (`bundle.adapterScore`, appended `bundle.feedbackCandidates`) WITHOUT core knowing
+  hooks over the fully-assembled, redacted evidence and attaches the results
+  (`bundle.adapterScore`, appended `bundle.feedbackCandidates`) without core knowing
   any product noun. Default (no hook) behavior is unchanged: the mission-based verdict
   stands alone.
 - **Adapter-namespaced product nouns.** Product-specific concepts (public
   CLI/product command observed, hosted product success-or-blocker, feedback
   id/draft, media/job/asset ids, no-media/no-provider-spend proof,
-  defection/friction risk) ride ONLY under a single namespaced field
+  defection/friction risk) ride only under a single namespaced field
   (`RunFeedbackCandidate.adapter: { namespace, data }` and
   `RunAdapterScore.{namespace, data}`) so core's enums stay product-agnostic and
   a future inert-field audit never misfires. No adopter noun is hardcoded into a
   core enum (avoiding closed-taxonomy rot); `e2b-terminal` is added to the
-  substrate enum so a terminal-agent candidate names its substrate honestly.
+  substrate enum so a terminal-agent candidate names the substrate it ran on.
 
-The seam is fail-closed: the route scrubs+redacts the returned payloads and DROPS
+The seam is fail-closed: the route scrubs+redacts the returned payloads and drops
 any malformed score/candidate with a warning, and `verifyRun` re-checks the
 surviving shapes, so a bad extension never poisons a verifiable bundle. Proven by
 `tests/routes/terminal/product-adapter-seam.test.ts` (a thin in-repo example adapter
 typing against the barrel only, registering a scorer, attaching namespaced nouns,
-emitting a candidate; the bundle verifies). At SLICE 4 this was contract proof,
-not a live rung; the later end-to-end route receipt is linked from the status
-note.
+emitting a candidate; the bundle verifies). That test is a contract proof; the
+live end-to-end route receipt is linked from the status note.
 
-The adopter's real scorecard is its OWN thin extension. The end-to-end route's
-live receipt is kept under the terminal-product goal, and true duplex PTY replay
-is deferred to SLICE 5.
+The adopter's real scorecard is its own thin extension. The end-to-end route's
+live receipt is kept under the terminal-product goal. Duplex PTY replay is not
+built.
 
 ## The reference adopter (codename-neutral)
 
-The requesting adopter is a public creative-CLI product (see issue #154 for its
-concrete public surfaces). Committed source and docs here stay codename-neutral
-per the public-surface scan; the committed CI fixture
-([`humanish/labs/terminal-product-demo.yaml`](https://github.com/danielgwilson/humanish/blob/main/humanish/labs/terminal-product-demo.yaml))
-uses a FICTIONAL mock CLI (`widgetsmith-cli`) with `example.com` surfaces. The
-adopter's real public surfaces appear only in operator-run docs and the GitHub
-issue, never in scanned committed text.
+The requesting adopter is a public creative-CLI product. Committed source and docs here
+stay codename-neutral per the public-surface scan; the committed CI fixture
+([`humanish/studies/terminal-product-demo.yaml`](https://github.com/danielgwilson/humanish/blob/main/humanish/studies/terminal-product-demo.yaml))
+uses a fictional mock CLI (`widgetsmith-cli`) with `example.com` surfaces. The adopter's
+real public surfaces appear only in operator-run docs and a GitHub issue, never in
+scanned committed text.

package/docs/contracts/README.md

@@ -0,0 +1,24 @@
+# Contracts
+
+Each page describes a shape that code outside humanish can depend on. A documented field is API;
+the types, parsers and validators in `src/` are the source of truth when a page and the code
+disagree.
+
+- [schemas.md](schemas.md): every `humanish.*` schema id, the study manifest, the library options
+  (`RunStudyOptions`) and the exports removed in 0.107.0.
+- [core.md](core.md): the records a run writes under `.humanish/runs/<id>/` and how each route
+  starts a run.
+- [run-bundle.md](run-bundle.md): `humanish.run-bundle.v1`, the evidence contract that `verify`
+  checks.
+- [policy.md](policy.md): credential, network, spend, redaction, sharing and assisted-run
+  boundaries.
+- [feedback.md](feedback.md): feedback candidates, drafts and issue URLs, which never mutate
+  GitHub.
+- [study-analysis.md](study-analysis.md): post-run analysis of retained participant evidence.
+- [study-costs.md](study-costs.md): what `humanish stats` counts as spend.
+- [errors.md](errors.md): the error code families, where each code appears, and the human
+  error shape on stderr.
+- [adapter-admission.md](adapter-admission.md): the admission limit a custom provider can raise
+  before a request is sent.
+- [adapter-fixtures.md](adapter-fixtures.md): the committed adapter fixtures and the parity checks
+  over them.

package/docs/contracts/adapter-admission.md

@@ -1,18 +1,18 @@
 # Adapter admission limits
 
-Library callers can throw `CuaAdmissionLimitError` from a custom `CuaProvider`
+Library callers can throw `ComputerUseAdmissionLimitError` from a custom `ComputerUseProvider`
 or the `fetchFn` supplied to `createOpenAiResponsesProvider` when a configured
 local control limit refuses a request **before provider dispatch**:
 
 ```ts
-import { CuaAdmissionLimitError, createOpenAiResponsesProvider } from "humanish";
+import { ComputerUseAdmissionLimitError, createOpenAiResponsesProvider } from "humanish";
 
 const provider = createOpenAiResponsesProvider({
   apiKey,
   fetchFn: async (url, init) => {
     if (localLimitReached()) {
       await recordLocalAdmissionRefusal();
-      throw new CuaAdmissionLimitError();
+      throw new ComputerUseAdmissionLimitError();
     }
     return transport(url, init);
   },

package/docs/contracts/adapter-fixtures.md

@@ -1,10 +1,7 @@
 # Adapter Fixture Parity Contract
 
-Date: 2026-06-02 (current-state note updated 2026-07-14)
-
-Status: committed contract fixtures with passing parity checks. A fixture
-proves that core can carry an adapter-owned evidence shape; it does not prove a
-live adopter integration or satisfy a deletion-branch depth phase.
+The committed fixtures pass their parity checks. A fixture proves that core can carry an
+adapter-owned evidence shape; it does not prove a live adopter integration.
 
 ## Purpose
 

package/docs/contracts/core.md

@@ -1,8 +1,6 @@
 # Core Contract
 
-Date: 2026-06-02 (current-state note updated 2026-09-30)
-
-Status: each route mints its run id and builds its bundle, and starts the run
+Each route mints its run id and builds its bundle, and starts the run
 through the run scope in `src/run/run.ts`. `startRun` creates
 `.humanish/runs/<id>` and begins `status.json`; the `Run` it returns publishes
 `run.json`, its projections and the latest pointer. `src/run/paths.ts` holds the

package/docs/contracts/errors.md

@@ -0,0 +1,62 @@
+# Error codes
+
+A failed command or library call reports a code and a message. The code is the stable part: a
+rename or removal gets a CHANGELOG entry in the release that makes it. Messages may change in any
+release.
+
+## Where a code appears
+
+- `--json`: the envelope has `ok: false` and `error: { code, message }`, and the command exits 2.
+  This output is the interface for scripts and agents. Two exceptions:
+  - A command-line usage error, such as an unknown option or a missing argument, prints
+    Commander's message on stderr, exits 1 and prints no JSON.
+  - `keys` and the `comms` connection commands report a failure as `ok: false` with a `message`
+    and no `error` field.
+- Human mode: two or three lines on stderr.
+
+  ```text
+  humanish run failed: Study not found: nope. Look in humanish/studies/ or humanish/labs/, or pass a .yaml path.
+  code: HUMANISH_STUDY_NOT_FOUND
+  next: humanish study list
+  ```
+
+  A result with no code (`keys`, `comms`) prints no `code:` line. The `next:` line comes from a
+  table in `src/cli/io.ts` keyed by code, which today holds `HUMANISH_STUDY_NOT_FOUND`. Other
+  codes get no `next:` line, though some messages name a command, as the run-not-found message
+  names `humanish runs`. Stdout keeps a result's other lines: a failed run
+  prints its run id, route and participants there, and a failed `verify` prints its failing
+  checks there, since they are its result. Before 0.108.0, human mode printed the code and message
+  on stdout.
+
+- Library: the result objects `runStudy` and the analysis entry points return carry the same
+  `error.code`.
+
+## Families
+
+| Family                 | Codes | Emitted by                                                               | Appears in                                                              |
+| ---------------------- | ----- | ------------------------------------------------------------------------ | ----------------------------------------------------------------------- |
+| `HUMANISH_*`           | 137   | every CLI command and route result                                       | JSON `error.code`, library `error.code`, human `code:` line             |
+| `ANALYSIS_*`           | 86    | `humanish analyze` and the analysis service (`src/analysis/`)            | JSON `error.code` of analysis results                                   |
+| `AUTOMATIC_ANALYSIS_*` | 21    | the post-run analysis job                                                | `automaticAnalysis.reason` on a run result and the job record           |
+| `analysis_*` lowercase | 29    | analysis execution                                                       | `error` fields in analysis artifacts and execution receipts             |
+| `codex_*` lowercase    | 13    | the Codex CLI readiness check (`src/actors/codex/`, `src/lab/doctor.ts`) | doctor rows and analysis readiness, such as `codex_unsupported_version` |
+
+Counts are the distinct quoted codes in `src/` on 2026-10-03.
+
+The lowercase families are values recorded inside artifacts and receipts, and an artifact keeps
+the code it was written with. Automatic analysis reads two of them back:
+`analysis_admission_estimate_exceeded` becomes the reason `AUTOMATIC_ANALYSIS_ADMISSION_EXCEEDED`,
+and `analysis_budget_exceeded` on a default analysis prints the hint to rerun with
+`humanish analyze --max-cost`. Validation also accepts a partial artifact whose error is
+`analysis_admission_estimate_exceeded`.
+
+Share-safety reasons in `humanish verify` (`VERIFY_FAILED`, `RAW_SCREENSHOTS` and the rest) are
+grades, not errors; [run-bundle.md](run-bundle.md) lists them.
+
+## Renames
+
+0.108.0 renamed the codes that said lab: `HUMANISH_LAB_*` is `HUMANISH_STUDY_*`,
+`HUMANISH_CUA_LAB_*` is `HUMANISH_COMPUTER_USE_*`, `HUMANISH_CONCURRENT_SHARED_WORLD_LAB_*` is
+`HUMANISH_SHARED_WORLD_*`, and the terminal and scripted families drop `_LAB`. It also renamed
+`HUMANISH_INVALID_SIM_COUNT` to `HUMANISH_INVALID_PARTICIPANT_COUNT`. A run saved before a rename
+keeps the codes it was written with.

package/docs/contracts/feedback.md

@@ -1,10 +1,7 @@
 # Feedback Contract
 
-Date: 2026-06-01 (current-state note updated 2026-07-14)
-
-Status: local feedback candidate, draft, verification, Markdown, and issue-URL
-generation are shipped. These commands do not mutate GitHub, and public output
-fails closed unless the run verifies as `share_ready`.
+Feedback candidates, drafts, verification, Markdown and issue URLs ship. These commands never
+mutate GitHub, and public output fails closed unless the run verifies as `share_ready`.
 
 ## Purpose
 
@@ -78,10 +75,12 @@ was not repeated in the message trace.
 ### `draft`
 
 Builds structured feedback from the first usable run candidate, or the candidate
-selected with `--candidate`. With no candidate, a dry run produces a contract
-follow-up and a live run produces a summary of its recorded review. These
-fallbacks do not add a finding to the candidate list. All drafts require a
-verified `share_ready` run and are written under the run bundle, not GitHub.
+selected with `--candidate`. With no candidate, a live run produces a summary of
+its recorded review; that fallback does not add a finding to the candidate list.
+A dry run tests no product behavior, so `draft`, `verify`, `issue` and
+`issue-url` refuse it with `HUMANISH_FEEDBACK_REQUIRES_LIVE_RUN`. All drafts
+require a verified `share_ready` live run and are written under the run bundle,
+not GitHub.
 
 ### `verify`
 

package/docs/contracts/policy.md

@@ -1,14 +1,9 @@
 # Policy Contract
 
-Date: 2026-06-02 (current-state note updated 2026-07-14)
-
-Status: shipped policy reference for credential, network, spend, redaction,
-sharing, and assisted-run boundaries. Support remains route-specific; the
-parser, route validation, and verifier determine whether a declared field is
-consumed, rejected, or reported as a warning.
-
-Safety amendment (2026-07-14): beginning with `0.15.1`, stored provider IDs are
-evidence and never authorize core provider mutation.
+This page is the policy reference for credential, network, spend, redaction, sharing and
+assisted-run boundaries. Support is route-specific: the parser, route validation and the verifier
+decide whether a declared field is consumed, rejected or reported as a warning. Stored provider
+ids are evidence and never authorize core provider mutation.
 
 ## Purpose
 
@@ -112,7 +107,7 @@ Spend policy names when provider costs may be incurred.
 | Mode                     | Meaning                                                                                            |
 | ------------------------ | -------------------------------------------------------------------------------------------------- |
 | `no_spend`               | No provider calls that can bill.                                                                   |
-| `dry_run_only`           | Only local contract proof; no live substrate.                                                      |
+| `dry_run_only`           | Only a local dry run; no live substrate.                                                           |
 | `explicit_live_provider` | Provider calls allowed because required env var names are present and operator intent is explicit. |
 | `maintainer_approved`    | Reserved for publish, billing, or high-risk mutation workflows.                                    |
 
@@ -126,7 +121,7 @@ providerClasses:
   - model
   - desktop_substrate
 operatorIntent:
-  command: humanish lab run my-lab --json --no-open
+  command: humanish run my-study --json --no-open
   explicit: true
 budget:
   limit: unspecified
@@ -148,7 +143,7 @@ shapes, and fails closed on a match. It does **not** detect free-form PII/PHI
 those depends on using synthetic data and on reviewer judgment. Accordingly,
 `redaction: passed` means the automated secret/path scan found no matches, not a
 certification that the artifact is free of every class in the policy below. A
-first-class PII/PHI detector is planned (issue #108) and would move the listed
+first-class PII/PHI detector is [planned](https://github.com/danielgwilson/humanish/issues/108) and would move the listed
 PII classes from author-responsibility to enforced.
 
 Required redaction gates: