arkgate v4.6.3

ArkGate 4.6.3

• Status: prepared
• Target npm: arkgate@4.6.3 (latest after publish)
• Target Git tag: v4.6.3
• Prior published: arkgate@4.6.2

Patch over 4.6.2. Codex CLI and local ChatGPT Desktop/App Server now get an honest
operation-scoped pre-write block for complete apply_patch calls. No required config migration.
No new skill names, sensors, scores, or runtime-package promotion.

What changed

• ArkGate accepts the current Codex hook payload: tool_name: "apply_patch" with the patch body
  in tool_input.command.
• A trusted, runtime-observed, completely reconstructed local apply_patch can report
  hard:true and exit 2 before disk mutation.
• .codex/hooks.json on disk remains configured/unverified; it does not prove trust or a live
  hook invocation.
• Doctor, status, --require-write-hook codex, onboarding matrices, generated host support, and
  self-service upgrade honesty agree on the same operation-scoped boundary.
• Codex CLI and local Desktop/App Server share the local hook contract. MCP remains advisory.

Honest limits

• Hosted tools do not use the local function-tool hook path.
• Specialized Codex paths may opt out of the default hook path.
• Shell/direct filesystem writes, human edits, and incomplete patch reconstruction do not inherit
  the local hard claim.
• Repair envelopes may emit, but Codex reinjection is not guaranteed.
• A required GitHub status context running arkgate-check --strict-merge remains the only
  all-path merge boundary.
• Z09 / RB-11 retained-adoption claims remain open.

Platform references:
Codex Hooks ·
Advanced configuration ·
Codex App Server.

Upgrade

npm install -D arkgate@4.6.3
npx arkgate-check --install-agent-gates --tools codex --force
npx arkgate-check --doctor

Restart Codex or the local Desktop session, review and trust the exact project hook, then exercise
a governed apply_patch. Installed files alone remain unverified.

Maintainer publication checklist

1. Land the prepared 4.6.3 PR on protected main
2. Signed tag v4.6.3 + GitHub Release from this file
3. gh workflow run publish-npm.yml -f tag=v4.6.3 -f dry_run=false
4. Verify npm latest, provenance, tarball checksum, and gitHead
5. Flip release notes, CHANGELOG, pointers, and q06 to published
6. mcp-publisher validate server.json && mcp-publisher publish server.json
7. Publish arkgate-site /changelog/4.6.3/ and host matrix

Security notes

This change narrows a prior false-negative in local Codex enforcement. It does not widen filesystem
access, auto-apply repair output, weaken architecture policy, or replace the required CI boundary.