baton-planlisted

<!-- baton-adapter package-version: 1.0.0-rc.5 operation-version: baton.operation/v2 operation-sha256: sha256:91197ccfdda4475b09f70d50e6dd1fe248f7135625172618051b81dc98016088 --> 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-plan --> --- operation: baton-plan version: baton.operation/v2 --- ## Purpose Propose a bounded delivery plan or forward-only revision for external approval. Planning never grants its own authority. ## Inputs - The goal, repository, target, and external authorizer. - Stable tracks and slices with scope, acceptance, checks, constraints, dependencies, consumed inputs, and exclusions. - The prior approved revision and current repository facts when revising. ## Authority Keep one release identity while its goal, target, and authority remain the same. Retain unchanged slices. Change only the slices whose contracts changed and identify the dependency closure whose consumed inputs changed. Approval must bind the exact proposed bytes. ## Actions 1. Inspect current Git and the applicable plan revision. 2. Propose the smallest complete next revision using `templates/plan.md`. 3. Preserve stable slice identities; add or explicitly retire slices when the approved outcomes change. 4. Present the