codex-orchestrator 0.1.49 → 0.1.51

package/CHANGELOG.md

@@ -6,6 +6,31 @@ The format is based on Keep a Changelog, and this project follows SemVer.
 
 ## [Unreleased]
 
+## [0.1.51] - 2026-07-15
+
+### Fixed
+- Bridge publication normalizes the package CLI executable mode before hashing,
+  so installed-package verification matches npm's required `bin` mode.
+
+## [0.1.50] - 2026-07-15
+
+### Added
+- Added a target-scoped shared/exclusive activity fence for daemon lifetime,
+  targeted claims, setup, and skill-runtime-v2 preparation.
+- Added `setup --prepare-skill-runtime-v2`, strict Darwin/Linux legacy-process
+  drain checks, canonical prepared-generation evidence, and a verified
+  `bridge-runtime.json` package manifest.
+
+### Changed
+- Runner state can preserve a forward-compatible empty version-2 envelope while
+  bridge config remains version 1; bridge execution still stores only legacy
+  run records and does not change prompt or Codex transport behavior.
+
+### Security
+- Skill-runtime-v2 preparation now fails closed on foreign or ambiguous process
+  ownership, active local/GitHub claims, GitHub read failure, and bridge package
+  provenance mismatch.
+
 ## [0.1.49] - 2026-07-15
 
 ### Added

package/README.md

@@ -225,8 +225,28 @@ Run setup and create missing labels:
 codex-orchestrator setup --prepare-labels
 ```
 
-Commit the generated `.codex-orchestrator/` directory to your repository. It is
-the repository-owned policy for how autonomous work should run.
+### Prepare A Consumer For Skill Runtime V2
+
+The bridge release adds a fail-closed activity fence without changing prompt
+execution. After that exact bridge package is installed, stop every runner for
+the target and prepare canonical migration evidence:
+
+```sh
+codex-orchestrator setup --target . --prepare-skill-runtime-v2
+```
+
+Preparation succeeds only when no daemon, targeted claim, setup, local
+nonterminal run, or open GitHub issue with the running label can overlap it.
+It writes `skill-runtime-v2/prepared-generation.json` below the configured
+runner state directory and records the verified bridge package hash. Relative
+or otherwise ambiguous daemon process identities block preparation. This
+command does not migrate config, switch the Codex transport, publish a package,
+or start work; those actions belong to a separately authorized structural
+release.
+
+For normal setup, commit the repository-owned config and prompt policy files
+under `.codex-orchestrator/`. Do not commit `prepared-generation.json`; it is
+runtime migration evidence beneath the ignored runner state directory.
 
 By default, setup reads the GitHub owner and repo from `git remote origin`. Use
 `--target`, `--github-owner`, or `--github-repo` only when you need to override