@unbrained/pm-cli 2026.10.7 → 2026.10.9

package/docs/MERGE_SAFETY.md

@@ -74,7 +74,18 @@ Health and validation name `pm merge install` as the repair command for missing
 or drifted drivers. This upgrade behavior is tracked by
 [pm-rcjyft](../.agents/pm/issues/pm-rcjyft.toon).
 
-The installer publishes the shared `.gitattributes` fence only after the clone-local driver commands are configured. If the repository Git config is read-only or another Git process holds its lock, the command returns the stable `merge_git_config_unwritable` error with recovery guidance and leaves an absent fence absent. Use `pm merge install --dry-run --json` to inspect the contract in intentionally read-only workspaces.
+The installer publishes the shared `.gitattributes` fence only after the
+clone-local driver commands are configured. Matching definitions are read
+without rewriting Git configuration. Concurrent pm installers coordinate
+through a clone-local lock shared by its worktrees. Each required Git write
+waits up to five seconds for Git's native config-file lock, with capped backoff;
+it never removes another writer's lock. Persistent contention, malformed
+configuration, and permission failures return the stable
+`merge_git_config_unwritable` error with recovery guidance and leave an absent
+fence absent. This behavior is tracked by
+[pm-gh1424](../.agents/pm/issues/pm-gh1424.toon).
+Use `pm merge install --dry-run --json` to inspect the contract in
+intentionally read-only workspaces.
 
 ### Independent worktree runtimes
 
@@ -177,7 +188,20 @@ and `hash_only`, while the clone-local receipt remains `clone_local`. This lets
 a fresh-clone reviewer recover ordinary control-plane decisions without
 publishing titles, descriptions, custom statuses, or other potentially private
 content. When both copies exist the SDK deduplicates them and prefers the
-locally recoverable copy:
+locally recoverable values. After immutable provenance matches, durable
+reconciled state takes precedence over a stale clone-local pending copy only
+when verified item history contains a sealed `merge_reconcile` event with the
+same complete receipt summary and disposition. An absent, unreadable, invalid,
+unsealed, or mismatched audit keeps the receipt pending in memory; inspection
+rewrites neither receipt nor history. History is verified once per affected
+item in each receipt scan.
+Copy provenance includes normalized `requested_preference_applied`, so copies
+that disagree on whether preference participated cannot share lifecycle state
+even if history matches one copy. Inspection reports `copy_provenance_mismatch`,
+and settlement refuses before either receipt is written. Legacy omission uses
+the declared conflict policy's default participation value.
+A local reconciled copy paired with a pending durable copy remains pending,
+so an interrupted settlement can finish its durable write:
 
 ```bash
 pm merge report
@@ -249,18 +273,33 @@ does not recover the original private value.
 
 ## Receipts from an aborted rebase
 
-Tracked by [pm-466m0j](../.agents/pm/issues/pm-466m0j.toon). New receipts
-created during a rebase capture only its original commit and item blob in the
-typed `MergeReceiptOperation` contract. After aborting, run:
+Tracked by [pm-466m0j](../.agents/pm/issues/pm-466m0j.toon) and
+[pm-gh1405](../.agents/pm/issues/pm-gh1405.toon). New receipts created during a
+merge or rebase capture only its operation kind, original commit, and item blob
+in the typed `MergeReceiptOperation` contract. A plain merge captures these
+before Git publishes `MERGE_HEAD`: Git must supply its `GITHEAD_<incoming object
+ID>` driver environment signal, `HEAD` must equal `ORIG_HEAD`, and the
+driver's ours input must hash to the item blob at that commit. Missing or
+ambiguous coordinates are omitted. Matching origin references and bytes alone
+cannot identify a plain merge: cherry-pick and revert also invoke content
+drivers. Without Git's incoming-head signal, those receipts remain unresolved
+and cannot receive a plain-merge abandonment audit. Branch labels from the
+driver environment are never persisted. After aborting, run:
 
 ```bash
 pm merge reconcile --dry-run --json
-pm merge reconcile --message "Record restored original rebase state" --json
+pm merge reconcile --message "Record restored original Git state" --json
 ```
 
+SDK consumers that exhaustively handle `MergeReceiptOperation.kind` must
+accept both `rebase` and `merge`. Existing rebase coordinates and receipt
+version remain valid; no stored receipt migration is required.
+
 Settlement requires Git to have left every active merge/rebase/cherry-pick/revert
 operation, HEAD to match the original commit, and the item in HEAD, index, and
 working tree to match the original blob. The item history must already be clean.
+Requiring the original HEAD also rules out a new commit incorporating the
+abandoned merge's other branch.
 The history transaction rechecks the proof against its exact protected item
 snapshot. Apply appends an explicit `merge_reconcile` event with
 `abandoned_receipts` and the reason `original_git_state_restored`; it then marks
@@ -271,6 +310,22 @@ If receipt persistence fails after the audit commits, retry reuses the identical
 verified disposition and finishes the receipt writes without appending another
 audit event. An unrelated earlier audit does not satisfy this check.
 
+The driver-created `merge-receipts/<receipt-id>.json` sidecar can remain
+untracked after Git aborts. After reviewed settlement, commit that privacy-safe
+sidecar together with the item's new history audit. Reconciliation preserves
+the durable evidence for other worktrees instead of deleting the sidecar.
+
+Applied-merge settlement has the same retry contract, tracked by
+[pm-gh1390](../.agents/pm/issues/pm-gh1390.toon). The current item must still
+satisfy authoritative receipt proof; only an identical receipt context in a
+sealed event from reanchored, verified history suppresses a repeated provenance
+event. Matching unsealed legacy context receives a new sealed audit while its
+original entry remains intact. This also works with
+durable-only evidence in another worktree. Once that worktree commits the
+settled sidecar and history, a receiving worktree's stale local pending receipt
+cannot reopen it. A subsequent `pm merge reconcile` leaves all three files
+unchanged.
+
 Old receipts without operation coordinates remain pending for ordinary review.
 Tracked `merge-receipts/` sidecars are durable provenance and must remain tracked.
 Deleting or ignoring them would lose the evidence needed by other clones.

package/docs/PACKAGE_GATE_ACCEPTANCE.md

@@ -0,0 +1,56 @@
+# Faithful package acceptance
+
+Tracked by [pm-gh1391](../.agents/pm/issues/pm-gh1391.toon),
+[pm-aiqmgj](../.agents/pm/issues/pm-aiqmgj.toon), and
+[pm-dqej6b](../.agents/pm/issues/pm-dqej6b.toon), with scratch ancestry protection
+tracked by [pm-runner-ancestor-tracker](../.agents/pm/issues/pm-runner-ancestor-tracker.toon).
+
+Package tests that create their own disposable projects need an unset `PM_PATH`.
+Otherwise a nested `pm init` follows the inherited tracker override and writes
+outside the intended fixture. Use the shared SDK linked-test runner with a
+disposable source snapshot:
+
+```bash
+pm test <item-id> --add-json '{"command":"npm run release:check","pm_context_mode":"none","workspace_context_mode":"snapshot","timeout_seconds":900}'
+pm test <item-id> --run --progress
+```
+
+The same fields are supported by the SDK's `runTest` and MCP. See
+[Testing](TESTING.md) for trust acknowledgements, assertions and run receipts.
+
+Snapshots copy the current source files and keep root and nested `node_modules`
+at their original relative paths. A Git workspace additionally receives an
+independent clone of commit and tag objects, so release-tag checks and dependency
+resolution work together. The clone uses no shared objects or source hooks,
+does not inherit source-local Git configuration, and has no origin remote.
+The internal remote name is explicit even with a custom `clone.defaultRemoteName`.
+Its Git objects remain readable after the source checkout is removed.
+
+The working tree excludes tracker and generated build/report directories.
+Git objects contain repository history, including any historically tracked
+files; a snapshot is an execution-isolation boundary, not a redaction mechanism.
+Source aliases remain subject to containment checks. Installed dependency
+directories are shared, so dependency-mutating tests need a separate installation.
+Tests that depend on absolute checkout paths, source-local Git configuration,
+submodule configuration, or exact dirty-status output must declare those
+requirements separately. Cloning failures fail the linked run rather than
+silently certifying a partial Git identity.
+
+`PM_GLOBAL_PATH` remains isolated. `none` with a live source workspace and direct
+PM commands remains refused. Existing command provenance and clone-local trust
+checks still apply. The runner records the effective workspace and tracker
+context on each execution so a green linked receipt identifies its boundary.
+Repository acceptance also refuses scratch roots beneath any initialized
+ancestor tracker before allocating fixtures, including external roots and
+root-layout trackers. Choose a temporary hierarchy without workspace ancestry.
+
+The optional SQLite accelerator filters Node's exact experimental announcement
+only during synchronous native loading. Every other warning retains its original
+arguments, and normal warning delivery is restored immediately, including after
+a failed optional load. JSON refusals and clean mutation stderr therefore remain
+usable on Node 22 and Node 24 without disabling application diagnostics.
+
+The repository's scratch lifecycle keeps its original 15-second latency and
+3,000-token output limits. Vitest schedules it in a separate project after the
+parallel contract suite. Functional assertions and the all-source coverage
+denominator stay intact; a real latency regression still fails admission.

package/docs/PACKED_FIRST_RUN.md

@@ -1,50 +1,34 @@
 # Packed First-Run Acceptance
 
-Tracked by [pm-ygli86](../.agents/pm/tasks/pm-ygli86.toon),
-[pm-rcjyft](../.agents/pm/issues/pm-rcjyft.toon), and
-[pm-07m41m](../.agents/pm/issues/pm-07m41m.toon).
+Trackers: [pm-ygli86](../.agents/pm/tasks/pm-ygli86.toon),
+[pm-rcjyft](../.agents/pm/issues/pm-rcjyft.toon),
+[pm-07m41m](../.agents/pm/issues/pm-07m41m.toon),
+[pm-p5u6](../.agents/pm/chores/pm-p5u6.toon).
 
-The `Packed first run` CI matrix installs the same tarball globally into an
-isolated npm prefix on Ubuntu, macOS, and Windows, using Node 22.18.0 and Node 24.
-It executes the installed `pm` shim before passing the installed package directory
-to the acceptance harness:
+CI globally installs one tarball in isolated npm prefixes on Ubuntu/macOS/Windows
+with Node 22.18.0 and 24, runs the installed `pm` shim, then invokes:
 
 ```bash
 node scripts/release/packed-first-run.mjs /path/to/installed/@unbrained/pm-cli
 ```
 
-The harness extracts the first three commands from the installed README's
-`60 Second Example` section. It executes `init`, `create`, and `list` in a
-temporary Git workspace, requires nonempty output below 4,096 characters per
-command, and checks that the created item was persisted. Missing sections,
-reordered commands, unsupported shell expressions, and unbalanced quotes fail.
-Arguments are passed directly to the installed CLI without a shell.
-
-Two branches then append independent comments through that CLI. A real Git merge
-must preserve both comments and their history. The installed reconciliation and
-strict history verifier must succeed. The installed MCP server must complete an
-initialize round trip and advertise the installed package version. An additional
-mutation enables telemetry only against a loopback HTTP collector. The harness
-acknowledges detached delivery batches until it receives `command_finish`, then
-verifies the physical queue is empty and a successful flush is recorded.
-One 30-second deadline covers the entire collection, including incomplete request
-bodies; an initial `command_start` batch alone cannot satisfy acceptance.
-It removes inherited inline-flush and
-test-runner overrides so this exercises the real detached process. Other commands
-and MCP keep telemetry disabled; the install and workspace use isolated home
-and global tracker directories.
-
-MCP cleanup waits for process closure before removing its workspace. It allows
-five seconds after SIGTERM, then sends SIGKILL and allows five more seconds. If
-the child still does not close, the harness fails with captured diagnostics and
-retains that workspace rather than attempting removal while it is in use.
-
-The separate runtime-upgrade regression installs drivers through an absolute
-runtime symlink, removes the original runtime directory, retargets the symlink,
-and performs a real Git merge. It verifies the upgrade failure from GitHub #1248
-without altering any developer runtime or repository.
-
-This matrix proves the packed artifact's first-run behavior. Registry propagation,
-npm/Bun installed agent sessions, npx/bunx execution, production telemetry, and
-previous-release compatibility remain separate acceptance claims under the
-[release workflow](RELEASING.md).
+| Journey | Required observation |
+| --- | --- |
+| Installed README | Ordered init/create/list from `60 Second Example`; missing/reordered commands, unsupported expressions or unbalanced quotes fail. No shell execution. |
+| Persistence | Each command returns nonempty output below 4,096 characters; the created item exists. |
+| Branch merge | Independent comments survive a real Git merge; reconciliation and strict history verification succeed. |
+| MCP | Initialization advertises the installed version. |
+| Telemetry | A loopback collector receives detached `command_finish`; queue empties and successful flush persists. One 90-second deadline includes incomplete bodies; start alone cannot pass. |
+
+Detached delivery removes inherited inline/test overrides; other commands/MCP
+disable telemetry. Home/global roots are isolated. Interrupts stop stage admission
+and collection, waiting five seconds for disposal. CLI errors await actual closure.
+MCP waits five seconds after SIGTERM, then SIGKILL plus five more; failure retains
+storage/diagnostics. [Storage lifecycle](SDK_STORAGE_LIFECYCLE.md) defines ownership
+and abrupt-exit limits.
+
+A separate #1248 regression removes/retargets an owned runtime symlink and performs
+a real Git merge, preserving developer runtimes.
+
+Registry propagation, npm/Bun sessions, npx/bunx, production telemetry and previous
+compatibility have separate [release acceptance](BUILD_AND_RELEASE_ACCEPTANCE.md).

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.
 - [Agent Read and Test Receipts](AGENT_READ_AND_TEST_RECEIPTS.md) - JSON help provenance, linked-test persistence, and history diff continuation.
+- [Fact-preserving Agent Output](AGENT_OUTPUT_ENCODINGS.md) - lossless SDK table cells, measured token ratchets, count aliases, and whole-response context budgets.
 - [Agent Evidence Consistency](AGENT_EVIDENCE_CONSISTENCY.md) - literal annotations, concurrent history validation, and declared recovery help.
 - [Actionable Item-read Evidence](GET_READ_EVIDENCE.md) - declared blocker status, historical separation, and truthful schedule/artifact omission receipts.
 - [Command Reference](COMMANDS.md) - command families with examples and when to use each family.
@@ -43,6 +44,7 @@ pm guide release --json
 - [Configuration](CONFIGURATION.md) - settings, storage formats, output, search, validation, and environment variables.
 - [Semantic Batching and Retrieval Quality](SEARCH_QUALITY.md) - independent request bounds, execution receipts, and per-query quality floors.
 - [Testing](TESTING.md) - sandbox-safe local tests and linked-test orchestration.
+- [Faithful Package Acceptance](PACKAGE_GATE_ACCEPTANCE.md) - self-isolating package gates, independent Git snapshots, native diagnostics and isolated timing admission.
 - [Completion Portability and Bounded Replication Checks](VALIDATION_PORTABILITY.md) - literal Bash choices across versions and locales, and semantic Git diff collection.
 - [Build and Release Acceptance](BUILD_AND_RELEASE_ACCEPTANCE.md) - complete-build leases and cross-platform registry installation controls.
 - [Security Governance](SECURITY_GOVERNANCE.md) - vulnerability reporting, review discipline, property fuzzing, and OpenSSF limitations.
@@ -98,6 +100,7 @@ pm guide release --json
 - [Extension Lifecycle Contracts](EXTENSION_LIFECYCLE.md) - source identity, durable migrations, and scoped preflight ownership.
 - [Extension Author Contracts](EXTENSION_AUTHOR_CONTRACTS.md) - the stability guarantees and contract surface package authors build against.
 - [SDK](SDK.md) - public import surfaces and typed authoring examples.
+- [SDK Storage Lifecycle](SDK_STORAGE_LIFECYCLE.md) - existing-parent writes, background worker lifetimes, and temporary acceptance producers.
 - [SDK Item Creation and Recovery](SDK_CREATE_AND_RECOVERY.md) - typed deterministic conflicts, resolved identity, actionable refusals, and amount-limited producer cursors.
 - [Audited SDK Settings and Item Updates](SDK_AUDITED_MUTATIONS.md) - extension-owned settings changes, replay-safe previews, and full-item JSON annotation integrity.
 - [SDK execution and recovery contracts](SDK_EXECUTION_CONTRACTS.md): schema-driven scheduling, handoff, and command recovery.

package/docs/SDK_AUDITED_MUTATIONS.md

@@ -4,6 +4,24 @@ The extension settings contract is tracked by
 [pm-wtqltn](../.agents/pm/issues/pm-wtqltn.toon). Full-item JSON annotation
 integrity is tracked by [pm-2589e6](../.agents/pm/issues/pm-2589e6.toon).
 Canonical previews are tracked by [pm-2sef82](../.agents/pm/features/pm-2sef82.toon).
+Preview path refusals are tracked by
+[pm-preview-path-refusal](../.agents/pm/issues/pm-preview-path-refusal.toon).
+
+## Transaction preview storage
+
+Item mutation and completion previews inspect a staged copy of the configured
+tracker storage without changing source items or bootstrapping source schemas.
+Linked entries, special files and directories configured as files are refused
+with `transaction_preview_non_regular_file` (CLI exit `2`). SDK callers receive
+a `PmCliError` with the same code and repair guidance in `context.nextSteps`.
+The producer diagnostic omits discovered filesystem paths. Inspect the configured
+settings, schema, session and item storage, restore the intended regular files and directories,
+then retry the original dry run.
+
+Entry and opened-descriptor checks enforce the same contract. Persistent native
+filesystem failures, including missing link targets and permission errors, keep
+their original codes. These checks require stable, trusted ancestors; they do
+not guarantee protection against hostile concurrent path redirection.
 
 ## Extension settings
 

package/docs/SDK_STORAGE_LIFECYCLE.md

@@ -0,0 +1,35 @@
+# SDK Storage Lifecycle
+
+Tracked by [pm-p5u6](../.agents/pm/chores/pm-p5u6.toon).
+
+Detached telemetry reads existing settings without scaffolding schemas/identity.
+Locks, queue/state rewrites and event/OTLP completion preserve owner-removed
+storage. Delivery stays best effort/nonblocking; foreground defaults create parents.
+
+```typescript
+import { acquireLock, writeFileAtomic } from "@unbrained/pm-cli/sdk";
+
+const policy = { createParentDirectories: false };
+const release = await acquireLock(root, "job", 60, "worker", false, true, 5000, policy);
+try {
+  await writeFileAtomic(resultPath, serializedResult, policy);
+} finally {
+  await release();
+}
+```
+
+Owners initialize lock/result parents; absence fails without recreation. The
+policy cannot pin identity or prevent symlink/replacement races. Extension lock
+overrides own their lifecycle.
+
+Async scripts use `registerTempOperation`: signal children, check after
+uncancellable SDK work, `finish` after finally disposal. Interrupts close admission
+and await completion; timeout retains evidence. Sync scripts use
+`registerTempCleanup`. Normal failure, SIGINT/SIGTERM (130/143), explicit retention
+and caller-owned roots are covered; unrelated roots survive. Abrupt exits retain
+async work. SIGKILL/power loss/Windows forced termination cannot run handlers.
+Unix tests cover signals; Windows covers callbacks/normal exit.
+
+Real storage, HTTP/OTLP, Git and subprocess regressions complement
+[build/registry acceptance](BUILD_AND_RELEASE_ACCEPTANCE.md) and
+[packed first run](PACKED_FIRST_RUN.md).

package/docs/TESTING.md

@@ -57,8 +57,12 @@ fixtures must never create production incidents from a developer host.
 
 Temporary directories must live outside the checkout and outside any ancestor
 workspace with initialized tracker data. The runner rejects a checkout-local
-temporary root, including a symlink alias, before starting build or test
-processes ([pm-bukwmy](../.agents/pm/issues/pm-bukwmy.toon)). If the default
+temporary root and every initialized standard or root-layout ancestor tracker,
+including physical symlink aliases, before allocating fixtures or starting build
+or test processes ([pm-bukwmy](../.agents/pm/issues/pm-bukwmy.toon),
+[pm-runner-ancestor-tracker](../.agents/pm/issues/pm-runner-ancestor-tracker.toon)).
+Unrelated valid settings files remain admissible; unreadable or invalid ancestor
+settings refuse ancestry certification. If the default
 temporary filesystem is full, set `TMPDIR` (or `TEMP`/`TMP` on Windows) to an
 existing isolated scratch directory; an ignored directory inside the repository
 is not isolated. Filesystem fixtures must honor `node:os`'s `tmpdir()` and remove
@@ -549,7 +553,11 @@ pm test <item-id> --run --workspace-context snapshot --override-linked-workspace
   copy, and binds its `.agents/pm` path to the selected temporary tracker.
   `.git`, `.agents`, coverage output, and common cache directories are excluded
   at every directory depth, with reserved names matched case-insensitively for
-  portable admission. Each existing root or nested `node_modules`
+  portable admission. Git sources receive an independent commit/tag object store
+  with fresh configuration, no source hooks, and no origin remote. Repository
+  history remains available; this is execution isolation, not history redaction.
+  See [Faithful package acceptance](PACKAGE_GATE_ACCEPTANCE.md) for limits.
+  Each existing root or nested `node_modules`
   directory is linked at its original relative path, including installations
   already represented by directory symlinks. This preserves independent
   monorepo dependency versions without copying dependency trees. Dependency

package/docs/generated/REFUSAL_CLOSURE_CENSUS.md

@@ -4,12 +4,12 @@ Tracker: `pm-f05lsg`.
 
 Every catalog code is listed. An `uncovered` row is an explicit closure obligation, never an omission or implied approval.
 
-- Catalog error codes: 395
+- Catalog error codes: 396
 - Executable error codes: 19
 - Executable-code ratchet floor: 18
 - Required executable canonical codes: `bulk_ids_input_empty`, `bulk_ids_input_missing_path`, `bulk_ids_input_unreadable`, `invalid_argument_value`, `manifest_unknown_key`, `missing_lifecycle_target`, `missing_required_argument`, `no_version_bounds_declared`, `projection_options_mutually_exclusive`, `tracker_not_initialized`, `tracker_root_missing`, `tracker_root_not_directory`, `tracker_root_unreadable`, `unknown_context_intent`, `unknown_field_projection`, `unknown_option`, `unknown_subcommand`
-- Uncovered error codes: 376
-- Coverage fraction: 0.048101
+- Uncovered error codes: 377
+- Coverage fraction: 0.047980
 - Closed-domain probes: 19
 - Grammar probes: 117
 
@@ -324,6 +324,7 @@ Every catalog code is listed. An `uncovered` row is an explicit closure obligati
 | `tracker_root_not_directory` | `tracker_root_not_directory` | executable | owned_state | 1 |
 | `tracker_root_unreadable` | `tracker_root_unreadable` | executable | owned_state | 1 |
 | `transaction_preview_external_schema` | `transaction_preview_external_schema` | uncovered | none | 0 |
+| `transaction_preview_non_regular_file` | `transaction_preview_non_regular_file` | uncovered | none | 0 |
 | `transaction_preview_snapshot_changed` | `transaction_preview_snapshot_changed` | uncovered | none | 0 |
 | `type_duplicate` | `type_duplicate` | uncovered | none | 0 |
 | `type_invalid` | `type_invalid` | uncovered | none | 0 |

package/marketplace.json

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

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@unbrained/pm-cli",
-  "version": "2026.10.7",
+  "version": "2026.10.9",
   "description": "Git-native project management CLI for humans and agents.",
   "type": "module",
   "packageManager": "pnpm@11.10.0",

package/packages/pm-beads/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@unbrained/pm-beads",
-  "version": "2026.10.7",
+  "version": "2026.10.9",
   "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.10.7",
+  "version": "2026.10.9",
   "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.10.7",
+  "version": "2026.10.9",
   "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.10.7",
+  "version": "2026.10.9",
   "private": true,
   "type": "module",
   "description": "Beyond-PM exemplar: a temporal production-facility digital twin built entirely on public pm SDK and extension primitives.",

package/packages/pm-governance-audit/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@unbrained/pm-governance-audit",
-  "version": "2026.10.7",
+  "version": "2026.10.9",
   "private": true,
   "type": "module",
   "description": "First-party pm package for governance audit and normalization workflows.",

package/packages/pm-guide-shell/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@unbrained/pm-guide-shell",
-  "version": "2026.10.7",
+  "version": "2026.10.9",
   "private": true,
   "type": "module",
   "description": "First-party pm package for guide and shell completion workflows.",

package/packages/pm-kanban/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@unbrained/pm-kanban",
-  "version": "2026.10.7",
+  "version": "2026.10.9",
   "private": true,
   "type": "module",
   "description": "First-party pm archetype package: a complete Kanban continuous-flow profile built on public SDK primitives.",

package/packages/pm-lifecycle-hooks/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@unbrained/pm-lifecycle-hooks",
-  "version": "2026.10.7",
+  "version": "2026.10.9",
   "private": true,
   "type": "module",
   "description": "First-party pm package demonstrating safe lifecycle hook registration.",

package/packages/pm-linked-test-adapters/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@unbrained/pm-linked-test-adapters",
-  "version": "2026.10.7",
+  "version": "2026.10.9",
   "private": true,
   "type": "module",
   "description": "First-party pm package for optional linked-test run management adapters and reporters.",

package/packages/pm-search-advanced/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@unbrained/pm-search-advanced",
-  "version": "2026.10.7",
+  "version": "2026.10.9",
   "private": true,
   "type": "module",
   "description": "First-party pm package for semantic, hybrid, and reindex search workflows.",

package/packages/pm-templates/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@unbrained/pm-templates",
-  "version": "2026.10.7",
+  "version": "2026.10.9",
   "private": true,
   "type": "module",
   "description": "First-party pm package for reusable create templates.",

package/packages/pm-todos/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@unbrained/pm-todos",
-  "version": "2026.10.7",
+  "version": "2026.10.9",
   "private": true,
   "type": "module",
   "description": "First-party pm package for Todo markdown import and export.",

package/packages/pm-vcs/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@unbrained/pm-vcs-sdk-exemplar",
-  "version": "2026.10.7",
+  "version": "2026.10.9",
   "private": true,
   "type": "module",
   "description": "Beyond-PM exemplar: a VCS-style changeset workflow built entirely on public pm SDK and extension primitives.",

package/plugins/pm-claude/.claude-plugin/plugin.json

@@ -3,7 +3,7 @@
   "name": "pm-claude",
   "displayName": "pm CLI",
   "description": "Native pm CLI integration for Claude Code — 32 MCP tools, 14 skills with slash invocations, 4 subagents (coordinator, delivery-chain, triage, verification), hybrid TUI task tracking (pm as persistent store + Claude Code task panel as live view), session context injection, and full git-based project management without leaving Claude Code.",
-  "version": "2026.10.7",
+  "version": "2026.10.9",
   "author": {
     "name": "unbrained",
     "url": "https://github.com/unbraind/pm-cli"

package/plugins/pm-claude/package.json

@@ -2,8 +2,8 @@
   "name": "pm-claude-runtime",
   "private": true,
   "type": "module",
-  "version": "2026.10.7",
+  "version": "2026.10.9",
   "dependencies": {
-    "@unbrained/pm-cli": "2026.10.7"
+    "@unbrained/pm-cli": "2026.10.9"
   }
 }

package/plugins/pm-codex/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "pm-codex",
-  "version": "2026.10.7",
+  "version": "2026.10.9",
   "description": "Native Codex integration for pm-cli with bundled MCP tools, skills, commands, and agent workflows.",
   "author": {
     "name": "unbrained",

package/plugins/pm-codex/package.json

@@ -2,8 +2,8 @@
   "name": "pm-codex-runtime",
   "private": true,
   "type": "module",
-  "version": "2026.10.7",
+  "version": "2026.10.9",
   "dependencies": {
-    "@unbrained/pm-cli": "2026.10.7"
+    "@unbrained/pm-cli": "2026.10.9"
   }
 }

package/plugins/pm-codex/plugin.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json",
   "name": "pm-codex",
-  "version": "2026.10.7",
+  "version": "2026.10.9",
   "description": "Repository-native project context workflows and a version-pinned pm MCP server for Codex.",
   "author": {
     "name": "unbrained",

package/runtime-dependencies.json

@@ -1,12 +1,12 @@
 {
   "name": "@unbrained/pm-cli",
-  "version": "2026.10.7",
+  "version": "2026.10.9",
   "lockfileVersion": 3,
   "requires": true,
   "packages": {
     "": {
       "name": "@unbrained/pm-cli",
-      "version": "2026.10.7",
+      "version": "2026.10.9",
       "dependencies": {
         "@sentry/node": "10.75.1",
         "@toon-format/toon": "^4.1.1",