@mnstry/atelier 0.2.0-alpha.13 → 0.2.0-alpha.15

package/docs/guides/ontology-guide.md

@@ -0,0 +1,111 @@
+# Source-bound ontology guidance
+
+The experimental internal ontology guide prepares a private proposal for the
+existing knowledge workspace. It starts with a decision and preserves concept
+identity, exact source passages, directed relationship meaning and uncertainty.
+It does not edit a plan or source, confirm a participant answer, accept a mapping,
+or execute a decision.
+
+This module is not a supported package export or a new browser route. Existing
+knowledge-plan v1 files, the five knowledge views, sessions and package interfaces
+are unchanged. Maintainers can inspect its behavior with:
+
+```sh
+node --test test/ontology-guide.test.mjs
+```
+
+## One guided loop
+
+Choose a question in the current plan, then answer seven prompts:
+
+1. What decision will this help?
+2. What is the thing you are naming?
+3. How would you recognize the same thing next week?
+4. What close example should stay separate?
+5. Which source supports it?
+6. What does the relationship mean in each direction?
+7. What would change your mind?
+
+For an existing corpus, select bounded permitted evidence through the current
+knowledge context. For a blank workspace, retain its enrolled source directory
+and begin with a permitted observation/interview note or an explicit unknown.
+A synthetic practice observation remains labelled synthetic. An absent or broken
+enrollment is a source configuration error; it cannot establish an abstention.
+Both routes lead to source-owner review and a proposed next decision or test.
+Observed outcomes belong in Learn after they exist.
+
+The seven prompts map to the four existing Model fields: `concept`, `identity`,
+`relation` and `test`. A host should use the existing session answer/propose,
+confirmation and private-save operations. The guide returns wording; it does not
+send those operations. A saved draft remains a proposal. Agent-written wording
+still requires the existing explicit participant confirmation before saving.
+
+## Identity, evidence and limits
+
+Choose concepts by their existing IDs. Definitions, stable identity rules and
+`concept:` tags remain in the v1 plan. Examples, near misses, distinction
+rationale and disconfirming observations stay in private proposal metadata;
+they do not widen the closed plan schema. Identical definitions or identity
+rules require an explanation of how the concepts differ. Similar labels or
+aliases never establish identity. This small check cannot detect every semantic
+ambiguity; a reviewer still judges the proposed definitions and examples.
+
+The guide reads context through the existing local knowledge workspace. Evidence
+must match a unique selected source ID, its current full-file digest, a valid
+line range and its exact text. The handoff retains repo/path, digest, locator
+and passage, including qualifications. A source or plan change requires a new
+binding; earlier evidence and drafts remain historical. This is local-operator
+source binding, not a recipient permission check or hosted access decision.
+
+Explain each required relation using its existing forward predicate and both
+endpoint concepts. A reverse reading helps a person understand the original
+relation; it creates no inverse assertion. Evidence retrieval cannot establish a
+business claim, certainty or semantic truth.
+
+A proposed answer can say `supported` or `abstain`. These are the participant's
+proposed labels. `ready-for-human-review` checks draft completeness and source
+binding only. It does not certify that the answer is supported. Require stated
+scope and uncertainty, alternative explanations, and what could change the
+answer. Missing evidence suggests narrowing the claim or abstaining. Omitted
+sources remain explicit in the handoff; an abstention with omissions is marked
+`unverified-omissions`, so it cannot imply corpus-wide absence of evidence.
+
+## Review handoff
+
+The internal `createOntologyGuide()` adapter reads an already-loaded local
+workspace and a current question ID:
+
+- `prompts(workspace, questionId, entry)` returns ordered guidance for `corpus`
+  or `blank` entry and the existing view/Model field for each step.
+- `inspect(workspace, questionId, draft)` returns field-specific next actions,
+  verified source passages and retained retrieval limitations.
+- `prepareReview(workspace, questionId, draft, {basePlanText, planRef})` returns
+  an input body for the existing copy-only proposal store, or diagnostics.
+
+`draft` retains the workspace snapshot, raw base-plan SHA-256, entry route,
+decision, exact concept IDs with examples/counterexamples and identity basis,
+required relation readings, selected evidence pins, proposed answer/limits and
+disconfirming observation. An optional `proposedPlan` must still validate as v1.
+The source owner reviews changes before any canonical admission.
+
+The handoff binds exact raw plan bytes, retains complete before/proposed text
+and structural changes, and uses `proposal.copy-only` with `directWrite: false`
+and no apply endpoint. Oversize handoffs refuse with a request to narrow the
+change, before the existing store can truncate them. The guide never calls the
+store or persists a second draft ledger. A host explicitly supplies the body to
+the existing proposal workflow after reviewing the private audience.
+
+Review and source edit remain separate. The source owner inspects the exact diff,
+checks identity and passage meaning, applies an admitted change using the normal
+Git path, reruns knowledge check/evaluate, then starts a newly bound session.
+No source pin is replaced automatically to clear a failed check.
+
+Cross-repository concept mappings remain proposals preserving both source
+identities. Conversion to an edge-governance record requires the allocated
+stable repository/source descriptor, exact current source revisions and raw
+byte locators, plus the receiving review policy. This internal guide does not
+invent those values, emit accepted equivalence or activate a semantic edge.
+
+The synthetic tests exercise software behavior on the invented equipment library.
+They do not demonstrate a cold participant's comprehension, answer correctness,
+host ACL behavior or a completed human corpus/blank-start drill.

package/docs/{personal-workspace.md → guides/personal-workspace.md}

@@ -29,7 +29,7 @@ stable local enrollment keys; matching a recorded remote is an offline change
 check, not proof of upstream membership or provider identity.
 
 The module entrypoint is `src/personal-workspace/index.mjs`; its public package
-subpath is `@mnstry/atelier/personal-workspace`. The API consists of fifteen exports:
+subpath is `@mnstry/atelier/personal-workspace`. The API consists of sixteen exports:
 
 - `MANIFEST_SCHEMA` and `OVERLAY_SCHEMA`.
 - `PersonalWorkspaceRefusal`.
@@ -37,8 +37,8 @@ subpath is `@mnstry/atelier/personal-workspace`. The API consists of fifteen exp
 - `resolvePersonalWorkspace`.
 - `planPersonalGeneration`, `materializePersonalGeneration`, and
   `composePersonalWorkspace`.
-- `selectPersonalGeneration`, `selectionConfirmDigest`, and
-  `readPersonalSelection`.
+- `selectPersonalGeneration`, `selectionConfirmDigest`,
+  `readPersonalSelection`, and `readPersonalSelectionHead`.
 - `inventoryPersonalHome`.
 - `planPersonalRestore` and `restorePersonalInputs`.
 
@@ -117,7 +117,9 @@ remove only their own temporary files. Every failure is a
   that `readPersonalSelection` returns, so a choice shown against an older history
   does not apply. Selections are append-only, numbered, hash-chained records under
   `selections/`, each written completely before it is published, so a crash leaves
-  only a temporary file. Concurrent selections refuse `selection-concurrent`. An
+  only a temporary file. New records include a unique confirmation identity: confirming the
+  same generation against the same predecessor again produces a distinct record. Existing
+  v1 records without this identity remain readable. Concurrent selections refuse `selection-concurrent`. An
   ineligible generation refuses with its composition code, such as
   `stale-generation`.
 - `readPersonalSelection({ personalHome })` returns the current selection and
@@ -127,7 +129,17 @@ remove only their own temporary files. Every failure is a
   reordering refuses `selection-history-corrupt`. Truncating, or consistently
   rewriting, any trailing run of records (up to the whole history) yields another
   valid chain; it changes the returned `head`, so a host that needs to detect it
-  keeps the head it last observed and compares it.
+  keeps the head it last observed and compares it. The Obsidian maintenance
+  service persists the highest observed record number, accepted head and observed
+  record identities in its machine-private continuity state. A restart keeps that
+  evidence. A shorter history refuses until the removed records return or the person
+  makes one fresh confirmation (see [obsidian.md](obsidian.md)).
+- `readPersonalSelectionHead({ personalHome })` returns `{ selected, sequence,
+  head }` from the history alone, with `sequence` 0 while nothing is selected.
+  It composes nothing, so it does not say whether the selection is still
+  eligible; the chain is checked as above. It is for a host that composes
+  elsewhere, and that reads the head again to compare it with the one it acted
+  on.
 - `inventoryPersonalHome({ personalHome })` lists what these operations write, for
   review before any deletion the person chooses: the authored files, each
   generation with its eligibility, interrupted staging directories, every

package/docs/{research-starter.md → guides/research-starter.md}

@@ -108,7 +108,7 @@ demonstrate framing, research return, uncertainty, review and graph proposals.
 local ingestion, persistent Knowledge records, retrieval and graph projection.
 The tests are synthetic conformance evidence, not real research validation.
 
-When useful practice emerges, use [Practical Judgment](practical-judgment.md):
+When useful practice emerges, use [Phronesis — practical judgment](../reference/phronesis.md):
 retain its reason, cases and exceptions, then adopt it into the appropriate
 instruction, capability or implementation through that destination's owner.
 Ordinary research does not require a new skill, ADR or personal tracking.

package/docs/{tenant-readiness.md → guides/tenant-readiness.md}

@@ -19,6 +19,38 @@ write through a browser view.
    commerce, sessions, audit, and client-grade sharing as MNSTRY runtime
    authority.
 
+## Select the Readiness Pack
+
+Projects include the bundled MNSTRY readiness pack by default. To use only
+declared custom protocols, set this in the tracked `atelier.project.json`,
+preserving the project's other settings:
+
+```json
+{
+  "ext": {
+    "mnstry.atelier": {
+      "readiness": { "includeBundled": false }
+    }
+  }
+}
+```
+
+An absent setting or explicit `true` keeps the existing bundled protocols and
+twelve-dimension tenant journey. Local preferences cannot re-enable a bundle
+that the tracked project deselects.
+
+After reviewing a selection change, update the existing lock explicitly:
+
+```bash
+atelier lock write --project ./atelier.project.json
+atelier lock check --project ./atelier.project.json
+```
+
+The lock records the selected packs while preserving its template and migration
+history. A lock that still pins the deselected bundle fails `lock check` and
+`upgrade --dry-run`. To select the bundle again, set `includeBundled` to `true`
+and write the lock after review.
+
 ## Local Review Pass
 
 Run checks from the copied workspace:
@@ -36,6 +68,13 @@ Use `--check` modes where available when validating committed generated output.
 If a command is unavailable in an older workspace, report the exact command and
 stderr instead of substituting a new protocol.
 
+With the bundle deselected, the graph, project projection and generic readiness
+checks remain available. The projection and readiness output omit the MNSTRY
+tenant journey; they do not create a replacement journey or packet. Selected
+custom protocols use the existing [extension-pack workflow](extensions.md#readiness-extension-packs).
+`readiness journey`, `readiness packet` and `readiness export --dry-run` refuse
+with `readiness-pack-disabled`, including when custom packs are selected.
+
 ## Claim-First Output
 
 Readiness summaries should lead with claims, then evidence:

package/docs/{upgrade.md → guides/upgrade.md}

@@ -9,9 +9,76 @@ workspace between Atelier package releases. The flow is local-only: it does not
 provision repositories, contact a Git host, mutate the MNSTRY runtime, or write
 through a browser view.
 
+## Upgrading to 0.2.0-alpha.15
+
+This release adds the graph workspace (`@mnstry/atelier/graph-workspace` and
+`@mnstry/atelier/graph-workspace/browser`) and the graph view, access and
+source-contribution modules. Existing consumers do not need to change. No schema
+or stored record format changes, with one effect on Knowledge Health:
+
+- Knowledge Health regenerates its rule identity for the knowledge-graph file:
+  the `check` each assessment carries names a new `version` and `sourceTree`.
+  The rule it applies is unchanged. A workshop contribution started on
+  0.2.0-alpha.14, completed or not, cannot start Review on this release
+  (`finding changed; refresh before selecting a new draft`); start Review
+  before upgrading, or record a new contribution.
+
+## Upgrading to 0.2.0-alpha.14
+
+`atelier upgrade closure --npm-root ABSOLUTE_NPM_ROOT` plans a check of a staged
+candidate's own dependency closure before an upgrade. It reads the candidate's
+lockfile and manifests only and runs no npm command. Exit code 3 is a completed
+plan and exit code 2 a refusal; the command never exits 0, because a plan is not
+proof of an offline reinstall. It refuses `--__proto__` as an unsupported flag.
+See [Consumer dependency closure plan](#consumer-dependency-closure-plan).
+
+This release also introduces `@mnstry/atelier/ui`, a tenant-neutral control
+grammar for local Atelier tooling and compatible downstream interfaces. Existing
+consumers do not need to change. Consumers that adopt it map the
+`--system-control-*` custom properties to their own theme.
+
+No schema or stored record format changes in this release. The boundary checks
+now judge work they used to miss, so a commit or push that passed on
+0.2.0-alpha.13 can be refused, and a few other results change:
+
+- Reinstall the boundary hooks with `atelier boundary install-hooks`. The new
+  pre-push hook passes the remote Git names, so history held only by another
+  remote is judged on its way to a new one. The push check judges every commit
+  the remote's tracking refs do not hold, each against its parent, binaries
+  included. A push carrying more than 1000 such commits or more than the
+  evidence budget is refused with `content-scan-incomplete`; push it in
+  smaller parts.
+- The pre-commit check reads the index and work tree Git names, so
+  `git commit -a`, `git commit <paths>` and commits from a linked worktree are
+  judged. It blocks with `pre-commit-repo-unresolved` when no single declared
+  repository is being committed, as the push check does.
+- The content scan pins its diff format, so an external diff, a textconv
+  driver, changed prefixes or quoted paths no longer leave a change unscanned.
+  A staged or pushed deletion of a binary file no longer blocks.
+- The semantic-field review takes only an added review marker as approval; a
+  removed marker, or one in a file name, approves nothing. `atelier upgrade`
+  applies the same rule.
+- `extract-structure` refuses `parallel: true` with `NATIVE_WORKERS_UNATTESTED`.
+- Knowledge Health regenerates its rule identity for the two graph files: the
+  `check` each assessment carries names a new `version`, `sourceTree` and
+  `graphBlob`. The rule it applies is unchanged. A workshop contribution
+  started on 0.2.0-alpha.13, completed or not, cannot start Review on this
+  release (`finding changed; refresh before selecting a new draft`); start
+  Review before upgrading, or record a new contribution.
+- `runMaintenanceService` from `@mnstry/atelier/obsidian` refuses a project
+  loader that answers with a promise when no `locateProject` is given
+  (`service-loader-not-synchronous`); on 0.2.0-alpha.13 such a service
+  protected no repository. Pass a synchronous `locateProject`, which answers
+  a project naming its folder, to keep an asynchronous loader (see
+  [Obsidian](obsidian.md)).
+
+A package update supplies no interpretation approval, source-write permission,
+publication authority or runtime activation. Rehearse this exact installed
+version in a disposable workspace before client use.
+
 ## Upgrading to 0.2.0-alpha.13
 
-The public [Knowledge Health workshop](knowledge-health/devday/public-default.md)
+The public [Knowledge Health workshop](../knowledge-health/quickstart.md)
 uses an invented local workspace. Participants can retain their original words,
 a separate interpretation and a `note`, `perspective-only`, `disagreement` or
 `pause` response. Review is a separate optional session. A selected draft can
@@ -22,7 +89,7 @@ then reads it back and reassesses. The browser host grants no source-apply route
 
 `atelier knowledge semantic` exposes the existing semantic runner's eleven
 operations through JSON stdin. It retains the runner's refusal codes and saved
-failure details. The [semantic operation contract](semantic-operation.md)
+failure details. The [semantic operation contract](../reference/semantic-operation.md)
 remains authoritative; this release adds no schema or package export.
 
 Existing source and local history remain owned by their original repositories.
@@ -43,13 +110,13 @@ The next release adds the responsibility workflows, source-current ingestion,
 Trackables, governed instruction adoption and local template profiles. Template
 adoption uses the existing exact-plan transaction engine with explicit v2 policy
 and v3 plans; existing policies are never converted automatically. See
-[template profiles](template-profile.md) and [template adoption](template-upgrades.md).
+[template profiles](../reference/template-profile.md) and [template adoption](template-upgrades.md).
 Optional advisory decisions require no provider installation or activation.
 
 New Trackable journals retain resolved calendar occurrences and byte-bound state.
 Legacy v1 journals remain available as chain-verified exports when state replay
 cannot be established. Preserve historical records and use the documented
-[Trackables](trackables.md) host limits before adopting a new profile.
+[Trackables](../reference/trackables.md) host limits before adopting a new profile.
 Regenerate local graph/projection artifacts through the ordinary upgrade process
 and qualify each consuming host independently. A package update supplies no
 publication permission or runtime activation.
@@ -112,7 +179,7 @@ The link resolver that produces `links_to` edges changed in five classes
 the repository root, malformed percent-encoding, and workspace-only wikilink
 and cross-repository edges). Regenerate committed graph artifacts after
 upgrading and review the difference; the classes are listed in the changelog
-and in [obsidian-contract.md](obsidian-contract.md).
+and in [obsidian-contract.md](../reference/obsidian-contract.md).
 
 ## Upgrading to 0.2.0-alpha.7
 
@@ -211,7 +278,7 @@ compensating for that.
 This release breaks the export vocabulary. The runtime owner names are now
 the vendor-neutral domain terms `identity`, `catalog`, `commitments`,
 `events`, `projection`, `consent`, `messaging`, `providers`, and `audit`
-(defined in `docs/ontology.md`), and documents written against
+(defined in `docs/reference/ontology.md`), and documents written against
 `v0.1.0-alpha.2` do not validate here. Regenerate exports and projections rather than hand-editing
 them, and update any consumer that pins an owner name. `CHANGELOG.md` lists
 every breaking change in this release, including the contract-stability epoch
@@ -223,7 +290,7 @@ current corpus against the validators of the baseline recorded in
 a tag sets `baselineTag` to that tag in the release commit, so the following
 development cycle is checked against the released validators. Until the first
 post-epoch tag is cut the baseline is null and the gate is inert by design.
-See `docs/contract-stability.md`.
+See `docs/reference/contract-stability.md`.
 
 ## Before You Upgrade
 
@@ -250,7 +317,7 @@ For registry installs, pin the exact version and record the resolved version
 in the lockfile:
 
 ```bash
-npm install --save-dev @mnstry/atelier@0.2.0-alpha.13
+npm install --save-dev @mnstry/atelier@0.2.0-alpha.14
 npx mnstry-atelier lock write --project ./atelier.project.json
 ```
 
@@ -258,7 +325,7 @@ For Git installs, pin the release tag rather than a branch, so the lock file
 records exactly what was reviewed:
 
 ```bash
-npm install --save-dev "git+https://github.com/MNSTRY/atelier.git#v0.2.0-alpha.13"
+npm install --save-dev "git+https://github.com/MNSTRY/atelier.git#v0.2.0-alpha.14"
 npx mnstry-atelier lock write --project ./atelier.project.json
 ```
 
@@ -325,8 +392,8 @@ and dependency trees; two observed byte inventories must agree and match the com
 checkout does not authenticate an upstream publisher.
 
 Review snapshots and decisions are separate from historical v1 locks. See
-[pack lifecycle](extension-pack-lifecycle.md) and
-[inspection portability](review-portability.md) before replacing packs or moving
+[pack lifecycle](../reference/extension-pack-lifecycle.md) and
+[inspection portability](../reference/review-portability.md) before replacing packs or moving
 state. Updating a package or a digest never silently renews old approval.
 
 ## Exact local candidate transactions
@@ -337,3 +404,122 @@ For the bounded, manually confirmed single-repository workflow, see
 commands are separate from the legacy flag-based migration workflow above.
 They preserve history and honor existing commit hooks; they do not install a
 new package or activate a runtime.
+
+## Consumer dependency closure plan
+
+`atelier upgrade closure --npm-root ABSOLUTE_NPM_ROOT` plans a check of a staged
+candidate's own dependency closure. A consumer does not inherit a dependency
+publisher's npm `overrides`, so the candidate's own lockfile is what counts.
+
+The command reads these files and no others:
+
+- the candidate's `package.json` and `package-lock.json`;
+- the installed `package.json` of every lockfile copy of the selected package;
+- `package.json` in each directory above the npm root, up to the filesystem
+  root, to refuse a parent that declares workspaces. When the npm root is under
+  your home directory, that includes a `package.json` in the home directory;
+- Atelier's own `package.json`. The CLI reads it on every run for its version;
+  this plan also takes the default package name from it when `--package` is
+  not given.
+
+It does not run npm, use the network, read npm configuration or credentials, or
+write anything. The directory need not be an Atelier workspace, and `--npm-root`
+has no default.
+
+Every run prints exactly one JSON document with `"proof": "not-run"`, including
+a run whose arguments are refused. A completed plan holds:
+
+- the lockfile's SHA-256, version and entry count;
+- entries by source (`npm`, `git`, `local_path`, `link`, `bundled` and
+  `unclassified`, an installed entry with no `resolved`); the counts add up to
+  the entry count;
+- the registry hosts the lockfile names, and separately the URL schemes (`http`,
+  `https`) it uses;
+- the number of registry tarballs an offline proof would need;
+- lockfile entries whose `os`, `cpu` or `libc` excludes this host;
+- the selected package's lockfile copies, and under `manifests` the path, name,
+  version and SHA-256 of each installed manifest that was read;
+- the selected package's exact `overrides` that were checked against every
+  installed copy, the ones with no copy, and the ones left unchecked: a
+  version-selector key, a nested override, a value that is not an exact
+  version, or a package that a link provides (`link-only`, or `linked-copy`
+  when a registry copy is installed beside the link);
+- every refusal, with its code, one `reason`, a message and a next step.
+
+A refused plan holds its refusals and whatever else was established. A refusal
+of the arguments, the npm root or the shape of the lockfile stops the plan
+there, so it holds nothing about the lockfile's entries; any other refusal is
+listed beside the rest of the classification.
+
+Exit code 3 means a completed plan. Exit code 2 means a refusal: the JSON
+document, then `[code] message` with a `Next:` step on standard error. The
+command never exits 0: a plan is not a pass, and this command does not prove an
+offline reinstall.
+
+Overrides are taken from the installed manifest only when it is the package the
+lockfile records: each copy's manifest must declare the selected name and the
+version of its own lockfile entry, and all copies must be at one version with
+the same overrides. Otherwise the plan is refused and no override is reported
+as checked.
+
+Refusals reuse existing codes:
+
+- `usage`: the input is not supported. Reasons: `npm-root-required`,
+  `npm-root-not-absolute`, `npm-root-not-directory`, `npm-root-linked` (the
+  path is a link or passes through one; the refusal prints the directory's
+  `realPath` to pass instead), `argument-unsupported` (an unknown flag, an
+  extra argument, a flag with no value, an empty `--package` or
+  `--registry-host`, or a flag given more than once; an empty value after
+  `--npm-root=` is `npm-root-required`), `manifest-missing`, `lockfile-missing`,
+  `lockfile-invalid` (not a JSON object, or a `packages` entry that is not an
+  object), `lockfile-version` (version 1, or no `packages` map), `workspaces`,
+  `prefix-mismatch` (a parent directory declares workspaces) and
+  `linked-node-modules`.
+- `consumer-closure-incomplete`: an offline reinstall could not be proven for a
+  lockfile entry. Reasons: `missing-integrity`, `git-source`, `other-host`,
+  `outside-project`, `link-target-missing` (a link that names no folder),
+  `zero-copies`, `selected-package-unreadable`, `selected-package-mismatch`
+  (an installed manifest that is not the package its lockfile entry records)
+  and `selected-copies-differ`.
+- `override-not-inherited`: reason `copy-off-pin`. A copy is installed at a
+  version other than the selected package's exact pin. More than one copy, all
+  at the pin, is reported and not refused.
+
+Options:
+
+- `--package NAME` selects the package whose overrides are checked. It defaults
+  to `@mnstry/atelier`.
+- `--registry-host HOST[,HOST]` names the approved registry hosts. A tarball on
+  any other host, or at a URL with no readable host, is then refused. Without
+  it, hosts are reported and `approvedRegistryVerified` is `false`, because the
+  plan does not read npm configuration.
+
+Give each option once, with a value, after the word `closure`. An option with
+an empty value is refused; leave the option out to use its default.
+
+Limits:
+
+- The plan cannot run `npm prefix`, so `prefixVerified` is always `false`.
+  Instead it requires `--npm-root` to be the directory's real path and refuses
+  any parent directory of it that declares workspaces, whether or not that
+  parent's workspaces include the candidate. A path that is a link, or passes
+  through one, is refused, with its `realPath` in the JSON result. On macOS,
+  `/tmp` is a link into `/private` and `$TMPDIR` passes through `/var`, another
+  such link, so a candidate staged there needs its real path (for example
+  `pwd -P` from inside it).
+- Containment of links and local files is checked by path, without following
+  links. The folder a link points to is not opened: an override for a package
+  that a link provides is listed as unchecked, never as checked.
+- Approving a host does not verify the transport. A host is matched by its
+  exact name and port, whatever the scheme; `registrySchemes` counts `http`
+  and `https` separately.
+- The manifest binding compares the name and version the installed manifest
+  declares. It does not verify the installed files against the lockfile's
+  `integrity`.
+- Platform evidence uses this process's `os` and `cpu`; `libc` is unknown
+  unless a caller of `planConsumerClosure` supplies it.
+- A flag with no value placed before the word `closure` (for example
+  `atelier upgrade --package closure`) takes `closure` as its value, so the
+  ordinary upgrade command runs instead of this one.
+- `lockTreeDifferences`, the comparison of two `npm ls` trees, is in the source
+  but is not exported from the package and no command uses it.

package/docs/knowledge-health/assessment/capabilities.md

@@ -1,4 +1,4 @@
-# Capability map and retained tooling needs
+# Capability map and qualification limits
 
 `KNOWLEDGE_HEALTH_CAPABILITIES` from the public assessment entry contains exact
 source commit/tree/blob/file references, baseline availability, verification
@@ -20,20 +20,11 @@ release certification or semantic/human acceptance.
 | Authoring/hosts | `./coauthor`: `createSession`, `transition`, `replaySession`; existing store/presentation/runtime/Obsidian; current knowledge dashboard/session and sidecar | Static only in this supplier. Mounted editor/store owns apply/save; native and participant proof separate. |
 | Normal initialization | Current `atelier init --template knowledge-workspace --target ./workspace` and its shipped template | Source dispatch inspected; public alpha.12 lacks this dispatch/template. Test both from the exact official new archive and published version. The explicit fixture helper is not that test. |
 
-Keep S2–S5 tooling work visible:
-
-- **S2:** qualifiers, contradiction/identity, optional bounded agent cost/value,
-  private perspectives and scoped learning. Reuse native semantic/contribution,
-  evaluation and learning primitives; human source-supported trials remain open.
-- **S3:** declared/adopted/consumed/executed traces, drift, partial refresh,
-  withdrawal/recovery. Join actual observation/runtime/harness evidence. This
-  context defaults all four use stages to unobserved.
-- **S4:** other hosts/media/domains, keyboard/IME/zoom/text scaling, accessible
-  graph alternatives and purposeful scale. Existing source-format,
-  presentation/runtime and budgets are starting points; installed measurements
-  remain host-specific. This proof is Node22/macOS only.
-- **S5:** ownership, documentation, rollback/recovery, maintenance and complete
-  programme closure. A public kit is an input to those journeys, not their proof.
+Semantic support, contradiction/identity judgments and human usefulness require
+source-supported trials. Declared, adopted, consumed and executed use remain
+distinct; this context defaults all four stages to unobserved. Installed-host
+keyboard, input-method, zoom, accessible alternatives, recovery and scale require
+host-specific measurements. The supplier proof here is limited to Node22/macOS.
 
 Preserve source evidence, structure, interpretations, proposals, owner decisions
 and execution as distinct records. Reuse existing canonicals and one editor/store

package/docs/knowledge-health/facilitator.md

@@ -1,8 +1,15 @@
 # Facilitator run sheet
 
-Use the exact supported release and one new disposable workshop copy per participant. The kit's target session is Thursday 8 October 2026; rehearse the installed version on Wednesday 7 October. Those dates do not prove publication or participant acceptance.
+Use the exact supported release and one new disposable workshop copy per
+participant. Record the package version, integrity and host used for rehearsal.
 
-Before the session, obtain the release owner's verified version and guided entry. Install that exact version using the package's tested quickstart, check its documented Node/Git/browser prerequisites, and rehearse the whole [exercise](exercise.md) from a clean copy without private paths, developer imports or environment overrides. Do not start until the public launch, copy/open, contribution, interpretation, Review, source-owner correction, readback/reopen and reassessment steps are available. Keep any genuine missing step visible.
+Before the session, install the selected version using the
+[public workshop quickstart](quickstart.md), check its documented
+Node/Git/browser prerequisites, and rehearse the flow from a clean copy. Verify
+original words, separate interpretation and the explicit four-choice response
+through ordinary saved drafts. Review saves a separately selected declaration;
+the retained handoff is a copy-only proposal. Canonical source correction stays
+with the source owner. Keep any missing or unqualified step visible.
 
 | Time | Invitation | Observe without answering for the participant |
 | --- | --- | --- |
@@ -15,6 +22,10 @@ Before the session, obtain the release owner's verified version and guided entry
 
 Offer the participant the source-owner role only for their own disposable copy. Explain what the ordinary source write will change before granting that role. Keep source ownership and participant judgment distinct even when one person performs both.
 
-For a recovery exercise, use the host's documented disposable failure rehearsal. If it has no supported rehearsal, discuss the visible unconfirmed state without disconnecting an unknown service. A pending choice is checked under its original identity; it is not submitted as a new note. Do not run a provider to fill a gap, alter a participant's words, or reset the example's history.
+For a recovery exercise, use the host's documented disposable failure rehearsal. If it has no supported rehearsal, discuss the visible unconfirmed state without disconnecting an unknown service. A pending request is checked under its original identity; it is not submitted as a new note. Do not run a provider to fill a gap, alter a participant's words, or reset the example's history.
 
-Observe keyboard access and the [checklist](support.md). If a step fails, preserve the words and exact pending intent, record the visible state and reproduction steps, then use the normal support route. Finishing a scripted exercise is not evidence that the participant found it useful.
+Observe actual keyboard access, focus return, input-method behavior and recovery
+in the receiving browser. If a step fails, preserve the words and exact pending
+intent, record the visible state and reproduction steps, then use the normal
+support route. Saved drafts do not establish native typed finding disposition,
+authenticated approval or participant usefulness.

package/docs/knowledge-health/{devday/participant-response.md → participant-response.md}

@@ -8,7 +8,7 @@ This public workshop uses the existing local Knowledge editor and ordinary coaut
 4. Choose Note, Perspective, Disagreement or Pause, then save and continue. Perspective retains the existing `perspective-only` value. Pause is a response choice; the session Pause control remains a separate navigation action.
 5. Read the original contribution and choice event IDs, descriptor/event-history readback and immutable saved-value readback. A save request ID identifies the save receipt and differs from the original answer ID. An unsaved choice remains unconfirmed.
 6. Review displays the current `[]` declaration and proposed `["devday:workshop"]` declaration. Return removes the preview and makes no request. Selecting the draft starts a separate linked Review session. Record selected draft, save it, continue, then reload or reopen the same session from history before preparing the handoff.
-7. The copy-only source-owner handoff retains original words, optional interpretation, four-choice meaning, original contribution/choice IDs, contributor session, selected save receipt, source/anchor/read set and all six finding fingerprints. Foundation owns durable proposal retention and original-identity lookup in its existing sidecar/proposals implementation. That owner work remains prospective until applied and qualified.
+7. The copy-only source-owner handoff retains original words, optional interpretation, four-choice meaning, original contribution/choice IDs, contributor session, selected save receipt, source/anchor/read set and all six finding fingerprints. The existing sidecar/proposals implementation owns durable proposal retention and original-identity lookup. Read the proposed record back before treating retention as confirmed; it applies no source change.
 8. The source owner checks the bound source digest and exact before/after UTF-8 declaration, edits the exact declaration through the ordinary repository route, reads it back, refreshes expected evidence and reruns the same assessment/question. Keep the earlier finding, contribution and selected draft as history. Automated Obsidian/frontmatter apply remains separate and keeps its refusals.
 
 ## Recovery and storage meaning
@@ -19,4 +19,6 @@ The existing draft engine requires nonempty text. This consumer stores optional
 
 `readSavedFields` reads the existing verified event chain and existing immutable values under the existing operation lock. It refuses redirected, missing or changed values and never reconstructs them. Reopen requires both owning readbacks to agree. Earlier descriptors without the participant profile marker retain their legacy revision history; new sessions use four responses and a separate Review.
 
-Source-only authored cases accompany this change. No tests, browser journey, installed package, retention readback, source edit or release was executed by this supplier attempt.
+These draft and recovery APIs do not establish installed-browser keyboard,
+input-method or undo behavior. Qualify the actual receiving host separately;
+draft retention never establishes source application, release or human acceptance.