baton-verifylisted

<!-- baton-adapter package-version: 1.0.0-rc.5 operation-version: baton.operation/v2 operation-sha256: sha256:080034f552086a7e73fc27fb9f155320ac7638749481b477d16af4afdc59afaf --> Treat the free-form invocation text as the operation inputs. Resolve the Baton package root from the current Git project .codex/baton install when present and valid; otherwise use the configured Codex user directory baton install. Read package-relative files from that root. <!-- BATON_CANONICAL_BEGIN baton-verify --> --- operation: baton-verify version: baton.operation/v2 --- ## Purpose Independently verify one slice candidate or the complete assembled product against the applicable approved contract. ## Inputs - Scope: one stable slice or the assembled release. - The applicable approved plan revision and exact candidate. - The applicable Captain decision for slice verification. - Required checks, observable evidence, and protected fresh read-only dispatch evidence. ## Authority Begin in fresh context with read-only candidate access. Differ from the Implementer and Captain. Bind the decision to the exact plan revision, candidate, product identity, evidence, and invocation. ## Actions 1. Re-establish every trust-critical binding from immutable facts. 2. Inspect the real candidate, rerun required checks, and test each acceptance claim at its named boundary. 3. For assembly, check every composed component and the complete product. 4. Return exactly one verdict: - `PASS` when the exact