Repository navigation
TRIAD Codex Dispatch 0.2.556
TRIAD Codex Dispatch 0.2.556 adds the opt-in v2 review workflow, owner-requested web verification, stronger transport evidence, and English/Korean installation guidance.
- Resolve and invoke all enabled roster entries, collect immutable per-entry attempts, and preserve all six bound result fields. Existing legacy and raw/custom-schema interfaces remain available.
- Enable web verification for participating legs only when the owner directly requests it for that round. Default reviews remain no-web; native availability and existing owner restrictions are checked before dispatch.
- Preserve transport failures, original verdicts, nullable adapter defaults and observed runtime identity. Reject reserved evidence paths before partial writes.
- Install through the GitHub marketplace or a local Git clone. Both language guides cover personal settings, existing configuration, updates and source switching. Legacy Gemini CLI / Gemini 구버전 CLI 사용 is the display label; authentication and version requirements remain unchanged.
Release commit: 5a12f822b6e19f5ecd162e4cc54888269ec0ffd9. Use this full commit ID with the local Git guide for a pinned installation. The marketplace install route follows main.
The attached archive was produced and tested at 2d4d71b1a6df09b26fae44d228229cd9aa43218d; its Git tree is identical to the release commit. SHA256SUMS verifies the attached archive:
fb1bd7b9f5e49855cdadd88838b51ef7e1a7fd09c0ea961a75af8adbd1684a79 triad-codex-dispatch-0.2.556.tar
Validation: 1,682 tests passed from the clean extracted archive; 48 package targets and all five final release-document changes match the source. A fresh source executor passed 46 relevant tests, skill validation and the provider-free lifecycle. The final four-leg review was ADMITTED_SAFE, and GitHub checks passed before merge.
Owner-reported validation (2026-09-21): Gemini CLI invocation succeeded in the reported environment.
Authenticated web verification across providers, Legacy Gemini CLI host-policy checks, fresh marketplace installation/discovery, and Claude-host shared-spec adoption remain separate verification steps. AGY page-body prefix loss remains a documented incomplete-evidence observation; its vendor cause is not established. Review success or a tool's success status does not prove that a fetched page body is complete.