@unbrained/pm-cli 2026.9.9 → 2026.9.11

package/docs/COMMAND_NAMESPACES.md

@@ -0,0 +1,65 @@
+# Context and operations command namespaces
+
+Tracked in [pm-kcs4](../.agents/pm/tasks/pm-kcs4.toon),
+[pm-6apl](../.agents/pm/tasks/pm-6apl.toon), and
+[pm-3i9q8g](../.agents/pm/tasks/pm-3i9q8g.toon).
+
+The CLI groups navigation and maintenance under stable nouns. Existing root
+spellings remain executable compatibility aliases with the same arguments,
+results, exit codes, and SDK behavior.
+
+| Native invocation | Compatibility spelling | Purpose |
+| --- | --- | --- |
+| `pm context next` | `pm next` | Select ready work and explain blockers |
+| `pm context focus` | `pm focus` | Read, set, or clear the focused item |
+| `pm ops stats` | `pm stats` | Inspect tracker statistics |
+| `pm ops health` | `pm health` | Diagnose tracker health |
+| `pm ops validate` | `pm validate` | Validate metadata and history |
+| `pm ops gc` | `pm gc` | Clean optional cache artifacts |
+| `pm ops telemetry` | `pm telemetry` | Inspect and manage telemetry |
+| `pm ops eval` | `pm eval` | Evaluate retrieval quality |
+| `pm ops test-all` | `pm test-all` | Run selected linked tests |
+| `pm ops reindex` | `pm reindex` | Refresh indexes through search-advanced |
+| `pm ops normalize` | `pm normalize` | Normalize through an active governance package |
+| `pm history events` | `pm events` | Read or follow committed mutation events |
+
+`pm context --limit 10 --for orient` still produces a context snapshot.
+`pm history <id> --verify` still reads and verifies one item's history.
+Namespace leaves do not change either default operation.
+
+## Discover only what the current task needs
+
+```bash
+pm context next --limit 5 --ready-only
+pm context focus --id pm-example
+pm ops health --check-only --summary
+pm ops validate --check-history-drift
+pm history events --item pm-example --limit 10
+pm ops --help
+pm contracts --command "ops stats" --flags-only
+```
+
+Help, contracts, and shell completion expose native paths. Compatibility aliases
+remain declared in the SDK alias table. Alias guidance uses the existing
+`ux.deprecation_hints` setting. Human-readable calls emit it on stderr; JSON and
+quiet calls suppress it. Compact contract summaries omit duplicate root alias
+rows; full and explicitly selected contracts retain them. Optional commands appear only when their providing package is active;
+namespace placement does not promote package behavior into core.
+
+## SDK and package integration
+
+`PM_NAMESPACED_COMMAND_ALIASES` and `resolvePmCommandOperation` are exported
+from `@unbrained/pm-cli/sdk` and `@unbrained/pm-cli/sdk/contracts`.
+The resolver maps a native path such as `context next` to the existing SDK
+operation identity `next`. Unknown paths are preserved. SDK functions, MCP
+action names, extension activation selectors, and command hooks retain their
+existing operation identities.
+
+Packages that provide `reindex` or `normalize` keep their existing command
+registration. The CLI places the registered handler beneath `ops` after
+activation, preserving flags, argument parsing, and nested commands. A conflicting
+native destination fails explicitly instead of silently replacing a handler.
+
+Generated Bash, Zsh, and Fish scripts recognize namespace command positions and
+skip global option values when selecting a leaf. Re-generate installed completion
+scripts after upgrading with `pm completion <shell>` from guide-shell.

package/docs/HISTORY_ATTESTATION.md

@@ -0,0 +1,164 @@
+# History algorithms and detached attestations
+
+Tracking: [pm-bbk8we](../.agents/pm/issues/pm-bbk8we.toon),
+[pm-3z0k](../.agents/pm/features/pm-3z0k.toon).
+
+A detached attestation commits to the exact bytes of every retained history
+stream. Keep the bundle, or its workspace digest, independently of the tracker.
+Verification can then detect a rewritten stream even when its author recomputed
+an internally valid hash chain.
+
+## CLI
+
+```sh
+pm history attest --output proof.json
+pm history attest --verify proof.json
+pm history attest --hash-algorithm sha512 --output proof-sha512.json
+```
+
+Export with `--output` creates a new JSON file exclusively and returns a compact
+receipt containing its path, workspace digest, and stream count. Existing files
+are not overwritten. Without `--output`, export writes the complete JSON bundle
+to stdout. Proof bytes bypass default row projection and output budgets so a
+redirected artifact retains its digest. Explicit universal output controls such
+as `--output-limit` are rejected. `--quiet` suppresses stdout. Verification returns a nonzero process
+exit status if any stream changed, appeared, disappeared, or failed validation.
+`--verify` cannot be combined with export options.
+
+Only the tracker directory and its `history/*.jsonl` files are needed. For a
+bare history copy, select the directory containing `history`:
+
+```sh
+pm --pm-path /path/to/copied-tracker history attest --verify proof.json
+```
+
+Item files, settings, indexes, extensions, and the original Git checkout are not
+needed. The verifier does not acquire tracker locks or create derived state.
+CLI attestation invocations disable extension loading automatically.
+
+## SDK
+
+```ts
+import {
+  exportAttestation,
+  parseHistoryAttestation,
+  verifyAttestation,
+} from "@unbrained/pm-cli/sdk/governance";
+
+const proof = await exportAttestation({
+  pmRoot: "/path/to/tracker",
+  hashAlgorithm: "sha256",
+});
+const parsed = parseHistoryAttestation(proof);
+const result = await verifyAttestation(parsed, {
+  pmRoot: "/path/to/copied-tracker",
+});
+```
+
+The same APIs are available from the SDK root. `generatedAt` optionally accepts
+an RFC 3339 timestamp with millisecond precision for reproducible exports.
+Equal stream bytes, options, and timestamps yield identical bundle digests.
+`PmClient.historyAttest` and `runAction({ action: "history-attest", ... })` expose
+the adapter used by CLI and MCP. Local CLI and SDK callers may use proof paths;
+SDK callers may also pass a typed bundle as `verify`. Direct export and verify functions
+accept and return typed bundles without requiring a proof file.
+
+## MCP
+
+Call `pm_run` with `action: "history-attest"` to receive the complete JSON bundle.
+Retain it on the client and pass that object as `verify` to compare the tracker.
+Both flat arguments and nested `options` use this data-only proof transport.
+MCP refuses `output` and string `verify` values before accessing proof files;
+server-local proof paths are available only to local CLI and SDK callers.
+
+## Version 1 wire format
+
+`PM_HISTORY_ATTESTATION_CONTRACT` is exported from the SDK contracts entrypoint.
+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 |
+| `generated_at` | Exporter's asserted timestamp |
+| `streams` | Complete retained stream inventory, sorted by ID |
+| `workspace_digest` | Digest of the stable JSON encoding of all other fields |
+
+Each stream contains its filename stem, exact byte length, nonblank record count,
+exact-byte digest, latest item-state and whole-record anchors, latest record
+algorithm, retained rewrite-evidence count, compact checkpoint digest, and last
+maintenance marker. Empty streams have null anchors and no maintenance marker.
+The workspace stream and streams belonging to deleted items are included.
+Identifiers contain only ASCII letters, digits, underscores, and hyphens.
+No item content, author, filesystem root, or patch value is embedded in a bundle.
+The bundle grows with the number of streams, not their event counts.
+
+Stream digests hash all file bytes, including blank lines, whitespace, and line
+endings. Thus a formatting-only change is also a divergence. The workspace
+rollup uses the SDK's recursive stable JSON encoding with sorted object keys
+and preserved array order, excluding only `workspace_digest`. Stream ordering
+uses ascending JavaScript code-unit comparison of IDs, not locale collation.
+Lowercase hexadecimal digest lengths are 64 for SHA-256 and 128 for SHA-512.
+
+Verification validates the bundle schema and rollup before inspecting files.
+It reports `changed_streams`, `missing_streams`, `added_streams`, and
+`invalid_streams`; these categories may overlap. `transitions` includes before
+and after byte digests plus the current last maintenance marker for each changed
+stream. Export refuses invalid streams instead of producing partial evidence.
+Unknown format versions and algorithms are rejected.
+
+## Record algorithms and migration
+
+Each new history entry names `hash_algorithm`. This label selects the digest
+used for `before_hash`, `after_hash`, and `record_hash`. Current writers default
+to `sha256`; callers constructing entries may explicitly select `sha512`.
+The immutable record digest covers the algorithm label itself.
+
+An absent label **always means SHA-256**, regardless of future writer defaults.
+Existing unlabeled history remains verifiable without rewriting it. A stream
+may mix algorithms: replay reconstructs the prior state and verifies each link
+using that entry's declared algorithm. Adjacent bare digest strings need not be
+equal when algorithms differ. Unknown labels fail verification even on legacy
+entries without whole-record seals.
+
+`item_hash_version` selects canonical item encoding and remains separate from
+`hash_algorithm`. The item document `format_version` does not change for this
+additive history field. `record_hash_version: 1` still defines stable record
+encoding; the algorithm field defines the digest. Older readers lacking the
+algorithm capability cannot verify SHA-512 entries and should be upgraded
+before such entries are introduced. No automatic archive migration is needed.
+
+Retained rewrite evidence carries the original entry's algorithm. Repair,
+redaction, merge reconciliation, and compaction preserve verifiable original
+algorithm commitments where they retain evidence. Version 1 patch digests and
+compact pruned-prefix commitments remain explicitly fixed to SHA-256; they are
+separate commitments, not item-state or record digests.
+
+Advancing the default affects future writes only. Never infer an unlabeled
+record's algorithm from digest length or the current default, and never rewrite
+an archive simply to add labels. Bundle algorithms are independent of record
+algorithms: a SHA-256 bundle can cover SHA-512 records and vice versa. Existing
+bundles retain their declared verification algorithm. Re-export after an
+intentional append or maintenance operation, review the reported transition,
+and retain both proofs if historical comparison matters.
+
+## Trust and consistency
+
+A self-consistent bundle is not a digital signature or a trusted timestamp. It
+does not identify an author, prove that events happened in the real world, or
+recover a pruned prefix. If an attacker can replace both tracker and trusted
+bundle, these hashes do not establish authenticity. Packages can anchor the
+workspace digest in an independent repository, signing service, or transparency
+log without changing this baseline format.
+
+Verification establishes equality with the retained proof and checks each
+current stream's internal replay integrity. It does not assert that current
+item files match history, or that every intended mutation was recorded. Use
+normal workspace validation for those checks.
+
+The scanner takes a snapshot per stream and checks filename inventories and
+file metadata again before returning. Observable concurrent changes fail with
+a retry error. This is not a transaction across independent writers; use a
+quiescent or externally snapshotted copy when a single workspace-wide instant
+is required. Symlink stream files and malformed UTF-8/JSONL are invalid.

package/docs/LIFECYCLE_COMMANDS.md

@@ -0,0 +1,77 @@
+# Lifecycle Commands and Ownership
+
+Tracked by [pm-ik19](../.agents/pm/tasks/pm-ik19.toon) and
+[pm-eq4x](../.agents/pm/tasks/pm-eq4x.toon).
+
+Bulk mutations and ownership compositions share SDK implementations with their
+compatibility spellings. Runtime help and contracts describe the active surface:
+
+```bash
+pm update many --help
+pm close many --help
+pm close delete --help
+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` |
+| `pm claim <id> --start` | `pm start-task <id>` |
+| `pm release <id> --pause` | `pm pause-task <id>` |
+| `pm close <id> "Verified" --release-assignment` | `pm close-task <id> "Verified"` |
+
+The old spellings remain accepted as hidden aliases. Bulk aliases are permanent;
+the three task aliases are deprecated. Human output for deprecated aliases can
+include migration hints according to `ux.deprecation_hints`; JSON and quiet
+invocations suppress those hints. Bulk commands retain their existing filters,
+stdin selection, dry runs, rollback behavior, and evidence flags. Put bulk flags
+after `many`. Deletion recovery remains `pm history restore <id> <version>`.
+
+Plain `claim`, `release`, `update`, and `close` keep their original semantics.
+`claim --start` requires an explicit item and rejects `--next` and
+`--if-available` before mutation. It claims ownership, then moves the item to the
+configured in-progress status. `release --pause` moves work to the configured
+open status, then releases ownership. `close --release-assignment` records the
+close and its inline evidence, then releases ownership.
+
+Each constituent operation enforces its own policy and writes its own history.
+Compositions do not provide rollback across operations: for example, if the
+status transition fails after a successful claim, the claim remains. Inspect the
+item before retrying after an error.
+
+## SDK and MCP
+
+```ts
+import { PmClient } from "@unbrained/pm-cli/sdk";
+
+const pm = new PmClient({ pmRoot: "/project/.agents/pm" });
+const started = await pm.claim("pm-example", { start: true });
+const paused = await pm.release("pm-example", { pause: true });
+const closed = await pm.close("pm-example", "Acceptance verified", {
+  releaseAssignment: true,
+  resolution: "Implemented the requested behavior",
+  expectedResult: "Acceptance checks pass",
+  actualResult: "Acceptance checks passed",
+  validateClose: "warn",
+});
+```
+
+Literal `true` options return typed `StartTaskResult`, `PauseTaskResult`, or
+`CloseTaskResult` receipts. Their discriminators remain `start_task`,
+`pause_task`, and `close_task`, with the constituent results available under
+`claim`, `update`, `close`, or `release`. Public `runStartTask`, `runPauseTask`, and
+`runCloseTask` primitives expose the same SDK-owned compositions.
+
+MCP actions remain `claim`, `release`, and `close`, using `start`, `pause`, and
+`releaseAssignment`. Action-specific discovery types claim's `start` as boolean;
+scheduling actions retain string timestamps. For the broad provider tool schema,
+pass the claim boolean through `options: { start: true }` because its shared flat
+`start` property retains the scheduling string contract. Bulk action names remain
+`update_many`, `close_many`, and `delete` for transport compatibility.
+
+See [SDK Lifecycle Policy](SDK_LIFECYCLE.md) for transaction and policy ownership
+and [CLI Scripting Contract](SCRIPTING.md) for output projection.

package/docs/README.md

@@ -35,6 +35,7 @@ pm guide release --json
 - [Onboarding](ONBOARDING.md) - first-two-hours maintainer and contributor setup.
 - [Agent Guide](AGENT_GUIDE.md) - canonical agent loop, tracker linking, and token-minimal command choices.
 - [Command Reference](COMMANDS.md) - command families with examples and when to use each family.
+- [Context and Operations Namespaces](COMMAND_NAMESPACES.md) - native navigation, diagnostics, event streams, and compatibility aliases.
 - [CLI Scripting Contract](SCRIPTING.md) - exit codes, flat mutation receipts versus read envelopes, stdout/stderr boundaries, stable JSON fields, uniform OR filters, and shell composition recipes.
 - [Configuration](CONFIGURATION.md) - settings, storage formats, output, search, validation, and environment variables.
 - [Testing](TESTING.md) - sandbox-safe local tests and linked-test orchestration.
@@ -61,6 +62,7 @@ pm guide release --json
 - [Generated Refusal Closure Census](generated/REFUSAL_CLOSURE_CENSUS.md) - complete error-catalog join to executable refusal evidence and explicit uncovered obligations.
 - [Universal Read Output Contracts](READ_OUTPUT_CONTRACTS.md) - cross-command include, amount, cost, and encoding controls for CLI, SDK, MCP, and packages.
 - [Diagnostic Output Contracts](DIAGNOSTIC_OUTPUT_CONTRACTS.md) - action-first error budgets, deterministic degradation, SDK projection, and executable refusal assurance.
+- [History Algorithms and Detached Attestations](HISTORY_ATTESTATION.md) - named record digests, portable exact-byte proofs, and read-only verification.
 - [History Maintenance and Recovery](HISTORY_MAINTENANCE.md) - native history commands, permanent aliases, shared SDK transforms, and transactional recovery.
 - [Declarative Workflow Policies](WORKFLOW_POLICIES.md) - portable lifecycle requirements, independent approvals, and completeness reports.
 - [Mutation Integrity](MUTATION_INTEGRITY.md) - shared CLI/SDK/MCP author, secret, append-only disposition, and stale-work guardrails.
@@ -100,6 +102,7 @@ Additional SDK, operations, and generated contracts:
 - [Item Read Projections](ITEM_READ_PROJECTIONS.md) - identity, projections, and read completeness.
 - [MCP Capability Surfaces](MCP_CAPABILITY_SURFACES.md) - negotiated MCP discovery contracts.
 - [PR Review Loop](PR_REVIEW_LOOP.md) - complete review inventories and feedback acknowledgment.
+- [Lifecycle Commands and Ownership](LIFECYCLE_COMMANDS.md) - canonical bulk commands, ownership compositions, and SDK/MCP migration.
 - [SDK Lifecycle](SDK_LIFECYCLE.md) - lifecycle primitives and package integration.
 - [SDK Runtime Boundaries](SDK_RUNTIME_BOUNDARIES.md) - runtime ownership and import boundaries.
 - [Sentry Contract Epochs](SENTRY_CONTRACT_EPOCHS.md) - diagnostic compatibility and release epochs.

package/docs/READ_OUTPUT_CONTRACTS.md

@@ -153,6 +153,19 @@ pm contracts --full --json
 
 Every projected result carries a `read_output` receipt with the requested dimensions, precedence, observed option provenance, deterministic estimated token count, string/row compaction signals, and budget outcome. When canonical controls are present, `canonical_options_used` records spellings such as `--output-include`; the optional field is omitted when no canonical control was supplied so minimum-budget session receipts remain compact. `legacy_aliases_used` and `migration_hints` record only compatibility flags the caller actually supplied. A command-local flag synthesized internally to execute a canonical projection mode is therefore never misreported as deprecated syntax. When both spellings are supplied, both provenance arrays report that mixed invocation. Budget degradation discovers nested arrays as well as declared result rows, so validation diagnostics and other governance payloads compact their inner findings before the useful result is omitted. `compacted_row_paths` names every reduced collection without redefining those nested arrays as ordinary pagination rows.
 
+The estimate is `ceil(utf8_bytes / 4)` for the complete envelope. The CLI uses
+its selected built-in JSON or TOON representation, including indentation and
+the final newline. SDK calls that select `outputFormat` use that representation;
+structured SDK calls without a renderer retain compact JSON measurement.
+Those unformatted calls keep the conservative workload-class ceiling
+(`default_max_estimated_tokens`, also used as the generated TOON ceiling).
+Selecting JSON explicitly opts into its larger declared rendering allowance;
+serializing an SDK object for measurement does not implicitly select that policy.
+Per-call and session receipts include their own cost and continuation disclosure.
+Compaction reserves room for that disclosure before returning a useful page, so
+an envelope cannot claim to fit merely because its rows fit before receipts were
+added. An infeasible ceiling returns the explicit omission result.
+
 For `context` and `next`, that final projection is also the usage-feedback
 delivery boundary. The SDK carries a JSON-invisible serve receipt through
 intent and universal output projection, then appends the final omitted decision

package/docs/generated/AGENT_CAPABILITY_ROUTING.md

@@ -6,12 +6,12 @@ This file is generated from `PM_COMMAND_CAPABILITY_CONTRACTS`. Do not edit it ma
 
 | Capability family | Commands |
 | --- | --- |
-| workspace | `init`, `config`, `merge`, `schema`, `profile`, `telemetry`, `health`, `gc`, `workspace` |
-| intake | `create`, `copy`, `focus`, `restore` |
-| context | `list`, `aggregate`, `context`, `get`, `search`, `duplicates`, `eval`, `next`, `activity`, `stats`, `help` |
-| lifecycle | `update`, `update-many`, `close`, `close-many`, `delete`, `claim`, `release`, `start-task`, `pause-task`, `close-task` |
-| evidence | `history`, `events`, `history-redact`, `history-repair`, `history-compact`, `history-author-acknowledge`, `append`, `comments`, `notes`, `learnings`, `files`, `docs` |
+| workspace | `init`, `config`, `workspace merge`, `schema`, `profile`, `ops telemetry`, `ops health`, `ops gc`, `workspace` |
+| intake | `create`, `item copy`, `context focus`, `history restore` |
+| context | `list`, `aggregate`, `context`, `get`, `search`, `item duplicates`, `ops eval`, `context next`, `history activity`, `ops stats`, `help` |
+| lifecycle | `update`, `update many`, `close`, `close many`, `close delete`, `claim`, `release` |
+| evidence | `history`, `history events`, `history redact`, `history repair`, `history compact`, `history attest`, `history-author-acknowledge`, `append`, `comments`, `notes`, `learnings`, `files`, `docs` |
 | graph | `graph`, `deps`, `plan` |
-| quality | `test`, `test-all`, `validate`, `assurance`, `contracts` |
+| quality | `test`, `ops test-all`, `ops validate`, `assurance`, `contracts`, `ops` |
 | automation | `meet`, `event`, `remind` |
 | extensions | `package` |

package/docs/generated/AGENT_COMMAND_SURFACE.md

@@ -14,7 +14,9 @@ This file is generated from `PM_COMMAND_CAPABILITY_CONTRACTS`. Do not edit it ma
 | `create` | core | intake |
 | `item-reopen` | full | lifecycle |
 | `copy` | full | intake |
+| `item copy` | full | intake |
 | `focus` | standard | intake |
+| `context focus` | standard | intake |
 | `list` | core | context |
 | `list-all` | standard | context |
 | `list-draft` | full | context |
@@ -30,24 +32,39 @@ This file is generated from `PM_COMMAND_CAPABILITY_CONTRACTS`. Do not edit it ma
 | `graph` | standard | graph |
 | `search` | core | context |
 | `duplicates` | full | context |
+| `item duplicates` | full | context |
 | `eval` | full | context |
+| `ops eval` | full | context |
 | `next` | core | context |
+| `context next` | core | context |
 | `history` | standard | evidence |
 | `events` | standard | evidence |
+| `history events` | standard | evidence |
 | `history-redact` | full | evidence |
+| `history redact` | full | evidence |
 | `history-repair` | full | evidence |
+| `history repair` | full | evidence |
 | `history-compact` | full | evidence |
+| `history compact` | full | evidence |
+| `history-attest` | full | evidence |
+| `history attest` | full | evidence |
 | `history-author-acknowledge` | full | evidence |
 | `merge` | full | workspace |
+| `workspace merge` | full | workspace |
 | `schema` | standard | workspace |
 | `profile` | standard | workspace |
 | `activity` | full | context |
+| `history activity` | full | context |
 | `restore` | full | intake |
+| `history restore` | full | intake |
 | `update` | core | lifecycle |
 | `update-many` | full | lifecycle |
+| `update many` | full | lifecycle |
 | `close` | core | lifecycle |
 | `close-many` | full | lifecycle |
+| `close many` | full | lifecycle |
 | `delete` | full | lifecycle |
+| `close delete` | full | lifecycle |
 | `append` | standard | evidence |
 | `comments` | standard | evidence |
 | `notes` | standard | evidence |
@@ -58,12 +75,18 @@ This file is generated from `PM_COMMAND_CAPABILITY_CONTRACTS`. Do not edit it ma
 | `plan` | core | graph |
 | `test` | standard | quality |
 | `test-all` | full | quality |
+| `ops test-all` | full | quality |
 | `telemetry` | full | workspace |
+| `ops telemetry` | full | workspace |
 | `stats` | full | context |
+| `ops stats` | full | context |
 | `health` | standard | workspace |
+| `ops health` | standard | workspace |
 | `validate` | core | quality |
+| `ops validate` | core | quality |
 | `assurance` | full | quality |
 | `gc` | full | workspace |
+| `ops gc` | full | workspace |
 | `workspace` | full | workspace |
 | `contracts` | standard | quality |
 | `claim` | core | lifecycle |
@@ -75,6 +98,7 @@ This file is generated from `PM_COMMAND_CAPABILITY_CONTRACTS`. Do not edit it ma
 | `event` | full | automation |
 | `remind` | full | automation |
 | `help` | core | context |
+| `ops` | core | quality |
 | `completion-statuses` | internal | internal |
 | `completion-tags` | internal | internal |
 | `completion-types` | internal | internal |

package/docs/generated/FLAG_LEXICON_BUDGETS.md

@@ -33,6 +33,7 @@ This file is generated by `listPmFlagLexicon()`. Compatibility aliases do not co
 | `next` | context | 38 | 38 |
 | `history` | evidence | 35 | 35 |
 | `events` | evidence | 33 | 33 |
+| `history-attest` | evidence | 23 | 23 |
 | `history-redact` | evidence | 27 | 27 |
 | `history-repair` | evidence | 27 | 27 |
 | `history-compact` | evidence | 30 | 30 |
@@ -44,7 +45,7 @@ This file is generated by `listPmFlagLexicon()`. Compatibility aliases do not co
 | `restore` | intake | 23 | 23 |
 | `update` | lifecycle | 105 | 105 |
 | `update-many` | lifecycle | 146 | 146 |
-| `close` | lifecycle | 31 | 31 |
+| `close` | lifecycle | 32 | 32 |
 | `close-many` | lifecycle | 72 | 72 |
 | `delete` | lifecycle | 24 | 24 |
 | `append` | evidence | 25 | 25 |
@@ -65,8 +66,8 @@ This file is generated by `listPmFlagLexicon()`. Compatibility aliases do not co
 | `gc` | workspace | 22 | 22 |
 | `workspace` | workspace | 23 | 23 |
 | `contracts` | quality | 29 | 29 |
-| `claim` | lifecycle | 38 | 38 |
-| `release` | lifecycle | 23 | 23 |
+| `claim` | lifecycle | 39 | 39 |
+| `release` | lifecycle | 24 | 24 |
 | `start-task` | lifecycle | 23 | 23 |
 | `pause-task` | lifecycle | 23 | 23 |
 | `close-task` | lifecycle | 24 | 24 |
@@ -74,3 +75,25 @@ This file is generated by `listPmFlagLexicon()`. Compatibility aliases do not co
 | `event` | automation | 33 | 33 |
 | `remind` | automation | 29 | 29 |
 | `test-runs-worker` | internal | 25 | 25 |
+| `history attest` | evidence | 23 | 23 |
+| `history redact` | evidence | 27 | 27 |
+| `history repair` | evidence | 27 | 27 |
+| `history compact` | evidence | 30 | 30 |
+| `history activity` | context | 35 | 35 |
+| `history restore` | intake | 23 | 23 |
+| `context next` | context | 38 | 38 |
+| `context focus` | intake | 22 | 22 |
+| `ops stats` | context | 29 | 29 |
+| `ops health` | workspace | 36 | 36 |
+| `ops validate` | quality | 46 | 46 |
+| `ops gc` | workspace | 22 | 22 |
+| `ops telemetry` | workspace | 21 | 21 |
+| `ops eval` | context | 25 | 25 |
+| `ops test-all` | quality | 40 | 40 |
+| `history events` | evidence | 33 | 33 |
+| `update many` | lifecycle | 146 | 146 |
+| `close many` | lifecycle | 72 | 72 |
+| `close delete` | lifecycle | 24 | 24 |
+| `item copy` | intake | 24 | 24 |
+| `workspace merge` | workspace | 27 | 27 |
+| `item duplicates` | context | 25 | 25 |

package/docs/generated/REFUSAL_CLOSURE_CENSUS.md

@@ -11,7 +11,7 @@ Every catalog code is listed. An `uncovered` row is an explicit closure obligati
 - Uncovered error codes: 352
 - Coverage fraction: 0.051213
 - Closed-domain probes: 19
-- Grammar probes: 97
+- Grammar probes: 101
 
 | Error code | Canonical code | Disposition | Evidence kinds | Probe count |
 | --- | --- | --- | --- | --- |
@@ -211,7 +211,7 @@ Every catalog code is listed. An `uncovered` row is an explicit closure obligati
 | `missing_parameter_alias` | `missing_parameter_alias` | uncovered | none | 0 |
 | `missing_positive_execution_receipt` | `missing_positive_execution_receipt` | uncovered | none | 0 |
 | `missing_probe` | `missing_probe` | uncovered | none | 0 |
-| `missing_required_argument` | `missing_required_argument` | executable | grammar | 60 |
+| `missing_required_argument` | `missing_required_argument` | executable | grammar | 63 |
 | `missing_required_option` | `missing_required_option` | uncovered | none | 0 |
 | `missing_suggested_retry` | `missing_suggested_retry` | uncovered | none | 0 |
 | `missing_suggested_retry_args` | `missing_suggested_retry_args` | uncovered | none | 0 |
@@ -313,13 +313,13 @@ Every catalog code is listed. An `uncovered` row is an explicit closure obligati
 | `unknown_field` | `unknown_field` | uncovered | none | 0 |
 | `unknown_field_projection` | `unknown_field_projection` | executable | closed_domain | 10 |
 | `unknown_item_type` | `unknown_item_type` | uncovered | none | 0 |
-| `unknown_lifecycle_action` | `unknown_subcommand` | executable | grammar, owned_state | 11 |
+| `unknown_lifecycle_action` | `unknown_subcommand` | executable | grammar, owned_state | 12 |
 | `unknown_noun` | `unknown_noun` | uncovered | none | 0 |
 | `unknown_option` | `unknown_option` | executable | owned_state | 1 |
 | `unknown_plan_template` | `unknown_plan_template` | uncovered | none | 0 |
 | `unknown_provenance_dimension` | `unknown_provenance_dimension` | uncovered | none | 0 |
 | `unknown_status` | `unknown_status` | uncovered | none | 0 |
-| `unknown_subcommand` | `unknown_subcommand` | executable | grammar, owned_state | 11 |
+| `unknown_subcommand` | `unknown_subcommand` | executable | grammar, owned_state | 12 |
 | `unsafe_init_recovery` | `unsafe_init_recovery` | uncovered | none | 0 |
 | `unsupported_update_option` | `unsupported_update_option` | uncovered | none | 0 |
 | `validate_command_references_stale_pm_ids` | `validate_command_references_stale_pm_ids` | uncovered | none | 0 |

package/marketplace.json

@@ -6,14 +6,14 @@
   },
   "metadata": {
     "description": "Official marketplace for pm CLI — native git-based project management for Claude Code and AI coding agents.",
-    "version": "2026.9.9"
+    "version": "2026.9.11"
   },
   "plugins": [
     {
       "name": "pm-claude",
       "source": "./plugins/pm-claude",
       "description": "Native pm CLI integration for Claude Code — 28 MCP tools, 5 workflow skills, 14 slash commands, 4 subagents, hybrid TUI task tracking, session context injection, and coordination subagents for git-based project management without leaving Claude Code.",
-      "version": "2026.9.9",
+      "version": "2026.9.11",
       "author": {
         "name": "unbrained",
         "url": "https://github.com/unbraind/pm-cli"

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@unbrained/pm-cli",
-  "version": "2026.9.9",
+  "version": "2026.9.11",
   "description": "Git-native project management CLI for humans and agents.",
   "type": "module",
   "packageManager": "pnpm@11.10.0",
@@ -205,7 +205,7 @@
     "node": ">=22.18.0"
   },
   "dependencies": {
-    "@sentry/node": "10.73.0",
+    "@sentry/node": "10.74.0",
     "@toon-format/toon": "^4.1.1",
     "@types/node": ">=22",
     "commander": "^15.0.0",
@@ -218,7 +218,7 @@
   "devDependencies": {
     "@codspeed/vitest-plugin": "^5.7.1",
     "@eslint/js": "^10.0.1",
-    "@modelcontextprotocol/ext-apps": "1.7.5",
+    "@modelcontextprotocol/ext-apps": "2.0.0",
     "@sentry/cli": "^3.7.0",
     "@types/node": "^26.5.0",
     "@types/npm-package-arg": "^6.1.4",
@@ -230,7 +230,7 @@
     "fast-check": "^4.9.0",
     "github-slugger": "2.0.0",
     "greptile": "^3.5.2",
-    "jscpd": "^5.1.2",
+    "jscpd": "^5.2.0",
     "marked": "18.0.12",
     "parse5": "8.0.1",
     "tsx": "^4.23.13",

package/packages/pm-beads/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@unbrained/pm-beads",
-  "version": "2026.9.9",
+  "version": "2026.9.11",
   "private": true,
   "type": "module",
   "description": "First-party pm package for importing Beads JSONL records.",

package/packages/pm-calendar/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@unbrained/pm-calendar",
-  "version": "2026.9.9",
+  "version": "2026.9.11",
   "private": true,
   "type": "module",
   "description": "First-party pm package for calendar and agenda views.",

package/packages/pm-command-kit/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@unbrained/pm-command-kit",
-  "version": "2026.9.9",
+  "version": "2026.9.11",
   "private": true,
   "type": "module",
   "description": "First-party pm exemplar package for the commands capability: registerCommand, registerFlags, and registerParser.",

package/packages/pm-digital-twin/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@unbrained/pm-digital-twin",
-  "version": "2026.9.9",
+  "version": "2026.9.11",
   "private": true,
   "type": "module",
   "description": "Beyond-PM exemplar: a temporal production-facility digital twin built entirely on public pm SDK and extension primitives.",