@unbrained/pm-cli 2026.10.7 → 2026.10.8

package/docs/BUILD_AND_RELEASE_ACCEPTANCE.md

@@ -1,115 +1,51 @@
 # Build generations and registry acceptance
 
-Tracked by [pm-cxc4jc](../.agents/pm/tasks/pm-cxc4jc.toon) and
-[pm-ygli86](../.agents/pm/tasks/pm-ygli86.toon). Ownership recovery and temporary
-workspace lifecycle follow-ups are
-[pm-63i8nr](../.agents/pm/tasks/pm-63i8nr.toon) and
+Trackers: [pm-cxc4jc](../.agents/pm/tasks/pm-cxc4jc.toon),
+[pm-ygli86](../.agents/pm/tasks/pm-ygli86.toon),
+[pm-63i8nr](../.agents/pm/tasks/pm-63i8nr.toon),
 [pm-p5u6](../.agents/pm/chores/pm-p5u6.toon).
 
-## Complete build ownership
+## Build ownership
 
-`pnpm build` owns one checkout-local lease from build-cache preparation through
-TypeScript compilation, bundling, and finalization. The sandboxed test runner
-uses the same lease for the entire test and coverage session. A second producer
-or consumer waits up to twenty minutes instead of reading partially rewritten
-JavaScript. The lease is under `.cache/build-lease`; its owner receipt records a
-process identifier and an opaque inheritance token.
+Build/test/coverage sessions own `.cache/build-lease` through completion;
+other producers/consumers wait twenty minutes. Nested readers inherit a verified
+PID/token receipt; nested builds require independent workspaces. Direct stages
+and arbitrary `dist` reads bypass this protocol.
 
-Nested read-only test runners inherit the verified live-owner receipt. Starting
-a build inside a test session is refused: rebuilding shared artifacts while
-other test workers consume them would violate the generation boundary. Fixtures
-that exercise the build orchestrator must use independent temporary workspaces.
+Leases never expire or get stolen. Two matching reads proving PID absence fail
+promptly with recovery guidance. Missing/malformed/changing/ambiguous receipts
+use the timeout; PID reuse is ambiguous. Inspect owner and children before
+abandoned-lease removal. Failed builds leave `.cache/build-incomplete`; prebuilt
+tests refuse it until a successful build.
 
-The lease never expires based on its age and is never automatically stolen.
-While waiting, the runner probes the recorded owner's process identifier. If
-the process is definitively absent and a second read confirms the same owner,
-it fails promptly with the receipt path and recovery instructions. Missing,
-malformed, changing, and permission-ambiguous receipts remain protected and use
-the ordinary acquisition timeout. PID reuse can make a departed owner appear
-live; the probe is a conservative diagnostic, not proof of process identity.
-After an interrupted process, inspect the owner and its children before removing
-an abandoned lease. A failed build leaves `.cache/build-incomplete`; prebuilt
-tests refuse that generation until a successful `pnpm build` clears the marker.
-Direct invocations of individual build stages or arbitrary reads of `dist` do
-not participate in this protocol. Use the build and test entrypoints for
-concurrent validation.
+Interrupts stop the child and stage admission, allowing five seconds for
+settlement, lease release and cleanup; unsettled children retain storage.
+Subprocess tests cover build/prebuilt paths and installer exits bypassing
+`finally`. [Storage lifecycle](SDK_STORAGE_LIFECYCLE.md) defines retention and
+platform limits.
 
-## Owned temporary workspaces
+## Registry acceptance
 
-Package smoke, external-package smoke, package-first dogfood, contract snapshots,
-plugin MCP smoke, and the sandboxed test runner register their temporary roots
-with the shared lifecycle helper. Release preparation, installed-agent and
-published-package verification, compatibility checks, isolated regression
-controls, context evaluation, intent calibration, refusal probes, and the point
-and context read benchmarks also register their owned roots. Normal completion
-releases the registration after cleanup. Synchronous
-workspaces also clean on process exit, including uncaught failure. SIGINT and
-SIGTERM run registered cleanup before returning exit codes 130 and 143.
+Release publishes once, chooses the registry's closest older calendar version
+and runs the same eleven-step session against control then candidate in separate
+roots. Linux/macOS/Windows cover npm local/global and Bun local. Installed CLI/SDK
+and selected runtimes have two-minute step deadlines, bounded output and token
+receipts. Synthetic telemetry/external reporting are disabled.
 
-An asynchronous producer must provide bounded shutdown. The plugin harness
-waits for its MCP child to close before removing its workspace; shutdown failure
-retains the directory and reports its path. An abrupt exit cannot await that
-shutdown, so it also retains asynchronous workspaces. Explicit keep-temp modes
-do not register cleanup. No cleanup scans or deletes unrelated temporary roots.
+Control failure indicates harness/environment problems; candidate-only failure
+requires regression investigation. Both block advertisement, which requires every
+matrix leg. Artifacts name manager/step. Immutable versions are never republished;
+exact-tag recovery retains the reviewed control selector. Parent deadlines cover
+preparation and publish/verify/advertise.
 
-The test runner stops its active build or test child on interruption, closes
-admission to later stages, and waits up to five seconds for the runner to settle.
-That wait includes release of its build lease and ordinary cleanup. If the child
-does not stop, the workspace is retained and its location is reported. A signal
-must never remove files still being used by a test process. Real subprocess
-regressions exercise both build-enabled and prebuilt execution, alongside
-installer failures that call `process.exit` and therefore bypass `finally`.
-
-Package-first dogfood disables telemetry for its synthetic child commands so
-detached flush workers cannot recreate the workspace after cleanup. Dedicated
-telemetry acceptance and the live Sentry/telemetry gate verify delivery.
-
-Release-note integration fixtures own their changelog, generator location, and
-Git lookup directory. Both a dated-only changelog and an Unreleased section are
-tested against the same real over-budget tracker. Release preparation can
-therefore regenerate the checkout changelog without changing test inputs.
-
-These handlers cannot run after SIGKILL, power loss, or Windows forced process
-termination. Native signal acceptance runs on Unix; callback and normal-exit
-contracts also run on Windows. The remaining script-wide migration stays tracked
-by pm-p5u6 rather than treating these covered entrypoints as complete adoption.
-
-## Published candidate and control
-
-The Release workflow publishes npm artifacts once, verifies executors, and
-selects the closest older calendar version from the public registry inventory.
-It then runs the same eleven-step agent session against the control first and
-the candidate second in independent temporary installation roots.
-
-The matrix covers Linux, macOS, and Windows with npm local, npm global, and Bun
-local installations. Each session initializes, orients, creates, claims,
-annotates, links evidence, closes, validates, reads the closed item and context,
-and verifies a complete corpus read through the installed public SDK. Each
-subprocess has a two-minute deadline; command output has per-step bounds and the
-report records estimated token cost. Telemetry and external error reporting are
-disabled in these acceptance workspaces.
-
-GitHub release advertisement is a separate job that depends on every matrix
-leg succeeding. A failed control identifies a harness or environment problem;
-a passing control followed by a failing candidate identifies a candidate
-regression to investigate. Neither failure permits advertisement. Reports are
-retained as workflow artifacts; failures also name the manager and failing step.
-Existing npm versions are never republished during exact-tag recovery.
-
-The prepublication artifact gate accepts both npm's array report and npm 12's
-package-keyed report. It requires exactly one artifact, validates keyed package
-identity, and applies the same file, source-map, and size limits to either shape.
-Exact-tag recovery preserves the reviewed control selector before checking out
-older unpublished source. The automatic-release parent budgets the complete
-publish, acceptance, and advertisement sequence plus its preparation work.
-
-Run the same comparison locally:
+The artifact gate validates one npm array/keyed receipt, identity and size/file/map
+limits. Release-note fixtures own generator/changelog/Git roots, isolating
+dated/Unreleased over-budget cases from checkout regeneration.
 
 ```bash
-npm run release:verify-installed-agent -- --version 2026.9.16 --previous-version 2026.9.15 --manager npm --global --json
-npm run release:verify-installed-agent -- --version 2026.9.16 --previous-version 2026.9.15 --manager bun --json
+npm run release:verify-installed-agent -- --version "$CANDIDATE" --previous-version "$CONTROL" --manager npm --global --json
+npm run release:verify-installed-agent -- --version "$CANDIDATE" --previous-version "$CONTROL" --manager bun --json
 ```
 
-Use `npm run` on Windows so the verifier receives the actual npm JavaScript
-entrypoint. CLI and SDK execution use the installed package and the selected
-runtime rather than assuming shell shim names.
+Set both versions. Windows `npm run` supplies npm's JavaScript entrypoint.
+See [packed first run](PACKED_FIRST_RUN.md) and [release policy](RELEASING.md).

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/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

@@ -98,6 +98,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/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.8",
   "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.8",
       "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.8",
   "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.8",
   "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.8",
   "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.8",
   "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.8",
   "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.8",
   "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.8",
   "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.8",
   "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.8",
   "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.8",
   "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.8",
   "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.8",
   "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.8",
   "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.8",
   "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.8",
   "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.8",
   "dependencies": {
-    "@unbrained/pm-cli": "2026.10.7"
+    "@unbrained/pm-cli": "2026.10.8"
   }
 }

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

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