pm-presets 2026.10.16 → 2026.10.20

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/README.md CHANGED
@@ -319,8 +319,11 @@ MIT
319
319
  This repo tracks its project management in `.agents/pm/` and ships a committed `.gitattributes`
320
320
  that maps those tracker artifacts to pm-cli's field-aware Git merge drivers, so concurrent-branch
321
321
  tracker edits merge cleanly instead of hard-conflicting. Generated extension assets are excluded
322
- from semantic merging, while their managed manifest retains key-level JSON merging. The driver
323
- **definitions** live in per-clone Git config; `npm install` / `npm ci` wires them automatically via the `prepare` script, `scripts/prepare-merge-driver.ts`: a local launcher that delegates to the installed pm-ops export and is tested against an installer behavior contract. 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`.
322
+ from semantic merging, while their managed manifest retains key-level JSON merging.
323
+ Extension assets use Git's native `merge=text` attribute. Native `text`, `binary`, and
324
+ `union` drivers need no `merge.<name>.driver` registration; the prepare checks require
325
+ registration for every custom driver and verify native extension text merging in a real checkout.
326
+ The custom driver **definitions** live in per-clone Git config; `npm install` / `npm ci` wires them automatically via the `prepare` script, `scripts/prepare-merge-driver.ts`: a local launcher that delegates to the installed pm-ops export and is tested against an installer behavior contract. 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`.
324
327
 
325
328
  After merging a branch that touched `.agents/pm/`, reconcile any residual history-hash drift with
326
329
  **`pm merge reconcile`**: preview with `pm merge reconcile --dry-run`, apply with
package/manifest.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "pm-presets",
3
- "version": "2026.10.16",
3
+ "version": "2026.10.20",
4
4
  "description": "All 7 official pm-cli workspace presets in one package: bug-triage, indie-dev, open-source, software-sprint, startup-roadmap, kanban, agent-workflow",
5
5
  "author": "@unbraind",
6
6
  "entry": "./dist/index.js",
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "pm-presets",
3
- "version": "2026.10.16",
3
+ "version": "2026.10.20",
4
4
  "description": "All 7 official pm-cli workspace presets in one package: bug-triage, indie-dev, open-source, software-sprint, startup-roadmap, kanban, agent-workflow",
5
5
  "repository": {
6
6
  "type": "git",
@@ -57,9 +57,9 @@
57
57
  },
58
58
  "devDependencies": {
59
59
  "@types/node": "^26.2.0",
60
- "@unbrained/pm-cli": "2026.10.12",
61
- "pm-changelog": "2026.10.12",
62
- "pm-ops": "2026.10.12",
60
+ "@unbrained/pm-cli": "2026.10.15",
61
+ "pm-changelog": "2026.10.16",
62
+ "pm-ops": "2026.10.16",
63
63
  "typescript": "^7.0.2"
64
64
  },
65
65
  "engines": {