@unbrained/pm-cli 2026.11.3 → 2026.11.5

package/docs/CONFIGURATION.md

@@ -37,7 +37,7 @@ it to the right typed flag based on the key (so `--policy`/`--format`/`--criteri
 remain optional for single values):
 
 ```bash
-pm config set telemetry-tracking off          # off|on|true|false map to disabled|enabled
+pm config set telemetry-tracking off          # off|on|true|false; global profile
 pm config set item-format toon                # same as --format toon
 pm config set governance-preset strict        # same as --policy strict
 pm config set definition-of-done "Tests pass" # same as --criterion "Tests pass"
@@ -80,34 +80,35 @@ If the existing `settings.json` is valid JSON but fails schema validation (for e
 
 ## Common Settings
 
-| Setting                                    | Purpose                                                                                                                                                                                               |
-| ------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `id_prefix`                                | generated item ID prefix, default `pm-`                                                                                                                                                               |
-| `ids.token_length`                         | random base36 token length for newly minted item ids (4-12, default `4`); raise it to shrink cross-branch id collision odds in concurrent multi-agent workflows (see [Merge Safety](MERGE_SAFETY.md)) |
-| `author_default`                           | configured mutation author before automatic harness detection                                                                                                                                         |
-| `mutation_guard.require_attributed_author` | reject mutations whose effective author remains `unknown` (default `false`)                                                                                                                           |
-| `mutation_guard.secret_guard`              | credential-shaped content policy: `off`, `advise`, or `block` (default `advise`)                                                                                                                      |
-| `mutation_guard.stale_in_progress_hours`   | age threshold for unclaimed in-progress work surfaced by `pm health` (integer >= 1, default `72`)                                                                                                     |
-| `item_format`                              | item storage format (`toon` writes; legacy markdown is read/migrate only)                                                                                                                             |
-| `output.default_format`                    | default renderer, usually `toon`                                                                                                                                                                      |
-| `locks.ttl_seconds`                        | stale lock threshold                                                                                                                                                                                  |
-| `locks.wait_ms`                            | wait budget before a contended lock returns `lock_conflict`; item-store mutations, restore and the hierarchy lock restart it on each owner handoff (120 s cap), other locks use it as a fixed total (default `3000`; `0` fails fast) |
-| `history.missing_stream`                   | `auto_create` or `strict_error`                                                                                                                                                                       |
-| `history.compact_policy.enabled`           | enable the compaction advisory: `pm health` warns on over-threshold streams (default `false`); when disabled, `max_entries`/`trigger` are inert                                                       |
-| `history.compact_policy.max_entries`       | when the policy is enabled, the entry count above which a stream is flagged by `pm health` and the default `pm history-compact --all-over` threshold (default `500`)                                  |
-| `history.compact_policy.trigger`           | policy intent when enabled: `health_warn` (advisory only) or `auto` (scheduled sweeps expected)                                                                                                       |
-| `testing.record_results_to_items`          | persist bounded linked-test summaries                                                                                                                                                                 |
-| `testing.allow_untrusted_linked_tests`     | permit the explicit `pm test --allow-untrusted-linked-tests` one-run override (default `false`; does not trust or execute commands by itself)                                                         |
-| `validation.sprint_release_format`         | `warn` or `strict_error`                                                                                                                                                                              |
-| `validation.parent_reference`              | `warn` or `strict_error` (`strict_error` is the built-in default; `pm create --allow-missing-parent` is the explicit escape hatch)                                                                    |
-| `item_types.definitions[]`                 | custom item types and type options                                                                                                                                                                    |
-| `governance.create_default_type`           | default `--type` used by `pm create "title"` when `--type` is omitted (defaults to `Task`); must resolve to a known item type                                                                         |
-| `governance.workflow_enforcement`          | per-type transition enforcement mode for `pm update --status` (`off` default, `warn`, or `strict`)                                                                                                    |
-| `governance.duplicate_detection_mode`      | create/copy similarity policy: `off`, `advisory`, or `strict`; the minimal preset uses `off`, while the default and strict presets use `strict`                                                       |
-| `governance.duplicate_detection_threshold` | inclusive likely-duplicate score from `0` through `1` (default `0.8`)                                                                                                                                 |
-| `governance.duplicate_detection_limit`     | maximum matches attached to a create/copy advisory from `0` through `20` (default `3`)                                                                                                                |
-| `schema.type_workflows[]`                  | per-type allowed status transitions (see Per-Type Workflows below)                                                                                                                                    |
-| `search.*`                                 | search mode, scoring, providers, embedding timeout, and vector settings                                                                                                                               |
+| Setting | Purpose |
+|---|---|
+| `id_prefix` | generated item ID prefix, default `pm-` |
+| `ids.token_length` | random base36 token length for newly minted item ids (4-12, default `4`); raise it to shrink cross-branch id collision odds in concurrent multi-agent workflows (see [Merge Safety](MERGE_SAFETY.md)) |
+| `author_default` | configured mutation author before automatic harness detection |
+| `mutation_guard.require_attributed_author` | reject mutations whose effective author remains `unknown` (default `false`) |
+| `mutation_guard.secret_guard` | credential-shaped content policy: `off`, `advise`, or `block` (default `advise`) |
+| `mutation_guard.stale_in_progress_hours` | age threshold for unclaimed in-progress work surfaced by `pm health` (integer >= 1, default `72`) |
+| `item_format` | item storage format (`toon` writes; legacy markdown is read/migrate only) |
+| `output.default_format` | default renderer, usually `toon` |
+| `locks.ttl_seconds` | stale lock threshold |
+| `locks.wait_ms` | wait budget before a contended lock returns `lock_conflict`; item-store mutations, restore and the hierarchy lock restart it on each owner handoff (120 s cap), other locks use it as a fixed total (default `3000`; `0` fails fast) |
+| `history.missing_stream` | `auto_create` or `strict_error` |
+| `history.compact_policy.enabled` | enable the compaction advisory: `pm health` warns on over-threshold streams (default `false`); when disabled, `max_entries`/`trigger` are inert |
+| `history.compact_policy.max_entries` | when the policy is enabled, the entry count above which a stream is flagged by `pm health` and the default `pm history-compact --all-over` threshold (default `500`) |
+| `history.compact_policy.trigger` | policy intent when enabled: `health_warn` (advisory only) or `auto` (scheduled sweeps expected) |
+| `testing.record_results_to_items` | persist bounded linked-test summaries |
+| `testing.allow_untrusted_linked_tests` | permit the explicit `pm test --allow-untrusted-linked-tests` one-run override (default `false`; does not trust or execute commands by itself) |
+| `validation.sprint_release_format` | `warn` or `strict_error` |
+| `validation.parent_reference` | `warn` or `strict_error` (`strict_error` is the built-in default; `pm create --allow-missing-parent` is the explicit escape hatch) |
+| `item_types.definitions[]` | custom item types and type options |
+| `governance.create_default_type` | default `--type` used by `pm create "title"` when `--type` is omitted (defaults to `Task`); must resolve to a known item type |
+| `governance.workflow_enforcement` | per-type transition enforcement mode for `pm update --status` (`off` default, `warn`, or `strict`) |
+| `governance.start_blocker_enforcement` | starting an item (`update --status in_progress`, `claim --start`, `claim --next --start`, `start-task`) while a declared `blocked_by` target is open: `strict` (default; refuse unless `--force`), `warn`, or `off`; `claim --next --start` skips a refused candidate and claims the next eligible one |
+| `governance.duplicate_detection_mode` | create/copy similarity policy: `off`, `advisory`, or `strict`; the minimal preset uses `off`, while the default and strict presets use `strict` |
+| `governance.duplicate_detection_threshold` | inclusive likely-duplicate score from `0` through `1` (default `0.8`) |
+| `governance.duplicate_detection_limit` | maximum matches attached to a create/copy advisory from `0` through `20` (default `3`) |
+| `schema.type_workflows[]` | per-type allowed status transitions (see Per-Type Workflows below) |
+| `search.*` | search mode, scoring, providers, embedding timeout, and vector settings |
 
 Lock recovery is tracked by
 [pm-02z97f](https://github.com/unbraind/pm-cli/blob/main/.agents/pm/issues/pm-02z97f.toon)
@@ -218,15 +219,15 @@ underscore aliases remain accepted for compatibility.
 
 ## Environment Variables
 
-| Variable                          | Use                                                                                                                      |
-| --------------------------------- | ------------------------------------------------------------------------------------------------------------------------ |
-| `PM_AUTHOR`                       | optional explicit session-wide mutation author override                                                                  |
-| `PM_PATH`                         | override project tracker root for tests or sandboxes                                                                     |
-| `PM_GLOBAL_PATH`                  | override global profile root for tests or sandboxes                                                                      |
-| `PM_LOCK_WAIT_MS`                 | per-process override for the `locks.wait_ms` budget (a no-progress window only where that lock uses the progress policy); non-negative integer milliseconds, with `0` restoring fail-fast lock conflicts |
-| `PM_OLLAMA_MODEL`                 | choose default Ollama embedding model                                                                                    |
-| `PM_DISABLE_OLLAMA_AUTO_DEFAULTS` | disable implicit Ollama search defaults                                                                                  |
-| `PM_CONTEXT_USAGE_DISABLED`       | set to `1` to disable the derived context/next usage-feedback ledger with zero filesystem reads or writes                |
+| Variable | Use |
+|---|---|
+| `PM_AUTHOR` | optional explicit session-wide mutation author override |
+| `PM_PATH` | override project tracker root for tests or sandboxes |
+| `PM_GLOBAL_PATH` | override global profile root for tests or sandboxes |
+| `PM_LOCK_WAIT_MS` | per-process override for the `locks.wait_ms` budget (a no-progress window only where that lock uses the progress policy); non-negative integer milliseconds, with `0` restoring fail-fast lock conflicts |
+| `PM_OLLAMA_MODEL` | choose default Ollama embedding model |
+| `PM_DISABLE_OLLAMA_AUTO_DEFAULTS` | disable implicit Ollama search defaults |
+| `PM_CONTEXT_USAGE_DISABLED` | set to `1` to disable the derived context/next usage-feedback ledger with zero filesystem reads or writes |
 
 For command-level tracker targeting, prefer `--pm-path <tracker-root>`. The old
 `--path` flag is still accepted, but it means the pm tracker storage directory
@@ -263,23 +264,31 @@ Tests should set both `PM_PATH` and `PM_GLOBAL_PATH` to temporary directories. T
 
 ### Telemetry environment variables
 
-Telemetry is enabled by default. Use `pm config set telemetry-tracking off` to opt out persistently (see [Common Settings](#common-settings)). When enabled, these environment variables tune runtime behaviour. All boolean knobs accept `1`, `true`, `yes`, or `on` (case-insensitive); any other value leaves the knob off.
+Telemetry is enabled by default. Use `pm config set telemetry-tracking off` to opt out persistently (see [Common Settings](#common-settings)). Consent and the event endpoint live only in the global profile:
 
-| Variable                             | Values                                        | Use                                                                                                                                             |
-| ------------------------------------ | --------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------- |
-| `PM_TELEMETRY_DISABLED`              | boolean                                       | Hard-disable all telemetry for this process, ignoring settings.                                                                                 |
+- A scope-less `telemetry-tracking` call targets the global profile.
+- Project-scope `get` and `set` refuse. Project `list` and `export` omit the key.
+- `pm init` asks only while no choice is recorded in the global profile. It keeps a choice another process records while its prompt is open. It reports the global value and writes no project `telemetry` block.
+- An older project `telemetry` block is ignored.
+
+When enabled, these environment variables tune runtime behaviour. All boolean knobs accept `1`, `true`, `yes`, or `on` (case-insensitive); any other value leaves the knob off.
+
+| Variable | Values | Use |
+|---|---|---|
+| `PM_TELEMETRY_DISABLED` | boolean | Hard-disable all telemetry for this process, ignoring settings. |
 | `DO_NOT_TRACK` | boolean | Hard-disable event capture, identity creation, flush workers, endpoint probes, and Sentry, regardless of persisted preferences. |
 | `PM_TELEMETRY_SEND_TEST_EVENTS` | boolean | Explicitly allow inferred test events. Hard opt-outs still take precedence. |
 | `PM_TELEMETRY_READ_SAMPLE_RATE` | number greater than `0` and at most `1` | Override automatic successful-read sampling; `1`, empty, or invalid values retain every invocation. Omit for automatic frequency bounding. |
-| `PM_NO_TELEMETRY`                    | boolean                                       | Alias for `PM_TELEMETRY_DISABLED` (honoured by the same checks).                                                                                |
-| `PM_TELEMETRY_OTEL_DISABLED`         | boolean                                       | Disable only OTLP trace-span export; the event queue still flushes.                                                                             |
-| `PM_TELEMETRY_INLINE_FLUSH`          | boolean                                       | Flush the queue and OTLP spans inline instead of dispatching the detached worker. Mainly for tests; normal use relies on the background worker. |
-| `PM_TELEMETRY_SOURCE_CONTEXT`        | `user` \| `automation` \| `test` \| `dogfood` | Override the inferred source context recorded on each event. Unrecognized nonempty values use inferred context with `source_context_source=env_override_rejected`; the raw value is never emitted.                            |
-| `PM_TELEMETRY_HTTP_TIMEOUT_MS`       | integer milliseconds                          | Bound each background event or OTLP request (default `20000`, clamped to `1000`–`25000` to stay below the worker lock TTL).                     |
-| `PM_TELEMETRY_INGEST_KEY`            | string                                        | Sent as the `x-pm-telemetry-key` header on queue flushes; never logged.                                                                         |
-| `OTEL_EXPORTER_OTLP_TRACES_ENDPOINT` | URL                                           | OTLP/HTTP traces endpoint for command spans. Takes precedence over the base endpoint.                                                           |
-| `OTEL_EXPORTER_OTLP_ENDPOINT`        | URL                                           | Base OTLP endpoint; the traces endpoint is derived by appending `/v1/traces`.                                                                   |
-| `OTEL_SERVICE_NAME`                  | string                                        | `service.name` attribute on exported spans (defaults to `pm-cli`).                                                                              |
+| `PM_NO_TELEMETRY` | boolean | Alias for `PM_TELEMETRY_DISABLED` (honoured by the same checks). |
+| `PM_TELEMETRY_OTEL_DISABLED` | boolean | Disable only OTLP trace-span export; the event queue still flushes. |
+| `PM_TELEMETRY_INLINE_FLUSH` | boolean | Flush the queue and OTLP spans inline instead of dispatching the detached worker. Mainly for tests; normal use relies on the background worker. |
+| `PM_TELEMETRY_SOURCE_CONTEXT` | `user` \| `automation` \| `test` \| `dogfood` | Override the inferred source context recorded on each event. Unrecognized nonempty values use inferred context with `source_context_source=env_override_rejected`; the raw value is never emitted. |
+| `PM_TELEMETRY_HTTP_TIMEOUT_MS` | integer milliseconds | Bound each background event or OTLP request (default `20000`, clamped to `1000`–`25000` to stay below the worker lock TTL). |
+| `PM_TELEMETRY_INGEST_KEY` | string | Sent as the `x-pm-telemetry-key` header on queue flushes; never logged. |
+| `PM_TELEMETRY_ENDPOINT` | http(s) URL | Deliver events to this collector instead of the configured endpoint. Events captured under it go to a queue and state file of their own that only a process with the same value reads or reports; a later flush removes them after a day idle. `pm telemetry clear` removes them too, but it also revokes consent and deletes every telemetry queue and state file of the profile. An empty value uses the configured endpoint; any other value that is not an http(s) URL disables delivery. URL credentials are sent as Basic auth, by `pm health --check-telemetry` too. |
+| `OTEL_EXPORTER_OTLP_TRACES_ENDPOINT` | URL | OTLP/HTTP traces endpoint for command spans. Takes precedence over the base endpoint. |
+| `OTEL_EXPORTER_OTLP_ENDPOINT` | URL | Base OTLP endpoint; the traces endpoint is derived by appending `/v1/traces`. |
+| `OTEL_SERVICE_NAME` | string | `service.name` attribute on exported spans (defaults to `pm-cli`). |
 
 Unrecognized source-context overrides produce one bounded warning per process on
 stderr, naming the accepted values without echoing the rejected input. JSON
@@ -325,9 +334,12 @@ Interaction rules:
 
 Test environments inferred from `VITEST`, `VITEST_WORKER_ID`, `NODE_TEST_CONTEXT`
 (native `node --test` children), or `NODE_ENV=test` suppress telemetry and Sentry
-before identity creation. A valid explicit `PM_TELEMETRY_SOURCE_CONTEXT` or
-`PM_TELEMETRY_SEND_TEST_EVENTS=1` permits intentional test delivery. Point such
-tests at a local collector. Inferred tests use inline telemetry flushing even
+before identity creation. A valid explicit `PM_TELEMETRY_SOURCE_CONTEXT`,
+including `test`, or `PM_TELEMETRY_SEND_TEST_EVENTS=1` permits intentional test
+delivery, so a test that only wants the label must also set
+`PM_TELEMETRY_DISABLED=1`. Point such tests at a local collector: set
+`PM_TELEMETRY_ENDPOINT` for events, `SENTRY_DSN` for errors, and
+`OTEL_EXPORTER_OTLP_*` for spans. Inferred tests use inline telemetry flushing even
 after an opt in, so CLI delivery settles before process exit and disposable-root
 cleanup. SDK telemetry completion also awaits inline delivery before returning.
 Neither setting overrides a hard opt-out. `pm telemetry status` exposes effective `enabled`, persisted
@@ -360,12 +372,12 @@ Tracing and privacy delivery: [pm-58yzil](../.agents/pm/features/pm-58yzil.toon)
 
 Crash and error diagnostics are reported to Sentry only when telemetry is enabled and the process is not opted out. These environment variables tune the Sentry client.
 
-| Variable                    | Values         | Use                                                                                                                                                                                                                         |
-| --------------------------- | -------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `PM_SENTRY_DISABLED`        | boolean        | Disable Sentry error reporting for this process (the Sentry SDK is not even imported). `PM_TELEMETRY_DISABLED` / `PM_NO_TELEMETRY` also disable it.                                                                         |
-| `SENTRY_DSN`                | URL            | Override the destination DSN. Defaults to the bundled pm-cli project DSN.                                                                                                                                                   |
-| `SENTRY_ENVIRONMENT`        | string         | Override the reported environment tag. Defaults to `test` under Vitest, `ci` when `CI` is set, otherwise `production`.                                                                                                      |
-| `PM_SENTRY_TRACE_COMMANDS`  | boolean        | Explicitly initialize Sentry for successful commands. Defaults to off, preserving lazy startup. All consent opt-outs and test isolation still apply; a zero trace sample rate avoids initialization. |
+| Variable | Values | Use |
+|---|---|---|
+| `PM_SENTRY_DISABLED` | boolean | Disable Sentry error reporting for this process (the Sentry SDK is not even imported). `PM_TELEMETRY_DISABLED` / `PM_NO_TELEMETRY` also disable it. |
+| `SENTRY_DSN` | URL | Override the destination DSN. Defaults to the bundled pm-cli project DSN. |
+| `SENTRY_ENVIRONMENT` | string | Override the reported environment tag. Defaults to `test` under Vitest, `ci` when `CI` is set, otherwise `production`. |
+| `PM_SENTRY_TRACE_COMMANDS` | boolean | Explicitly initialize Sentry for successful commands. Defaults to off, preserving lazy startup. All consent opt-outs and test isolation still apply; a zero trace sample rate avoids initialization. |
 | `SENTRY_TRACES_SAMPLE_RATE` | number `0`–`1` | Fraction of command spans sampled for performance tracing. Defaults to `0.2` (20%). Set to `1` for full-trace performance debugging or `0` to disable tracing. Non-numeric or out-of-range values fall back to the default. |
 
 > Sentry is hard-disabled under Vitest (`VITEST` / `VITEST_WORKER_ID`), so these knobs are no-ops inside the test suite.
@@ -628,21 +640,21 @@ When query expansion or rerank providers fail, `pm search` degrades gracefully a
 
 `search.default_mode` decides the mode a bare `pm search` runs in (`--mode` always wins):
 
-| Value                | Behavior                                                                                                                                                          |
-| -------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `auto`               | default; `hybrid` when `search.provider` names the active embedding provider and a vector store or extension adapter resolves (or an extension search provider is active), `keyword` otherwise |
-| `keyword`            | pin exact-token ranking for every bare search                                                                                                                     |
-| `semantic`, `hybrid` | pin the semantic path; an unreachable provider still degrades to keyword hits with a `search_semantic_fallback` warning                                            |
+| Value | Behavior |
+|---|---|
+| `auto` | default; `hybrid` when `search.provider` names the active embedding provider and a vector store or extension adapter resolves (or an extension search provider is active), `keyword` otherwise |
+| `keyword` | pin exact-token ranking for every bare search |
+| `semantic`, `hybrid` | pin the semantic path; an unreachable provider still degrades to keyword hits with a `search_semantic_fallback` warning |
 
 Every search result reports `mode_source` (`explicit`, `settings`, or `auto`) beside the effective `mode`.
 
 Mutation commands invalidate keyword search caches immediately. Semantic vector refresh is controlled by `search.mutation_refresh_policy`:
 
-| Policy                | Behavior                                                                                                            |
-| --------------------- | ------------------------------------------------------------------------------------------------------------------- |
-| `semantic_configured` | default; refresh vectors during mutations only when semantic provider/store settings are explicitly configured      |
-| `cache_only`          | fastest writes; invalidate keyword caches and leave vector refresh to `pm reindex` or `pm health --refresh-vectors` |
-| `semantic_auto`       | also apply implicit local Ollama/LanceDB defaults during mutations                                                  |
+| Policy | Behavior |
+|---|---|
+| `semantic_configured` | default; refresh vectors during mutations only when semantic provider/store settings are explicitly configured |
+| `cache_only` | fastest writes; invalidate keyword caches and leave vector refresh to `pm reindex` or `pm health --refresh-vectors` |
+| `semantic_auto` | also apply implicit local Ollama/LanceDB defaults during mutations |
 
 Useful commands:
 

package/docs/CONTEXT_ALGORITHM_PORTFOLIO.md

@@ -28,7 +28,7 @@ Where two descriptions express one experiment, both slugs resolve to its owner.
 Existing acceptance owners retain their original delivery boundary.
 
 | Stable slug | Historical ordinal | Source note (UTC) | Canonical owner | Disposition |
-| --- | --- | --- | --- | --- |
+|---|---|---|---|---|
 | `act-r-activation` | 1 | 2026-07-07T15:12:12.161Z | [pm-fr9ok0](../.agents/pm/tasks/pm-fr9ok0.toon) | Proposed experiment |
 | `typed-spreading-activation` | 2 | 2026-07-07T15:12:12.161Z | [pm-fdb8e8](../.agents/pm/tasks/pm-fdb8e8.toon) | Proposed experiment |
 | `learned-linear-signal-weights` | 3 | 2026-07-07T15:12:12.161Z | [pm-ex5p2u](../.agents/pm/tasks/pm-ex5p2u.toon) | Proposed experiment |
@@ -112,7 +112,7 @@ The 18 candidate compositions from pm-vvib retain the architecture decision gate
 Individual experiment drafts record the ideas without accepting that decision.
 
 | Candidate | Composition | Canonical owner |
-| --- | --- | --- |
+|---|---|---|
 | 1 | Prospective memory | [pm-0uvib0](../.agents/pm/tasks/pm-0uvib0.toon) |
 | 2 | Metacognitive revalidation | [pm-ur2t9o](../.agents/pm/tasks/pm-ur2t9o.toon) |
 | 3 | Interference and belief revision | [pm-xfta80](../.agents/pm/tasks/pm-xfta80.toon) |

package/docs/CONTEXT_INTEGRITY_CONTRACTS.md

@@ -53,11 +53,11 @@ History writers using item-hash epoch 2 always emit `item_hash_version: 2`. An e
 
 Repair keeps implicit legacy streams implicit and byte-stable when no drift exists. Unsupported explicit epochs still fail with a typed `unsupported_item_hash_version` diagnostic instead of being rewritten.
 
-| Writer/runtime range                     | Item-hash output | Read contract                                                                                                                  |
-| ---------------------------------------- | ---------------- | ------------------------------------------------------------------------------------------------------------------------------ |
-| Legacy writers before an explicit marker | implicit epoch 1 | Modern readers retain legacy canonicalization candidates.                                                                      |
-| Observed 2026.8.24 through 2026.8.28     | explicit epoch 2 | Modern readers accept both field-frozen and expanded epoch-2 forms without mixing forms inside one entry.                      |
-| 2026.8.31 and newer                      | explicit epoch 3 | Exact pins and bounded ranges that cannot select an epoch-3 reader cause current runtimes to reject the write before mutation. |
+| Writer/runtime range | Item-hash output | Read contract |
+|---|---|---|
+| Legacy writers before an explicit marker | implicit epoch 1 | Modern readers retain legacy canonicalization candidates. |
+| Observed 2026.8.24 through 2026.8.28 | explicit epoch 2 | Modern readers accept both field-frozen and expanded epoch-2 forms without mixing forms inside one entry. |
+| 2026.8.31 and newer | explicit epoch 3 | Exact pins and bounded ranges that cannot select an epoch-3 reader cause current runtimes to reject the write before mutation. |
 
 The table records confirmed release boundaries rather than inventing an exact
 first release for legacy epoch 1 or epoch 2. The SDK exports

package/docs/CORPUS_SHAPES.md

@@ -46,7 +46,7 @@ identifier is `https://schema.unbrained.dev/pm/corpus-shape/v1`.
 ## Built-in populations
 
 | Shape | Purpose |
-|-------|---------|
+|---|---|
 | `scratch` | Seconds-old, shallow project with minimal history |
 | `representative` | Medium-lived project with rich evidence and typed lineage |
 | `deep-graph` | Deep relationship graph with deterministic cycles |

package/docs/DEPENDENCY_KIND_CONTRACT.md

@@ -4,12 +4,12 @@ Tracker: [pm-4020c5](../.agents/pm/issues/pm-4020c5.toon), [pm-jkbqt8](../.agent
 
 Dependency rows have one canonical stored spelling per relationship meaning. Command inputs remain compatibility-friendly: hyphens normalize to underscores and the aliases below are accepted, but `pm create` and `pm update` persist the canonical kind. Existing historical rows are never rewritten implicitly.
 
-| Canonical kind | Accepted legacy aliases                |
-| -------------- | -------------------------------------- |
-| `blocked_by`   | `depends_on`, `depends-on`             |
-| `related`      | `related_to`, `related-to`             |
-| `parent`       | `child_of`, `child-of`, `epic`         |
-| `child`        | `parent_child`, `parent-child`, `task` |
+| Canonical kind | Accepted legacy aliases |
+|---|---|
+| `blocked_by` | `depends_on`, `depends-on` |
+| `related` | `related_to`, `related-to` |
+| `parent` | `child_of`, `child-of`, `epic` |
+| `child` | `parent_child`, `parent-child`, `task` |
 
 `epic` and `task` are compatibility aliases, not item types embedded in the relationship ontology. New integrations should use `parent` or `child` and express the work classification through the item `type` field.
 

package/docs/DIAGNOSTIC_OUTPUT_CONTRACTS.md

@@ -7,12 +7,12 @@ Tracker references: [pm-cha95z](../.agents/pm/tasks/pm-cha95z.toon), [pm-5t33or]
 Failures are context-management surfaces. Every diagnostic family now declares
 a format-aware token ceiling and one degradation ladder in the public SDK:
 
-| Class                | Text | JSON | Corrective action that survives degradation |
-| -------------------- | ---: | ---: | ------------------------------------------- |
-| `error`              |  768 | 2000 | required action, retry/domain, or next step |
-| `warning`            |  768 | 2000 | required action, retry/domain, or next step |
+| Class | Text | JSON | Corrective action that survives degradation |
+|---|---:|---:|---|
+| `error` | 768 | 2000 | required action, retry/domain, or next step |
+| `warning` | 768 | 2000 | required action, retry/domain, or next step |
 | `validation_summary` | 1500 | 3000 | required action, retry/domain, or next step |
-| `recovery_bundle`    |  768 | 2000 | required action, retry/domain, or next step |
+| `recovery_bundle` | 768 | 2000 | required action, retry/domain, or next step |
 
 The smallest explicit ceiling is 192 estimated tokens. At that floor, the
 projector may reduce the diagnostic to its code, required action, compact

package/docs/ECOSYSTEM_PLANNING_REVIEW.md

@@ -38,7 +38,7 @@ canonical GitHub file URL under the [documentation policy](../AGENTS.md#document
 so installed readers can access the data without a broken package-relative path.
 
 | Measure | Initial observation | Interpretation |
-| --- | ---: | --- |
+|---|---:|---|
 | Directed graph edges | 14,097 | Deduplicated directed basis |
 | Ordering layers / critical-path edges | 12 / 11 | Acyclic prerequisite graph |
 | Missing graph endpoints / isolated items | 0 / 0 | Across all statuses |
@@ -98,7 +98,7 @@ measured evidence govern promotion. Priority measures impact; horizon measures
 readiness and uncertainty. Review monthly and when a material observation changes.
 
 | Horizon | Illustrative window | Canonical outcomes and promotion evidence |
-| --- | --- | --- |
+|---|---|---|
 | Current | 0–3 months | [Agent-legible grammar](../.agents/pm/milestones/pm-j82fd3.toon), active readiness, retrieval failures, release diagnosis and current protocol proof. Require completed-task token comparisons, preserved compatibility and actual installed-consumer evidence. |
 | Emerging | 3–12 months | [Provable history](../.agents/pm/milestones/pm-w7ccmv.toon), reproducible observations and [measured self-improvement](../.agents/pm/milestones/pm-zzylb9.toon). Require independent replay, mutation coverage and three consecutive measured improvement cycles. |
 | Expansion | 12–36 months | [Proven scale](../.agents/pm/milestones/pm-o87av6.toon), [universal domain platform](../.agents/pm/milestones/pm-t4d7nz.toon), [federated agents](../.agents/pm/milestones/pm-z1kr34.toon). Require published million-item/fleet distributions and SDK-only domain exemplars. |
@@ -151,7 +151,7 @@ it does not prove the outstanding 100k/1M performance acceptance.
 Five project golden queries were evaluated at k=10:
 
 | Mode | Mean nDCG | Mean MRR | Mean recall | Broad history/episode query recall |
-| --- | ---: | ---: | ---: | ---: |
+|---|---:|---:|---:|---:|
 | Keyword | 0.7451 | 0.80 | 0.8727 | 4/11 |
 | Semantic | 0.7944 | 0.85 | 0.8182 | 1/11 |
 | Hybrid | 0.8405 | 0.90 | 0.8364 | 2/11 |

package/docs/EXTENSION_AUTHOR_CONTRACTS.md

@@ -44,7 +44,7 @@ Every `pm` command records a telemetry event. Extension commands use the same te
 Allowed values:
 
 | Value | Meaning |
-|-------|---------|
+|---|---|
 | `redacted` | Default. Records sanitized command args, options, result summary, and runtime environment. |
 | `minimal` | Records structural metadata and one-way digests only. No readable command text, args, options, result summary, or runtime environment is kept. |
 | `max` | Same as `redacted`, but raises the per-string truncation cap from 512 to 2048 characters. Redaction still applies. |
@@ -77,7 +77,7 @@ Create path:
 
 - Used by `pm update`, `pm close`, `pm claim`, `pm release`, `pm restore`, `pm delete`, and other mutations of existing items.
 - Locates the item, acquires the lock, reads the item through the `onRead` hook, enforces ownership and history policy, applies the mutation, enters the commit fence, consults `item_store_write`, writes the item atomically, appends history, fires `onWrite` for the item and history stream, records the after-command affected-item snapshot, then releases the lock.
-- `item_store_write` handlers can redirect the target path, replace serialized contents, or skip the physical item write.
+- `item_store_write` handlers can redirect the target path, replace serialized contents, or skip the physical item write. Inside an expected-revision scope (`withExpectedItemRevisions`, `--expect-hash`) the scope then advances to the item read back from storage, not the pre-override document, so the caller's next guarded write is admitted while the item stays readable in the tracker with the id the commit kept. A handler that rewrites the embedded id leaves no revision to bind to, so that write refuses with `item_revision_conflict` although no other writer ran. An item moved out of the tracker advances the scope to the empty tombstone, and a later guarded `update`, `close` or `delete` cannot locate it. Contents the store cannot parse back make the next guarded `update`, `close` or `delete` fail with `item_document_invalid` before any revision check, and a guarded `restore` refuse with `item_revision_conflict`. An `item_store_delete` handler that skips or redirects the removal advances the scope to the item that remains.
 - The commit fence verifies the lock lease and the stored item revision first. When the lease was taken over (`lock_lost`) or the item changed after the read (`stale_revision`), the mutation refuses before `item_store_write` or `item_store_delete` (non-dry-run) runs, so a handler that persists the payload itself never commits a refused write.
 
 Both paths guarantee:
@@ -91,7 +91,7 @@ Both paths guarantee:
 `changed_fields` sentinel values:
 
 | Value | Meaning |
-|-------|---------|
+|---|---|
 | `["imported"]` | Item came from an importer. |
 | `["restored"]` | Item was restored from a previous state. |
 | `["deleted"]` | Item was deleted. |
@@ -99,7 +99,7 @@ Both paths guarantee:
 Surface matrix:
 
 | Surface | Create path | `mutateItem` path |
-|---------|-------------|-------------------|
+|---|---|---|
 | `onRead` hook | No | Yes |
 | `item_store_write` service override | No | Yes |
 | `history_append` service override | Yes | Yes |

package/docs/HISTORY_ATTESTATION.md

@@ -77,7 +77,7 @@ server-local proof paths are available only to local CLI and SDK callers.
 The JSON document has exactly these fields:
 
 | Field | Meaning |
-| --- | --- |
+|---|---|
 | `format` | Literal `pm-history-attestation` |
 | `version` | Integer `1` |
 | `hash_algorithm` | `sha256` or `sha512`, for bundle commitments |

package/docs/HISTORY_MAINTENANCE.md

@@ -10,7 +10,7 @@ these policies; the CLI exposes the same operations through one history family.
 ## Command paths
 
 | Native command | Permanent compatibility spelling | Purpose |
-| --- | --- | --- |
+|---|---|---|
 | `pm history <id>` | unchanged | Read or verify one item stream |
 | `pm history activity` | `pm activity` | Read activity across streams |
 | `pm history redact <id>` | `pm history-redact <id>` | Remove selected sensitive content |

package/docs/LIFECYCLE_COMMANDS.md

@@ -17,7 +17,7 @@ pm contracts --command 'close many' --flags-only --json
 ## Command migration
 
 | Canonical invocation | Compatibility invocation |
-| --- | --- |
+|---|---|
 | `pm update many --ids <ids> --priority 1` | `pm update-many --ids <ids> --priority 1` |
 | `pm close many --ids <ids> --reason "Verified"` | `pm close-many --ids <ids> --reason "Verified"` |
 | `pm close delete <id> --dry-run` | `pm delete <id> --dry-run` |

package/docs/MCP_2026_07_28.md

@@ -49,10 +49,10 @@ Legacy means every revision that establishes a session with an `initialize`
 handshake, which the canonical revision defines as `2025-11-25` and earlier.
 The stdio adapter therefore accepts the full initialize-era set, newest first:
 
-| Revision     | Accepted at `initialize` | Notes                                                                |
-| ------------ | ------------------------ | -------------------------------------------------------------------- |
-| `2025-11-25` | yes                      | Final legacy revision; offered when a client omits `protocolVersion` |
-| `2025-06-18` | yes                      | Earlier legacy revision retained for existing consumers              |
+| Revision | Accepted at `initialize` | Notes |
+|---|---|---|
+| `2025-11-25` | yes | Final legacy revision; offered when a client omits `protocolVersion` |
+| `2025-06-18` | yes | Earlier legacy revision retained for existing consumers |
 
 `initialize` answers with the revision the client requested, because a legacy
 client has no fall-forward mechanism and treats the answered version as the
@@ -101,18 +101,18 @@ windows. Removal is a reviewed compatibility change, never a history rewrite.
 
 ## Removed, migrated, and deprecated behavior
 
-| Prior behavior                                                    | Disposition                                                                                                 |
-| ----------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------- |
-| `initialize` and `notifications/initialized`                      | Legacy stdio adapter only; absent from modern behavior.                                                     |
-| `Mcp-Session-Id` and protocol sessions                            | Removed; explicit application handles are ordinary arguments.                                               |
-| `ping`                                                            | Legacy adapter only; modern calls return Method Not Found.                                                  |
-| `resources/subscribe` and `resources/unsubscribe`                 | Replaced by the implemented `subscriptions/listen` filter.                                                  |
-| SSE event ids and `Last-Event-ID` replay                          | Removed; callers retry with a new request id.                                                               |
-| Reverse `roots/list`, sampling, and elicitation requests          | Migrate to MRTR `input_required` under `pm-rz9gep`.                                                         |
-| Core tasks                                                        | Migrate to `io.modelcontextprotocol/tasks` under `pm-rzs24j`.                                               |
-| `logging/setLevel`                                                | Removed; optional request-local log metadata is never shared, and remote operations use host OpenTelemetry. |
-| Roots, Sampling, Logging, HTTP+SSE, and non-none `includeContext` | Retain only in bounded legacy compatibility while `pm-vzcisw` drives deprecation removal.                   |
-| Dynamic Client Registration                                       | Legacy authorization fallback; Client ID Metadata Documents are canonical under `pm-3zh9s4`.                |
+| Prior behavior | Disposition |
+|---|---|
+| `initialize` and `notifications/initialized` | Legacy stdio adapter only; absent from modern behavior. |
+| `Mcp-Session-Id` and protocol sessions | Removed; explicit application handles are ordinary arguments. |
+| `ping` | Legacy adapter only; modern calls return Method Not Found. |
+| `resources/subscribe` and `resources/unsubscribe` | Replaced by the implemented `subscriptions/listen` filter. |
+| SSE event ids and `Last-Event-ID` replay | Removed; callers retry with a new request id. |
+| Reverse `roots/list`, sampling, and elicitation requests | Migrate to MRTR `input_required` under `pm-rz9gep`. |
+| Core tasks | Migrate to `io.modelcontextprotocol/tasks` under `pm-rzs24j`. |
+| `logging/setLevel` | Removed; optional request-local log metadata is never shared, and remote operations use host OpenTelemetry. |
+| Roots, Sampling, Logging, HTTP+SSE, and non-none `includeContext` | Retain only in bounded legacy compatibility while `pm-vzcisw` drives deprecation removal. |
+| Dynamic Client Registration | Legacy authorization fallback; Client ID Metadata Documents are canonical under `pm-3zh9s4`. |
 
 ## Rollout, rollback, and proof
 

package/docs/MCP_2026_07_28_CONFORMANCE.md

@@ -5,25 +5,25 @@ Tracker: [pm-55yf1t](../.agents/pm/tasks/pm-55yf1t.toon). The official
 every revision-level change to one canonical pm owner and records executable
 evidence or an explicit open obligation.
 
-| Requirement family                                                                                 | Canonical owner                                     | Current disposition                                                                                                      | Executable evidence                                                                       |
-| -------------------------------------------------------------------------------------------------- | --------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------- |
-| Stateless per-request version, client capabilities, and identity                                   | [pm-vae5ec](../.agents/pm/features/pm-vae5ec.toon)  | Implemented                                                                                                              | `tests/unit/sdk/mcp/protocol.spec.ts`, `tests/integration/mcp-stateless-protocol.spec.ts` |
-| Mandatory `server/discover`, deterministic capabilities and identity                               | [pm-vae5ec](../.agents/pm/features/pm-vae5ec.toon)  | Implemented                                                                                                              | direct SDK/server tests plus plugin and release real-process probes                       |
-| Unsupported version `-32022`                                                                       | [pm-vae5ec](../.agents/pm/features/pm-vae5ec.toon)  | Implemented                                                                                                              | SDK and server negative controls                                                          |
-| Header mismatch `-32020` and missing capability `-32021`                                           | [pm-vae5ec](../.agents/pm/features/pm-vae5ec.toon)  | Implemented in SDK, stdio, and Streamable HTTP                                                                            | SDK negative controls and `tests/integration/mcp-streamable-http.spec.ts`                 |
-| Required result `resultType`; legacy omission means complete only at compatibility boundary        | [pm-vae5ec](../.agents/pm/features/pm-vae5ec.toon)  | Implemented for modern pm results                                                                                        | SDK unit and modern direct-server tests                                                   |
-| No modern initialize, initialized notification, ping, or protocol session                          | [pm-sqvshj](../.agents/pm/decisions/pm-sqvshj.toon) | Implemented with bounded legacy stdio adapter                                                                            | modern removed-method and legacy handshake tests                                          |
-| Legacy interoperability covers every initialize-era revision the spec names   | [pm-edywqn](../.agents/pm/issues/pm-edywqn.toon)   | Implemented: `2025-11-25` and `2025-06-18` accepted, requested revision echoed                                            | `tests/integration/mcp-handshake.spec.ts` handshake matrix plus the plugin smoke `assertProtocolHandshakeMatrix` real-process gate and its negative control |
-| MRTR `input_required`, retry state, and reverse-request removal                                    | [pm-rz9gep](../.agents/pm/features/pm-rz9gep.toon)  | Implemented for SDK and stateless stdio adapter                                                                          | `tests/unit/sdk/mcp/interactions.spec.ts`; direct server negative controls                |
-| `subscriptions/listen`, request-scoped streams, no SSE resumability                                | [pm-v7e337](../.agents/pm/features/pm-v7e337.toon)  | Implemented; consumer acceptance remains a per-release gate                                                             | subscription SDK, stdio, HTTP, backpressure, disconnect, and retry tests                  |
-| Official `io.modelcontextprotocol/tasks` extension                                                 | [pm-rzs24j](../.agents/pm/features/pm-rzs24j.toon)  | Implemented for eligible tool calls, durable lifecycle, and stdio methods; notifications remain with subscriptions owner | `tests/unit/sdk/mcp/tasks.spec.ts`, `tests/integration/mcp-stateless-protocol.spec.ts`    |
-| Cacheable list/read results, deterministic tools, JSON Schema 2020-12, any JSON structured content | [pm-hv1x1x](../.agents/pm/features/pm-hv1x1x.toon)  | Implemented for current pm tool/resource/prompt surfaces                                                                 | SDK schema/cache tests and direct modern server surface suite                             |
-| Issuer-bound authorization, client metadata documents, consent, headers, OpenTelemetry             | [pm-3zh9s4](../.agents/pm/features/pm-3zh9s4.toon)  | Implemented; deployment-specific identity-provider verification remains host-owned                                       | authorization SDK adversarial tests, real HTTP bearer suite, and threat model             |
-| Stable MCP Apps negotiation, tool/resource metadata, fallback, sandboxing, and accessible views    | [pm-pznhee](../.agents/pm/features/pm-pznhee.toon)  | Implemented in the public SDK and stateless server; exact-version journeys run in the published-release verifier           | `tests/unit/sdk/mcp/apps.spec.ts`, `tests/integration/mcp-stateless-protocol.spec.ts`      |
-| Draft Skills over MCP list/get/read, compatibility, provenance, digests, bounds, and pagination    | [pm-8nzivt](../.agents/pm/features/pm-8nzivt.toon)  | Implemented against exact SEP-2640 draft revision; the published-release verifier checks negotiation and content digests   | `tests/unit/sdk/mcp/skills.spec.ts`, `tests/integration/mcp-stateless-protocol.spec.ts`    |
-| Per-request `io.modelcontextprotocol/logLevel`; omission forbids `notifications/message`          | [pm-pd7nh0](../.agents/pm/tasks/pm-pd7nh0.toon)    | SDK validates the eight severity values and rejects malformed metadata with `-32602`; pm emits no protocol log notifications | `tests/unit/sdk/mcp/protocol.spec.ts`, real stdio and Streamable HTTP negative controls |
-| Deprecated Roots, Sampling, Logging, HTTP+SSE, `includeContext`, dynamic registration              | [pm-vzcisw](../.agents/pm/chores/pm-vzcisw.toon)    | Canonical source ratcheted; bounded stdio adapter and dated migration policy remain                                      | generated inventory, negative controls, adapter tests, and migration guide                |
-| Official schema, real stdio/HTTP, packed/published, npx/bunx, negative controls                    | [pm-55yf1t](../.agents/pm/tasks/pm-55yf1t.toon)     | Conformance and released-consumer gates implemented; each release must produce its own acceptance evidence                 | SDK/server suites, plugin smokes, published-release verifier                              |
+| Requirement family | Canonical owner | Current disposition | Executable evidence |
+|---|---|---|---|
+| Stateless per-request version, client capabilities, and identity | [pm-vae5ec](../.agents/pm/features/pm-vae5ec.toon) | Implemented | `tests/unit/sdk/mcp/protocol.spec.ts`, `tests/integration/mcp-stateless-protocol.spec.ts` |
+| Mandatory `server/discover`, deterministic capabilities and identity | [pm-vae5ec](../.agents/pm/features/pm-vae5ec.toon) | Implemented | direct SDK/server tests plus plugin and release real-process probes |
+| Unsupported version `-32022` | [pm-vae5ec](../.agents/pm/features/pm-vae5ec.toon) | Implemented | SDK and server negative controls |
+| Header mismatch `-32020` and missing capability `-32021` | [pm-vae5ec](../.agents/pm/features/pm-vae5ec.toon) | Implemented in SDK, stdio, and Streamable HTTP | SDK negative controls and `tests/integration/mcp-streamable-http.spec.ts` |
+| Required result `resultType`; legacy omission means complete only at compatibility boundary | [pm-vae5ec](../.agents/pm/features/pm-vae5ec.toon) | Implemented for modern pm results | SDK unit and modern direct-server tests |
+| No modern initialize, initialized notification, ping, or protocol session | [pm-sqvshj](../.agents/pm/decisions/pm-sqvshj.toon) | Implemented with bounded legacy stdio adapter | modern removed-method and legacy handshake tests |
+| Legacy interoperability covers every initialize-era revision the spec names | [pm-edywqn](../.agents/pm/issues/pm-edywqn.toon) | Implemented: `2025-11-25` and `2025-06-18` accepted, requested revision echoed | `tests/integration/mcp-handshake.spec.ts` handshake matrix plus the plugin smoke `assertProtocolHandshakeMatrix` real-process gate and its negative control |
+| MRTR `input_required`, retry state, and reverse-request removal | [pm-rz9gep](../.agents/pm/features/pm-rz9gep.toon) | Implemented for SDK and stateless stdio adapter | `tests/unit/sdk/mcp/interactions.spec.ts`; direct server negative controls |
+| `subscriptions/listen`, request-scoped streams, no SSE resumability | [pm-v7e337](../.agents/pm/features/pm-v7e337.toon) | Implemented; consumer acceptance remains a per-release gate | subscription SDK, stdio, HTTP, backpressure, disconnect, and retry tests |
+| Official `io.modelcontextprotocol/tasks` extension | [pm-rzs24j](../.agents/pm/features/pm-rzs24j.toon) | Implemented for eligible tool calls, durable lifecycle, and stdio methods; notifications remain with subscriptions owner | `tests/unit/sdk/mcp/tasks.spec.ts`, `tests/integration/mcp-stateless-protocol.spec.ts` |
+| Cacheable list/read results, deterministic tools, JSON Schema 2020-12, any JSON structured content | [pm-hv1x1x](../.agents/pm/features/pm-hv1x1x.toon) | Implemented for current pm tool/resource/prompt surfaces | SDK schema/cache tests and direct modern server surface suite |
+| Issuer-bound authorization, client metadata documents, consent, headers, OpenTelemetry | [pm-3zh9s4](../.agents/pm/features/pm-3zh9s4.toon) | Implemented; deployment-specific identity-provider verification remains host-owned | authorization SDK adversarial tests, real HTTP bearer suite, and threat model |
+| Stable MCP Apps negotiation, tool/resource metadata, fallback, sandboxing, and accessible views | [pm-pznhee](../.agents/pm/features/pm-pznhee.toon) | Implemented in the public SDK and stateless server; exact-version journeys run in the published-release verifier | `tests/unit/sdk/mcp/apps.spec.ts`, `tests/integration/mcp-stateless-protocol.spec.ts` |
+| Draft Skills over MCP list/get/read, compatibility, provenance, digests, bounds, and pagination | [pm-8nzivt](../.agents/pm/features/pm-8nzivt.toon) | Implemented against exact SEP-2640 draft revision; the published-release verifier checks negotiation and content digests | `tests/unit/sdk/mcp/skills.spec.ts`, `tests/integration/mcp-stateless-protocol.spec.ts` |
+| Per-request `io.modelcontextprotocol/logLevel`; omission forbids `notifications/message` | [pm-pd7nh0](../.agents/pm/tasks/pm-pd7nh0.toon) | SDK validates the eight severity values and rejects malformed metadata with `-32602`; pm emits no protocol log notifications | `tests/unit/sdk/mcp/protocol.spec.ts`, real stdio and Streamable HTTP negative controls |
+| Deprecated Roots, Sampling, Logging, HTTP+SSE, `includeContext`, dynamic registration | [pm-vzcisw](../.agents/pm/chores/pm-vzcisw.toon) | Canonical source ratcheted; bounded stdio adapter and dated migration policy remain | generated inventory, negative controls, adapter tests, and migration guide |
+| Official schema, real stdio/HTTP, packed/published, npx/bunx, negative controls | [pm-55yf1t](../.agents/pm/tasks/pm-55yf1t.toon) | Conformance and released-consumer gates implemented; each release must produce its own acceptance evidence | SDK/server suites, plugin smokes, published-release verifier |
 
 This matrix describes implementation coverage, not a blanket certification of
 every deployed artifact. Programme completion requires each owner's positive