@unbrained/pm-cli 2026.9.17 → 2026.9.19

package/docs/PERFORMANCE.md

@@ -135,3 +135,40 @@ Review the report and budget diff together. Before a refresh, compare the delive
 ## Startup and observability
 
 Sentry is loaded only when an error-reporting path actually initializes it. Disabled and normal successful commands do not resolve or compile the `@sentry/node` → OpenTelemetry → Undici graph. The loader uses the package's supported CommonJS export after the opt-out gate, preserving the repo-wide ban on dynamic/inline imports while keeping enabled capture, sanitization, and flush behavior intact.
+
+## Invocation timing
+
+Tracked by [pm-ag9nka](../.agents/pm/issues/pm-ag9nka.toon).
+
+Use `pm --profile list --limit 5` to print diagnostics on stderr while retaining
+normal stdout (including JSON). Every executable invocation with `--profile`
+emits one final receipt on normal process drain, including help, version, and
+handled refusals:
+
+```text
+profile:command=list took_ms=20
+profile:invocation total_ms=324.125 scope=process_start_to_output_drain command_took_ms_scope=handler
+```
+
+`total_ms` uses monotonic runtime uptime, starting before module initialization
+and ending after pending command output and event-loop work drain. It includes
+bootstrap, settings/schema and extension loading, dispatch, rendering, and
+foreground cleanup. Existing `profile:command` records retain their compatible
+`took_ms` field; `command_took_ms_scope=handler` explicitly labels those narrower
+spans. Extension discovery timing is another component, never an invocation
+total. Components may overlap and must not be added to the total.
+
+The total excludes parent-side scheduling/spawn, final OS teardown, and remote
+telemetry delivery after a detached flush. A forcibly terminated process may
+never reach the drain callback. In-process SDK calls do not emit a process-total
+receipt: their host owns the lifetime. `--profile` after the `--` positional
+terminator does not enable the receipt.
+
+The real-process regression compares the reported total against external wall
+time across query, mutation, configuration, schema, health, discovery, and
+refusal paths. It permits parent/teardown overhead of the greater of 250 ms or
+25% of external wall time, and no more than 5 ms of clock rounding above it.
+This is an instrument agreement tolerance, not a performance budget. Existing
+transport/scale gates retain external end-to-end process wall time and their
+unchanged stricter regression budgets; never gate invocation latency on handler
+`took_ms`.

package/docs/README.md

@@ -39,6 +39,7 @@ pm guide release --json
 - [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.
+- [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.
 - [Architecture](ARCHITECTURE.md) - contributor internals: storage, mutation flow, search, extensions, and command contracts.
 - [Noun–Verb CLI Grammar](CLI_GRAMMAR.md) - accepted command architecture, exhaustive destination census, hidden aliases, and the surface-growth gate.
@@ -53,6 +54,7 @@ pm guide release --json
 - [MCP Remote Transport, Authorization, and Migration](MCP_REMOTE_TRANSPORT_SECURITY.md) - Streamable HTTP operation, subscriptions, OAuth and trace boundaries, threat model, and deprecated-feature ratchet.
 - [SDK Artifact Output Contracts](SDK_ARTIFACT_OUTPUT.md) - clean stdout/file exporter channels, bounded receipts, binary-safe delivery, and shared NDJSON terminal framing.
 - [Context Relevance and Packing](CONTEXT_RELEVANCE.md) - shared CLI/SDK signals, derived-store provenance, ranking explanations, and token budgets.
+- [Next-work Selection Budgets](NEXT_SELECTION_BUDGETS.md) - bounded executable recommendations, omission receipts, and graded 10k/100k context verification.
 - [Context Algorithm Portfolio](CONTEXT_ALGORITHM_PORTFOLIO.md) - stable proposal slugs, historical aliases, individual owners, cognitive compositions, and experiment gates.
 - [Output Projection and Omission Contracts](OUTPUT_PROJECTION_CONTRACTS.md) - explicit withheld-field receipts, mode-paired row keys, and completion resolver outcomes.
 - [Output Token Accounting](OUTPUT_TOKEN_ACCOUNTING.md) - opt-in CLI/MCP byte attribution, bounded receipt overhead, and release-level tokens-per-task baselines.

package/docs/READ_OUTPUT_CONTRACTS.md

@@ -1,6 +1,6 @@
 # Universal Read Output Contracts
 
-Tracker references: [pm-hb7ug8](../.agents/pm/features/pm-hb7ug8.toon), [pm-cxr0jb](../.agents/pm/features/pm-cxr0jb.toon), [pm-hid9g1](../.agents/pm/features/pm-hid9g1.toon), [pm-h8tpeh](../.agents/pm/features/pm-h8tpeh.toon), [pm-5t33or](../.agents/pm/features/pm-5t33or.toon), [pm-wv47pf](../.agents/pm/issues/pm-wv47pf.toon), [pm-srns](../.agents/pm/issues/pm-srns.toon), [pm-sb0tns](../.agents/pm/issues/pm-sb0tns.toon), [pm-gjjurs](../.agents/pm/issues/pm-gjjurs.toon), [pm-eugaqy](../.agents/pm/issues/pm-eugaqy.toon), [pm-jt8aa2](../.agents/pm/issues/pm-jt8aa2.toon), [pm-kyjdne](../.agents/pm/issues/pm-kyjdne.toon), [pm-8nev0o](../.agents/pm/issues/pm-8nev0o.toon), [pm-oahhyc](../.agents/pm/issues/pm-oahhyc.toon), [pm-q4isdq](../.agents/pm/issues/pm-q4isdq.toon), [pm-e5gl05](../.agents/pm/issues/pm-e5gl05.toon), [pm-cha95z](../.agents/pm/tasks/pm-cha95z.toon), [pm-2qvq7a](../.agents/pm/issues/pm-2qvq7a.toon), and [pm-xam9bt](../.agents/pm/issues/pm-xam9bt.toon).
+Tracker references: [pm-15yuly](../.agents/pm/issues/pm-15yuly.toon), [pm-g8oh0f](../.agents/pm/issues/pm-g8oh0f.toon), [pm-hb7ug8](../.agents/pm/features/pm-hb7ug8.toon), [pm-cxr0jb](../.agents/pm/features/pm-cxr0jb.toon), [pm-hid9g1](../.agents/pm/features/pm-hid9g1.toon), [pm-h8tpeh](../.agents/pm/features/pm-h8tpeh.toon), [pm-5t33or](../.agents/pm/features/pm-5t33or.toon), [pm-wv47pf](../.agents/pm/issues/pm-wv47pf.toon), [pm-srns](../.agents/pm/issues/pm-srns.toon), [pm-sb0tns](../.agents/pm/issues/pm-sb0tns.toon), [pm-gjjurs](../.agents/pm/issues/pm-gjjurs.toon), [pm-eugaqy](../.agents/pm/issues/pm-eugaqy.toon), [pm-jt8aa2](../.agents/pm/issues/pm-jt8aa2.toon), [pm-kyjdne](../.agents/pm/issues/pm-kyjdne.toon), [pm-8nev0o](../.agents/pm/issues/pm-8nev0o.toon), [pm-oahhyc](../.agents/pm/issues/pm-oahhyc.toon), [pm-q4isdq](../.agents/pm/issues/pm-q4isdq.toon), [pm-e5gl05](../.agents/pm/issues/pm-e5gl05.toon), [pm-cha95z](../.agents/pm/tasks/pm-cha95z.toon), [pm-2qvq7a](../.agents/pm/issues/pm-2qvq7a.toon), and [pm-xam9bt](../.agents/pm/issues/pm-xam9bt.toon).
 
 ## Agent Quick Context
 
@@ -165,7 +165,7 @@ pm stats --output-row-contract
 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.
+Canonical amount, encoding, and cost controls that leave an already-fitting result unchanged do not add a `read_output` receipt. Explicit include projections, sessions, continuations, and `--output-row-contract` retain the detailed receipt. Every shaped or budget-compacted 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
@@ -178,7 +178,11 @@ 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.
+added. Each selected collection uses a measured prefix search instead of irreversible
+halving, retaining the largest prefix that fits with the other collections held
+fixed. `applied_limit` and both continuation forms follow the retained item count.
+A complete page and a truncated page have different mandatory metadata costs;
+row counts across that boundary are not an unconditional monotonicity guarantee. 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
@@ -188,7 +192,7 @@ rows; it can never leave the packer's earlier inclusions marked as served.
 `PmClient` finalizes the receipt before resolving, while the CLI finalizes it
 from the exact active result passed to telemetry and after-command hooks.
 
-When rows are dropped to satisfy a ceiling, the result also carries `output_budget_truncation`, naming the binding budget and its source, any explicitly requested dimension the budget overrode, every compacted collection path, and executable CLI/SDK/MCP recovery options — a default ceiling can override an explicit `--output-limit unbounded`, and that override is reported rather than silent. If a producer supplied an opaque item-page cursor, compaction rebases it to the last row actually returned and reports `continuation_cursor_rebased: true`; following the cursor therefore cannot skip rows removed from the middle of a producer page. If no useful content can fit, `PmReadOutputBudgetExceeded` provides a discriminated omission result, a compact `{ outputBudget: "unbounded" }` recovery object, and `omitted_result_estimated_tokens`, the last useful-result estimate before omission; use `isReadOutputBudgetExceeded` before accessing result-specific fields. Universal controls are rejected on mutation commands and on the mutation mode of hybrid commands such as `comments`, `notes`, `files`, and `docs`.
+When rows are dropped to satisfy a ceiling, the result also carries `output_budget_truncation`, naming the binding budget and its source, any explicitly requested dimension the budget overrode, every compacted collection path, and executable CLI/SDK/MCP recovery options — a default ceiling can override an explicit `--output-limit unbounded`, and that override is reported rather than silent. If a producer supplied an opaque item-page cursor, compaction rebases it to the last row actually returned and reports `continuation_cursor_rebased: true`; following the cursor therefore cannot skip rows removed from the middle of a producer page. If no useful content can fit, `PmReadOutputBudgetExceeded` provides a discriminated omission result, a compact `{ outputBudget: "unbounded" }` recovery object, and `omitted_result_estimated_tokens`, the last useful-result estimate before omission; use `isReadOutputBudgetExceeded` before accessing result-specific fields. The encoding control `--output-format <toon|json>` also applies to mutation envelopes, including the mutation modes of `comments`, `notes`, `files`, and `docs`. Other universal read controls remain rejected before mutation execution. `--json` remains supported.
 
 Cursor recovery carries the opaque value once in `recovery.cursor` and declares
 the accepting `cli`, `sdk`, and `mcp` binding beside it. This avoids

package/docs/SDK_AGENT_SESSION_CONTEXT.md

@@ -7,7 +7,8 @@ Tracker references: [pm-9wbiye](../.agents/pm/issues/pm-9wbiye.toon),
 [pm-eq9dlw](../.agents/pm/issues/pm-eq9dlw.toon), and
 [pm-lu6sca](../.agents/pm/features/pm-lu6sca.toon), plus
 [pm-5q8wa0](../.agents/pm/issues/pm-5q8wa0.toon) and
-[pm-c0lrdm](../.agents/pm/features/pm-c0lrdm.toon).
+[pm-c0lrdm](../.agents/pm/features/pm-c0lrdm.toon) and
+[pm-4f1l7f](../.agents/pm/issues/pm-4f1l7f.toon).
 
 Project management is context management. The public SDK therefore carries a
 session's purpose and episode boundary through the same immutable history that
@@ -129,8 +130,8 @@ public SDK exports for custom hosts.
 the bounded built-in resolver. It never contains environment values, session
 paths, prompts, or file contents.
 
-New mutation history records failed or explicitly unavailable configured
-resolver outcomes under `context.agent_provenance_outcomes`; dimensions with
+New mutation history records successful probes, failed probes, and explicitly
+unavailable configured resolver outcomes under `context.agent_provenance_outcomes`; dimensions with
 no configured resolver retain the compact legacy-compatible null projection.
 A resolver is only counted as
 attempted when its required input belongs to the detected harness; a foreign
@@ -138,7 +139,30 @@ host's shared `AI_AGENT` value is not Codex input. Consequently `pm health` can
 `provenance_resolver_zero_success:<harness>:<dimension>:<resolver>:<attempts>`
 without confusing an unavailable harness signal with a failed resolver. The
 warning is advisory and the storage check includes the bounded attempt and
-success counters for diagnosis.
+success counters for diagnosis. Resolved environment, session, client, and
+inferred observations do not count as probe successes merely because that
+harness declares a resolver. Existing immutable records are preserved; a new
+successful probe clears an all-failed advisory when the complete sample includes
+that event.
+
+`scanProvenanceResolverHealth()` from `@unbrained/pm-cli/sdk/governance` returns
+`sample`, also exposed as `checks[name=storage].details.provenance_sample` by
+`pm health --full --json`. The receipt declares `scope=history_prefix`, the
+10,000-event and 8 MiB ceilings, events/bytes read, truncation, unreadable sources, malformed rows,
+and the earliest/latest valid event timestamps inspected. Files are traversed
+by sorted name and events by append order: this is a bounded history prefix,
+not a rolling recent window. Timestamp bounds describe observed events only.
+`sample.complete=false` suppresses population-wide zero-success conclusions;
+`truncated` separately identifies byte/event limits. Missing or malformed input
+is diagnosed by the integrity checks. An empty or unavailable-only sample is
+not proof that a resolver works. These measurements describe the sampled
+history, not current probe availability or an unobserved historical success.
+The optional `eventLimit` argument must be a non-negative safe integer;
+invalid bounds throw `RangeError`, and zero requests an empty bounded sample.
+
+The `ProvenanceResolverHealthScan` TypeScript result adds a required `sample`
+receipt. Consumers that construct this result themselves must supply the receipt;
+consumers that only read returned scans retain all prior fields unchanged.
 
 Older immutable history can also contain roles outside the controlled domain,
 including values recorded from presence-only harness flags before semantic role

package/docs/SDK_LIFECYCLE.md

@@ -1,8 +1,9 @@
 # SDK Lifecycle Policy
 
 Tracked by [pm-z5pmf8](../.agents/pm/issues/pm-z5pmf8.toon),
-[pm-xm0id4](../.agents/pm/issues/pm-xm0id4.toon), and
-[pm-2ew0w3](../.agents/pm/issues/pm-2ew0w3.toon).
+[pm-xm0id4](../.agents/pm/issues/pm-xm0id4.toon),
+[pm-2ew0w3](../.agents/pm/issues/pm-2ew0w3.toon), and
+[pm-scbr0s](../.agents/pm/issues/pm-scbr0s.toon).
 
 The public SDK owns lifecycle transactions and policy. CLI and MCP operations
 delegate to SDK modules, so an item does not gain different storage,
@@ -39,6 +40,10 @@ Package authors can import these operations from `@unbrained/pm-cli/sdk`
 without importing CLI modules or spawning the executable. Existing CLI import
 paths remain source-compatible while integrations migrate.
 
+See [Concurrent Workspace Mutations](WORKSPACE_CONCURRENCY.md) for settings
+snapshot reconciliation, schema publication, session locks, and checkpoint
+collision semantics shared by these operations.
+
 ## Relationship Identity
 
 Tracked by [pm-olcoon](../.agents/pm/issues/pm-olcoon.toon).
@@ -94,6 +99,15 @@ An embedded SDK consumer can explicitly choose `orderingEdges: "remove"` for
 a domain where predecessor facts are intentionally ephemeral. The CLI and MCP
 do not expose that override and use the durable default.
 
+Explicit removal returns `closed_removed_predecessors:<item>:<ids>` for the
+complete removed row set and `closed_removed_predecessors_count:<item>:<n>`
+for its cardinality. The count is the number of dependency rows, including
+distinct provenance rows that reference the same item. Clearing a transient
+`blocked_by` scalar is reported separately as
+`closed_cleared_blocked_by:<item>:<blocker>` and does not inflate that count.
+Both removal and its receipts use the same selected rows; other relationship
+kinds survive unchanged.
+
 ```ts
 import {
   closeItem,

package/docs/WORKSPACE_CONCURRENCY.md

@@ -0,0 +1,67 @@
+# Concurrent Workspace Mutations
+
+Tracked by [pm-bgcu](../.agents/pm/issues/pm-bgcu.toon). Power-loss durability is
+governed by [pm-o2kc](../.agents/pm/epics/pm-o2kc.toon).
+
+The CLI and MCP use the SDK's persistence primitives. Atomic replacement makes
+one file write indivisible, but preserving concurrent edits also requires
+protecting the read and decision that precede that write.
+
+## Settings snapshots
+
+`readSettings` attaches an internal, non-enumerable persistence snapshot.
+`writeSettings` compares the caller's edited snapshot with the latest document
+while holding the `workspace-history` lock. Changes to different object keys
+are combined, including separate keys in a newly introduced nested object.
+Unchanged keys keep the current persisted values; sparse defaults and
+file-backed schema definitions remain sparse.
+
+Concurrent incompatible edits to the same scalar, array, or deleted object
+return a conflict before writing. Read a fresh settings snapshot and reapply
+the intended operation. Equal concurrent changes are idempotent. A successful
+write advances that instance's baseline, so reusing it cannot replay an earlier
+edit over another writer. Conflict messages name keys without exposing values.
+Deleting the settings document also invalidates an unchanged read snapshot;
+its next write returns the same structured conflict.
+
+Keep the object returned by `readSettings` when editing settings. Constructing
+a new object, spreading it, or using `structuredClone` drops the internal
+snapshot; `writeSettings` treats such objects as explicit whole-document
+replacements. They are suitable for initialization, not concurrent edits.
+
+The same lock protects the persisted document, its workspace history entry,
+and compensation if history append fails. This prevents concurrent writers
+from forking the chain or leaving an accepted write unrecorded. It does not
+claim crash atomicity across separate filesystem writes.
+
+## Schema, session, and rollback state
+
+Schema mutations hold the existing `schema-types`, `schema-statuses`, or
+`schema-fields` lock while reading and modifying their file. Profile application
+uses the same lock order. Bootstrap stages complete seed bytes and publishes
+them through a non-replacing hard link: a concurrent schema writer or reader
+can never be overwritten by a delayed bootstrap. A filesystem that refuses
+hard links returns an error instead of falling back to an unsafe overwrite.
+
+Focus and semantic attribution share the `session-state` lock across the full
+read-modify-write operation. Independent agents retain their attribution while
+focus changes. This state remains local and ephemeral.
+
+Rollback checkpoints use the same atomic, non-replacing publication as schema
+seeds. Filesystem identity also protects paths reached through symlink aliases.
+A byte-identical retry succeeds; reusing an ID for different contents fails without
+replacing the original rollback evidence. Different checkpoint paths remain
+independent.
+
+Atomic publication guarantees complete visible bytes and prevents replacement.
+It does not flush file data or directory entries to stable storage, so success
+does not guarantee survival of power loss. A stronger durability policy must
+cover all writers, newly created ancestor directories, retry acknowledgements,
+and supported filesystems; syncing only this publication path would not establish
+that workspace-wide guarantee.
+
+The mutation locks use the existing bounded contention and stale-owner recovery
+mechanism. Settings use configured lock TTL and wait values. Internal session
+locks use the standard defaults; `PM_LOCK_WAIT_MS` still
+overrides their wait budget. Every acquired lock is released on success and
+failure.

package/docs/agent-task-token-baseline.json

@@ -77,7 +77,7 @@
       {
         "task_id": "orientation-contracts-next",
         "command_count": 2,
-        "estimated_tokens": 4829,
+        "estimated_tokens": 5180,
         "capabilities": [
           "actionable_work",
           "active_ownership",
@@ -120,16 +120,16 @@
     },
     {
       "id": "orientation-contracts-next",
-      "max_estimated_tokens": 4829,
+      "max_estimated_tokens": 5180,
       "steps": [
         {
           "id": "contracts",
-          "max_estimated_tokens": 4111,
+          "max_estimated_tokens": 4458,
           "accounting_mode": "self_reported"
         },
         {
           "id": "next",
-          "max_estimated_tokens": 718,
+          "max_estimated_tokens": 722,
           "accounting_mode": "self_reported"
         }
       ]
@@ -199,11 +199,11 @@
     },
     {
       "id": "unknown-option-recovery",
-      "max_estimated_tokens": 603,
+      "max_estimated_tokens": 596,
       "steps": [
         {
           "id": "refuse-option",
-          "max_estimated_tokens": 440,
+          "max_estimated_tokens": 433,
           "accounting_mode": "self_reported"
         },
         {
@@ -261,5 +261,5 @@
       ]
     }
   ],
-  "composite_max_estimated_tokens": 12667
+  "composite_max_estimated_tokens": 13011
 }

package/docs/generated/AGENT_CAPABILITY_ROUTING.md

@@ -13,5 +13,5 @@ This file is generated from `PM_COMMAND_CAPABILITY_CONTRACTS`. Do not edit it ma
 | evidence | `history`, `history events`, `history redact`, `history repair`, `history compact`, `history attest`, `history acknowledge`, `item append`, `item comments`, `item notes`, `item learnings`, `item files`, `item docs` |
 | graph | `graph`, `item deps`, `plan` |
 | quality | `item test`, `ops test-all`, `ops validate`, `assurance`, `contracts`, `ops` |
-| automation | `meet`, `event`, `remind` |
+| automation | `calendar meet`, `calendar event`, `calendar remind` |
 | extensions | `package` |

package/docs/generated/AGENT_COMMAND_SURFACE.md

@@ -105,8 +105,11 @@ This file is generated from `PM_COMMAND_CAPABILITY_CONTRACTS`. Do not edit it ma
 | `pause-task` | full | lifecycle |
 | `close-task` | full | lifecycle |
 | `meet` | full | automation |
+| `calendar meet` | full | automation |
 | `event` | full | automation |
+| `calendar event` | full | automation |
 | `remind` | full | automation |
+| `calendar remind` | full | automation |
 | `help` | core | context |
 | `ops` | core | quality |
 | `completion-statuses` | internal | internal |

package/docs/generated/FLAG_LEXICON_BUDGETS.md

@@ -108,3 +108,6 @@ This file is generated by `listPmFlagLexicon()`. Compatibility aliases do not co
 | `item copy` | intake | 24 | 24 |
 | `workspace merge` | workspace | 27 | 27 |
 | `item duplicates` | context | 25 | 25 |
+| `calendar meet` | automation | 33 | 33 |
+| `calendar event` | automation | 33 | 33 |
+| `calendar remind` | automation | 29 | 29 |

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.17"
+    "version": "2026.9.19"
   },
   "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.17",
+      "version": "2026.9.19",
       "author": {
         "name": "unbrained",
         "url": "https://github.com/unbraind/pm-cli"

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@unbrained/pm-cli",
-  "version": "2026.9.17",
+  "version": "2026.9.19",
   "description": "Git-native project management CLI for humans and agents.",
   "type": "module",
   "packageManager": "pnpm@11.10.0",
@@ -98,6 +98,8 @@
     ".claude-plugin/**",
     "plugins/**",
     "packages/pm-*/**",
+    "scripts/build.mjs",
+    "scripts/build-lease.mjs",
     "scripts/bundle-cli.mjs",
     "scripts/generate-agent-capability-surfaces.mjs",
     "scripts/finalize-build.mjs",
@@ -108,7 +110,7 @@
     "marketplace.json"
   ],
   "scripts": {
-    "build": "node scripts/prepare-build-cache.mjs && tsc -p tsconfig.json && node scripts/bundle-cli.mjs && node scripts/finalize-build.mjs",
+    "build": "node scripts/build.mjs",
     "typecheck": "tsc --noEmit -p tsconfig.json && tsc --noEmit -p tsconfig.typetests.json && tsc -p tsconfig.packages.json && tsc -p tsconfig.examples.json",
     "start": "node dist/cli.js",
     "dev": "tsx src/cli.ts",
@@ -205,7 +207,7 @@
     "node": ">=22.18.0"
   },
   "dependencies": {
-    "@sentry/node": "10.74.0",
+    "@sentry/node": "10.75.0",
     "@toon-format/toon": "^4.1.1",
     "@types/node": ">=22",
     "commander": "^15.0.0",
@@ -219,18 +221,18 @@
     "@codspeed/vitest-plugin": "^5.7.1",
     "@eslint/js": "^10.0.1",
     "@modelcontextprotocol/ext-apps": "2.0.0",
-    "@sentry/cli": "^3.7.0",
-    "@types/node": "^26.5.1",
+    "@sentry/cli": "^3.8.0",
+    "@types/node": "^26.6.1",
     "@types/npm-package-arg": "^6.1.4",
     "@vitest/coverage-v8": "^4.1.11",
     "esbuild": "0.28.2",
     "eslint": "^10.10.0",
-    "eslint-plugin-sonarjs": "^4.2.0",
-    "eslint-plugin-unicorn": "74.0.0",
-    "fast-check": "^4.10.0",
+    "eslint-plugin-sonarjs": "^4.2.1",
+    "eslint-plugin-unicorn": "75.0.0",
+    "fast-check": "^4.10.1",
     "github-slugger": "2.0.0",
     "greptile": "^3.5.2",
-    "jscpd": "^5.2.0",
+    "jscpd": "^5.2.1",
     "marked": "18.0.13",
     "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.17",
+  "version": "2026.9.19",
   "private": true,
   "type": "module",
   "description": "First-party pm package for importing Beads JSONL records.",

package/packages/pm-calendar/README.md

@@ -1,9 +1,9 @@
 # pm Calendar Package
 
-`@unbrained/pm-calendar` provides agenda and calendar views as an installable pm package.
+`@unbrained/pm-calendar` provides scheduling shortcuts, agenda, and calendar views as an installable pm package.
 
 ```bash
-pm install calendar --project
+pm package install calendar --project
 # Or bootstrap all bundled package commands in a new project:
 pm init --defaults --with-packages
 pm calendar --view week --full-period
@@ -14,6 +14,47 @@ The package owns presentation commands for deadline, reminder, and scheduled eve
 
 Runtime sources are authored in TypeScript and use only the public `@unbrained/pm-cli/sdk` surface.
 
+## Scheduling commands
+
+Tracking: [pm-o3fh](../../.agents/pm/tasks/pm-o3fh.toon),
+[pm-jkjt](../../.agents/pm/issues/pm-jkjt.toon).
+
+```bash
+pm calendar meet "Planning" --start +1d --duration 30min --location "Room A"
+pm calendar event "Release window" --start 2026-10-01T09:00:00Z --duration PT2H
+pm calendar remind "Review release" --at +2d --text "Check acceptance results"
+```
+
+The legacy `pm meet`, `pm event`, and `pm remind` spellings remain aliases.
+Install `calendar` in each project where these commands are needed; without the
+package, the CLI provides an installation hint. Core `create` and `update` retain
+scheduling metadata primitives. SDK integrations can continue calling `runMeet`,
+`runEvent`, and `runRemind` directly without installing presentation commands.
+
+Meetings and events default to a start of `now` and a duration of `1h`.
+An explicit `--end` overrides the shortcut's duration. Reminders default to `+1d`
+and use the title as their reminder text. All three commands support parent,
+tags, priority, body, description, history message, and the host's global author
+and output options. Use `pm contracts --command "calendar meet" --flags-only`
+for the active project's exact contract.
+
+### Duration decision
+
+Accepted [duration ADR](../../.agents/pm/decisions/pm-j1vw3a.toon).
+
+Event durations accept integer `min`, `mins`, `minute`, or `minutes`; `h`, `d`,
+`w`, or explicit `mo` for calendar months; and ISO time durations such as `PT30M`
+or `PT1H30M`. Bare `m`, including signed values such as `+5m`, is rejected with
+`min`/`mo` alternatives before mutation. This resolves the ambiguity recorded in
+pm-jkjt and supersedes the duration compatibility decision in
+[pm-zoe4](../../.agents/pm/features/pm-zoe4.toon).
+
+This rule applies to shortcut durations and the shared `create`/`update` event
+parser. Other relative date fields retain `m` for calendar months. Zero duration
+creates an instant event; an end before the start is rejected. Calendar month
+arithmetic clamps to the last valid day of the target month; compound offsets
+such as `+1d+2h` are rejected.
+
 ## Recurrence Notes
 
 Recurring event `recur_count` values are counted from the event series `start`, not from the query window. For example, a daily event starting April 1 with `recur_count=3` has its counted occurrences on April 1, 2, and 3; querying April 10 does not restart the count.

package/packages/pm-calendar/extensions/calendar/command-definitions.ts

@@ -0,0 +1,52 @@
+/**
+ * @module packages/pm-calendar/extensions/calendar/command-definitions
+ *
+ * Declares pure calendar command metadata shared by runtime and contract gates. The host
+ * supplies alias routing, argument validation, mutation receipts, and telemetry.
+ */
+import type { CommandDefinition, FlagDefinition } from "@unbrained/pm-cli/sdk";
+
+const commonFlags: FlagDefinition[] = [
+  { long: "--parent", value_name: "id", value_type: "string", description: "Parent item id" },
+  { long: "--allow-missing-parent", value_type: "boolean", description: "Permit a parent id that does not exist yet" },
+  { long: "--tags", value_name: "list", value_type: "string", description: "Comma-separated tags" },
+  { long: "--priority", value_name: "value", value_type: "string", description: "Priority" },
+  { long: "--body", value_name: "text", value_type: "string", description: "Body/markdown content" },
+  { long: "--description", value_name: "text", value_type: "string", description: "Short description" },
+  { long: "--message", value_name: "value", value_type: "string", description: "History message" },
+];
+
+const eventFlags: FlagDefinition[] = [
+  { long: "--start", value_name: "when", value_type: "string", description: "Start time (ISO, now, or relative +1h/+2d); defaults to now" },
+  { long: "--duration", value_name: "span", value_type: "string", description: "Duration: min|mins|minute|minutes, h, d, w, mo, or ISO PT time; bare m is ambiguous; defaults to 1h" },
+  { long: "--end", value_name: "when", value_type: "string", description: "End time (ISO or relative); overrides --duration" },
+  { long: "--location", value_name: "value", value_type: "string", description: "Location" },
+  { long: "--timezone", value_name: "value", value_type: "string", description: "IANA timezone (for example America/New_York)" },
+  { long: "--all-day", value_type: "boolean", description: "Mark as an all-day event" },
+];
+
+/** Package-owned shortcuts retain the public SDK operation identities and flags. */
+export const schedulingCommandDefinitions: Omit<CommandDefinition, "run">[] = [
+  ...(["meet", "event"] as const).map((name): Omit<CommandDefinition, "run"> => ({
+    name,
+    action: name,
+    tier: "standard",
+    family: "automation",
+    description: `Create a ${name === "meet" ? "Meeting" : "Event"} with a start time and duration.`,
+    arguments: [{ name: "title", required: true, description: "Item title" }],
+    flags: [...eventFlags, ...commonFlags],
+  })),
+  {
+    name: "remind",
+    action: "remind",
+    tier: "standard",
+    family: "automation",
+    description: "Create a Reminder from a single point in time.",
+    arguments: [{ name: "title", required: true, description: "Item title" }],
+    flags: [
+      { long: "--at", value_name: "when", value_type: "string", description: "Reminder time (ISO, now, or relative +2d); defaults to +1d" },
+      { long: "--text", value_name: "value", value_type: "string", description: "Reminder text; defaults to the title" },
+      ...commonFlags,
+    ],
+  },
+];

package/packages/pm-calendar/extensions/calendar/index.ts

@@ -10,6 +10,7 @@ import type {
 } from "@unbrained/pm-cli/sdk";
 import type { CalendarOptions } from "@unbrained/pm-cli/sdk/runtime";
 import { renderCalendarPackageOutput, runCalendarPackage } from "./runtime.ts";
+import { schedulingCommands } from "./shortcuts.ts";
 
 const CALENDAR_VIEW_NAMES = ["agenda", "day", "week", "month"] as const;
 
@@ -278,6 +279,7 @@ function calendarCommand(name: "calendar" | "cal"): CommandDefinition {
 export function activate(api: ExtensionApi): void {
   api.registerCommand(calendarCommand("calendar"));
   api.registerCommand(calendarCommand("cal"));
+  for (const command of schedulingCommands) api.registerCommand(command);
   api.registerService("output_format", (context) => {
     const rendered = renderCalendarPackageOutput(
       context as ServiceOverrideContext,

package/packages/pm-calendar/extensions/calendar/manifest.json

@@ -4,10 +4,10 @@
   "entry": "./index.ts",
   "priority": 0,
   "trusted": true,
-  "sandbox_profile": "strict",
+  "sandbox_profile": "restricted",
   "permissions": {
     "fs_read": true,
-    "fs_write": false,
+    "fs_write": true,
     "network": false,
     "env_read": true,
     "env_write": false,
@@ -17,6 +17,6 @@
   "manifest_version": 1,
   "pm_min_version": "2026.6.24",
   "activation": {
-    "commands": ["cal", "calendar"]
+    "commands": ["cal", "calendar", "meet", "event", "remind"]
   }
 }

package/packages/pm-calendar/extensions/calendar/shortcuts.ts

@@ -0,0 +1,15 @@
+/**
+ * @module packages/pm-calendar/extensions/calendar/shortcuts
+ *
+ * Binds package-owned scheduling declarations to the public SDK mutation paths.
+ */
+import { runEvent, runMeet, runRemind, type CommandDefinition } from "@unbrained/pm-cli/sdk";
+import { schedulingCommandDefinitions } from "./command-definitions.ts";
+
+/** Scheduling handlers preserve native SDK validation, history, and output receipts. */
+export const schedulingCommands: CommandDefinition[] = schedulingCommandDefinitions.map((definition) => ({
+  ...definition,
+  run: (context) => (
+    definition.name === "meet" ? runMeet : definition.name === "event" ? runEvent : runRemind
+  )(context.args[0], context.options, context.global),
+}));

package/packages/pm-calendar/package.json

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