pm-brief 2026.9.22 → 2026.9.26

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -1,5 +1,11 @@
1
1
  # Changelog
2
2
 
3
+ ## 2026.9.26 - 2026-09-26
4
+
5
+ ### Other
6
+
7
+ - Certify pm CLI 2026.9.23 and adopt the guarded pm-ops merge-driver launcher ([pm-brief-ewrg](https://github.com/unbraind/pm-brief/blob/main/.agents/pm/chores/pm-brief-ewrg.toon))
8
+
3
9
  ## 2026.9.22 - 2026-09-22
4
10
 
5
11
  ### Fixed
package/README.md CHANGED
@@ -334,9 +334,7 @@ explicitly disable both host output bounds.
334
334
  This repo tracks its project management in `.agents/pm/` and ships a committed `.gitattributes`
335
335
  that maps those tracker artifacts to pm-cli's field-aware Git merge drivers, so concurrent-branch
336
336
  tracker edits merge cleanly instead of hard-conflicting. The driver **definitions** live in
337
- 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
338
- `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
339
- on POSIX shells and Windows `cmd.exe`). To (re)run manually: `npm run merge:install`.
337
+ 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`.
340
338
 
341
339
  After merging a branch that touched `.agents/pm/`, reconcile any residual history-hash drift with
342
340
  **`pm merge reconcile`** (pm-cli ≥ 2026.7.22): preview with `pm merge reconcile --dry-run`, apply with
package/dist/index.js CHANGED
@@ -4269,7 +4269,7 @@ function classifyPaths(paths, pmRootRel, historyIds, toonIds) {
4269
4269
  }
4270
4270
  export default defineExtension({
4271
4271
  name: "pm-brief",
4272
- version: "2026.9.22",
4272
+ version: "2026.9.26",
4273
4273
  description: "Token-budgeted agent briefs and next-work plans for pm workspaces",
4274
4274
  activate(api) {
4275
4275
  registerCommands(api);
package/manifest.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "pm-brief",
3
- "version": "2026.9.22",
3
+ "version": "2026.9.26",
4
4
  "description": "Token-budgeted agent briefs and next-work plans for pm workspaces",
5
5
  "author": "@unbraind",
6
6
  "entry": "dist/index.js",
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "pm-brief",
3
- "version": "2026.9.22",
3
+ "version": "2026.9.26",
4
4
  "description": "Token-budgeted agent briefs and next-work plans for pm workspaces",
5
5
  "type": "module",
6
6
  "main": "dist/index.js",
@@ -58,9 +58,9 @@
58
58
  },
59
59
  "devDependencies": {
60
60
  "@types/node": "^26.1.1",
61
- "@unbrained/pm-cli": "2026.9.21",
62
- "pm-changelog": "2026.9.18",
63
- "pm-ops": "2026.9.18",
61
+ "@unbrained/pm-cli": "2026.9.23",
62
+ "pm-changelog": "2026.9.23",
63
+ "pm-ops": "2026.9.23",
64
64
  "typescript": "^7.0.2",
65
65
  "yaml": "2.9.1"
66
66
  },