TRIAD Codex Dispatch 0.2.560

Fixes #42: formal public-v2 guarded-worktree Gemini reviews can read their required task and diff when the sealed packet is outside the product workspace. Generated calls add only the exact bound shared directory through Gemini's native --include-directories; the product cwd and read-only policy stay intact.

Packet access is bound through the existing preflight and allocation. Invalid or changed controls refuse before inference. Result bindings, raw investigations and prepared-directory behavior are unchanged. A valid negative result caused by unavailable inputs remains a blocked review, not a transport retry.

After updating, open a fresh Codex session and create a new review ID/basis. Do not reuse or hand-edit an old allocation.

Shared specification: R-PREPARE/C79, spec PR #14. This clarification does not change tagged spec adoption or Claude's existing packet co-location.

Verification on macOS arm64 / Python 3.12.13: source suite and immutable release archive each passed 2,462 tests with 4 route skips; focused source checks passed 148 tests with 4 skips; four skill validators passed. All 335 tracked archive files match the reviewed commit d0f32ad89be037884d39a48bfcec123358e8f4c3, including the 52 packaged hash targets. Unrelated untracked source files were preserved; this is immutable archive verification, not a claim that the original checkout was completely clean. Native Ubuntu verification was not run here.

Asset SHA-256: b771a47594321310fbbfc981e7a18bcf85601fc6c0c88c7c92eba39466d923e9 for triad-codex-dispatch-0.2.560.tar.

Independent final review with owner-authorized web and official source lookup: Sol/xhigh, Astra/high and AGY Google Pro/high all returned SAFE on the same candidate and digest, with matching before/after integrity (triad-gemini-packet-20261012-r2). A nonblocking suggestion to comment on hypothetical future native changes was declined because it identifies no current defect; the version-specific evidence limits remain explicit. Claude uses the owner's standing quota exception.

Authenticated Gemini validation remains for the owner's company environment after release. Local verification uses deterministic wrapper regressions and the official Gemini CLI 0.63.0 native file-tool implementation without inference; it does not establish enterprise authentication, service availability or effective company policy. No local plugin installation or fresh installed-session success is claimed by this release.