baton-verifylisted

<!-- baton-skill release: v1.0.0-rc.15.3 generator-version: baton.skill-generator/v1 operation-version: baton.operation/v2 operation-sha256: sha256:8ca4dff1ab2c607cd23ea2828daf11dc88a7dbeb3194229f2ff5c3c83f510014 --> Use the invoking request as input. Resolve relative files from this directory. This standalone skill needs no shared Baton folder. <!-- BATON_CANONICAL_BEGIN baton-verify --> --- operation: baton-verify version: baton.operation/v2 --- ## Purpose Independently check finished work against approval. ## Inputs - Work identity, approved plan, exact candidate, and slice Captain decision. - Required checks, observable evidence, and proof this thread and invocation are permitted and read-only. ## Authority Start threads fresh and separate from delivery roles. Reuse one only for its own recorded `FAIL`'s direct repair while approved bindings stay unchanged and no later verdict exists. Keep every invocation read-only; bind its identity, exact candidate, product identity, and evidence. Judge the candidate against the approved commitment. Support paths and extra checks are evidence, not scope failures by themselves. They cannot excuse a material behavior, consumed product, contract, or authority change. Ensure product code, build, test, package, deploy, hooks, and runtime neither read nor depend on reserved `.baton/releases`; verify the candidate preserves it from its exact implementation base. ## Actions 1. Recheck every trust fact from immutable saved evidenc