baton-implementlisted

<!-- baton-adapter package-version: 1.0.0-rc.5 operation-version: baton.operation/v2 operation-sha256: sha256:f8558c042acc653c3093fc2efb9bac7599a4e479139174e93df9c33e64743a6d --> 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-implement --> --- operation: baton-implement version: baton.operation/v2 --- ## Purpose Design or implement one eligible slice without crossing the Captain or Verifier boundary. ## Inputs - The applicable approved plan revision and stable slice identity. - The current attempt, dependencies, consumed inputs, scope, acceptance, checks, constraints, and exclusions. - The applicable Captain decision and prior Verifier decision when present. ## Authority Work only inside the approved slice and current attempt. Implementation requires an applicable `PROCEED` bound to this plan revision, slice, and design attempt. A `REVISE` adds a design attempt; a `FAIL` adds an implementation attempt. Neither replaces the slice. ## Actions 1. Before design, require the engine-prepared exact current consumed `PASS` base. Then inspect the work and return a concise design TL;DR covering approach, touched surfaces, consequential decisions, risks, and evidence. Stop. 2. After applicable `PROCEED`, requi