Published · npm latest
Upgrade into the right process.
Patch over 4.6.3. ark upgrade now tells Codex how to refresh,
trust, restart, and verify its local patch hook. Stale MCP and outside-tree
CLI processes stop pretending they are current. No required config migration.
Upgrade
Get 4.6.4
Restart Codex or local Desktop, review and trust the exact hook, exercise a governed
apply_patch, then inspect doctor.writePath.
What changed
No more silent version bleed.
Codex upgrade card
JSON and human output include codex-hard-write with
the exact refresh, restart, trust, and verification path.
Stale MCP fails closed
ark_identity explains the mismatch. Other project tools return
PROCESS_PACKAGE_STALE until restart or retarget.
Global CLI hands off
Outside-tree ark upgrade uses the project-local CLI instead of
managing a checkout through stale PATH state.
CI remains universal
Required arkgate-check --strict-merge still covers hosted,
specialized, shell/direct, incomplete, and human write paths.
Honest limits
What still needs an explicit restart
- A running MCP process cannot replace its own loaded package; restart or retarget it.
- A global CLI older than 4.6.4 cannot contain the handoff; enter once through
npx arkgate upgrade. - MCP remains advisory. Repair reinjection is not guaranteed.
- Only a complete trusted runtime-observed local Codex patch is hard.
Published from gitHead 74bca23.
GitHub release v4.6.4 ↗
· Maintainer source:
docs/releases/4.6.4.md ↗