projmux 0.13.0 → 0.14.0

package/docs/upgrading.md

@@ -1,5 +1,11 @@
 # Upgrading
 
+If an older live app server refuses ordinary commands after upgrading, or npm
+cannot resolve the platform optional dependency, follow
+[Troubleshooting](troubleshooting.md). The canonical marker recovery is the
+exact `projmux config apply --socket <name>` printed by the refusal; ordinary
+runtime commands never backfill missing markers.
+
 projmux has two update surfaces:
 
 - `projmux shell` reads the cached release status before opening the app. When
@@ -25,7 +31,9 @@ projmux update apply
 Use `--dry-run` to see the planned action and `--no-apply` to skip reloading
 the live tmux config after the binary changes. `--no-apply` suppresses live
 tmux access only; the new binary still migrates the keymap schema and
-marker-owned provider files, then writes the generated config. See
+marker-owned provider files, then writes the generated config. It finishes by
+printing `projmux config apply --socket projmux` as the explicit live
+convergence still required before ordinary mutation. See
 [Keymap schema migration](#keymap-schema-migration) and
 [Managed Agent hook producer migration](#managed-agent-hook-producer-migration).
 
@@ -44,6 +52,21 @@ still requires an explicit `PROJMUX_INSTALLER=github-release`.
 
 ## Behavior Changes
 
+### Prompted Codex create requires native authority
+
+A prompted managed Codex create — provider `codex` with exactly one non-empty
+payload operand — no longer degrades to the plain CLI lane when native authority
+cannot be proven. It refuses at the provider-mutation boundary with zero
+threads, zero Panes, and zero Registry writes, and names `--interactive-only` as
+the explicit way to ask for a plain interactive Codex Agent instead.
+
+There is nothing to migrate: no Registry schema, configuration, hook contract,
+or stored Agent changes, and every existing resource keeps working after the
+upgrade. `projmux agent resume`, empty-prompt creates, and the Claude and
+Antigravity providers are unchanged. For the affected calls, the escape hatch,
+and how to verify each claim, see
+[Codex Native-Required Create Migration](codex-native-required-migration.md).
+
 ### Registry schema v2 final Window anchors
 
 The unreleased intermediate schema-v2 Window field `primaryPaneRef` has been
@@ -538,10 +561,17 @@ npm install -g projmux
 For npm-managed installs, `projmux update apply` runs:
 
 ```sh
+<current-projmux> config apply --bin <published-projmux> --socket projmux
 npm install -g projmux@latest
 projmux config apply
 ```
 
+The first apply must succeed before npm publication begins. The final apply is
+post-publication verification by the new binary. Go, GitHub Release, and source
+`make install` use the same pre-converge → publish → verify contract. A failed
+pre-apply prevents publication; a publication or verification failure returns
+non-zero and prints the exact `projmux config apply --socket projmux` recovery.
+
 `npm install -g projmux@latest` is used instead of `npm update -g projmux`
 because `npm update -g` honors the installed semver range and frequently
 refuses to move a global install across a newer minor/major release, leaving it
@@ -564,9 +594,10 @@ projmux update apply --no-apply  # migrate + write config, skip the live reload
 projmux update apply --dry-run   # print the steps only
 ```
 
-`projmux update apply` reinstalls via `go install`, atomically replaces the active
-file, and reapplies the live tmux config so a running `-L projmux` server picks
-up new bindings without a restart.
+`projmux update apply` first converges the live route with the current binary
+and exact eventual executable path, reinstalls via `go install`, then reapplies
+with the published binary so a running `-L projmux` server picks up new bindings
+without a restart.
 
 The command reads `PROJMUX_PROJDIR` from the calling shell and memoizes the
 primary path to `~/.config/projmux/projdir`, so the new binary keeps the same
@@ -585,8 +616,9 @@ PROJMUX_PROJDIR="/main/repos:/secondary/repos" projmux update apply
 
 When `PROJMUX_INSTALLER=github-release`, `projmux update apply` downloads the
 latest matching `projmux_<version>_<goos>_<goarch>.tar.gz` asset from GitHub
-Releases, extracts the binary, atomically replaces the current executable, and
-then runs the new binary's `projmux config apply` — or `config apply --no-reload`
+Releases, extracts the binary, converges the exact live route, atomically
+replaces the current executable, and then runs the new binary's
+`projmux config apply` — or `config apply --no-reload`
 when `--no-apply` is set, so the keymap schema migration still happens.
 
 Set the installer explicitly if you manage a release binary outside npm or Go:

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "projmux",
-  "version": "0.13.0",
+  "version": "0.14.0",
   "description": "tmux project session manager",
   "license": "MIT",
   "homepage": "https://github.com/crevissepartners/projmux#readme",
@@ -28,9 +28,9 @@
     "package:npm:pack": "scripts/package-npm.sh --pack"
   },
   "optionalDependencies": {
-    "@projmux/linux-x64": "0.13.0",
-    "@projmux/linux-arm64": "0.13.0",
-    "@projmux/darwin-x64": "0.13.0",
-    "@projmux/darwin-arm64": "0.13.0"
+    "@projmux/linux-x64": "0.14.0",
+    "@projmux/linux-arm64": "0.14.0",
+    "@projmux/darwin-x64": "0.14.0",
+    "@projmux/darwin-arm64": "0.14.0"
   }
 }