baton-mergelisted

<!-- baton-adapter package-version: 1.0.0-rc.5 operation-version: baton.operation/v2 operation-sha256: sha256:ccc995fd1b38814858f5fcf1122c61409acbbd281596cb259c6de4ba18a6df1b --> 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-merge --> --- operation: baton-merge version: baton.operation/v2 --- ## Purpose Mechanically compose passed track candidates or integrate the exact assembled candidate covered by current `PASS`. ## Inputs - The applicable approved plan revision and one captured Git snapshot. - For track composition, the ordered passed slice candidates. - For release integration, the exact assembled candidate and fresh assembly `PASS`. ## Authority Merge never invents a verdict or resolves a product conflict. Derive candidates, topology, and expected targets from approved facts. Refuse unsafe mutation, then allow the surrounding system to rescan and reconcile operational outcomes. ## Actions 1. For a track, prove every required slice has applicable `PASS`, freeze the exact candidate, and compose it through the approved topology. 2. After all tracks are present, identify the exact assembled candidate and stop for fresh `baton-verify` assembly. 3. For release Merge, recheck the assembly `PASS`, candi