pm-context 2026.9.22 → 2026.10.3

package/CHANGELOG.md

@@ -1,5 +1,11 @@
 # Changelog
 
+## 2026.9.26 - 2026-09-26
+
+### Other
+
+- Certify pm CLI 2026.9.23 and adopt the guarded pm-ops merge-driver launcher ([pm-context-h04z](https://github.com/unbraind/pm-context/blob/main/.agents/pm/chores/pm-context-h04z.toon))
+
 ## 2026.9.22 - 2026-09-22
 
 ### Fixed

package/README.md

@@ -173,9 +173,7 @@ sent to another agent, or attached to a pull request — and, with
 This repo tracks its project management in `.agents/pm/` and ships a committed `.gitattributes`
 that maps those tracker artifacts to pm-cli's field-aware Git merge drivers, so concurrent-branch
 tracker edits merge cleanly instead of hard-conflicting. The driver **definitions** live in
-per-clone Git config; `npm install` / `npm ci` wires them automatically via the `prepare` script (a portable Node guard, `scripts/prepare-merge-driver.ts`, a thin launcher over `pm-ops/merge-driver`: it runs
-`pm merge install` only when the `pm` CLI is on `PATH`, and no-ops cleanly when `pm` is absent. Registry installs of this package never run `prepare`; a production install of a clone (`npm ci --omit=dev`) omits `pm-ops` too, so it must pass `--ignore-scripts`; being Node-based it behaves identically
-on POSIX shells and Windows `cmd.exe`). To (re)run manually: `npm run merge:install`.
+per-clone Git config; `npm install` / `npm ci` wires them automatically via the `prepare` script, `scripts/prepare-merge-driver.ts`: the launcher template pm-ops ships, copied unchanged, which a test compares byte for byte with the pinned template. It runs pm-ops's installer, which calls `pm merge install` when the `pm` CLI is on `PATH` and skips with a notice when it is not. A production install of a clone (`npm ci --omit=dev`) has no `pm-ops`, so the launcher skips with one notice, while a stale or broken `pm-ops` fails the install. Registry installs of this package never run `prepare`. Being Node-based, it behaves identically on POSIX shells and Windows `cmd.exe`. To (re)run manually: `npm run merge:install`.
 
 After merging a branch that touched `.agents/pm/`, reconcile any residual history-hash drift with
 **`pm merge reconcile`** (pm-cli ≥ 2026.7.22): preview with `pm merge reconcile --dry-run`, apply with

package/dist/index.js

@@ -1389,7 +1389,7 @@ function setupCommands(api) {
 const defineExtension = (module) => module;
 export default defineExtension({
     name: "pm-context",
-    version: "2026.9.22",
+    version: "2026.10.3",
     description: "Generate deterministic pm context packs for agent handoffs, reviews, and status briefs",
     activate(api) {
         setupCommands(api);

package/manifest.json

@@ -1,6 +1,6 @@
 {
   "name": "pm-context",
-  "version": "2026.9.22",
+  "version": "2026.10.3",
   "description": "Generate deterministic pm context packs for agent handoffs, reviews, and status briefs",
   "author": "@unbraind",
   "pm_min_version": "2026.8.15",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "pm-context",
-  "version": "2026.9.22",
+  "version": "2026.10.3",
   "description": "Generate deterministic pm context packs for agent handoffs, reviews, and status briefs",
   "type": "module",
   "main": "dist/index.js",
@@ -55,10 +55,10 @@
   },
   "devDependencies": {
     "@types/node": "^26.1.1",
-    "@unbrained/pm-cli": "2026.9.21",
+    "@unbrained/pm-cli": "2026.9.23",
     "c8": "^12.0.0",
-    "pm-changelog": "2026.9.18",
-    "pm-ops": "2026.9.18",
+    "pm-changelog": "2026.9.23",
+    "pm-ops": "2026.9.23",
     "typescript": "^7.0.2",
     "yaml": "2.9.1"
   },