baton-planlisted

<!-- baton-skill release: v1.0.0-rc.15.3 generator-version: baton.skill-generator/v1 operation-version: baton.operation/v2 operation-sha256: sha256:ad6a38f379987bfc7d1ef00c7ab471693063edb21110224af365bd2e1af557bb --> Use the invoking request as input. Resolve relative files from this directory. This standalone skill needs no shared Baton folder. <!-- BATON_CANONICAL_BEGIN baton-plan --> --- operation: baton-plan version: baton.operation/v2 --- ## Purpose Turn a goal into a clear contract for someone else to approve. Planning never approves itself. ## Inputs - Goal, repository, target, approver, and applicable plan. - Current repository, scope, acceptance, dependencies, inputs, limits, and exclusions. ## Authority Keep the release while its goal, target, and approver stay the same. Preserve unchanged slices and identify consumers of changed inputs. Approval must cover the exact release skeleton and every declared slice file. The plan is a commitment. Support paths, additional checks, evidence, scheduling, retries, worktrees, and bookkeeping need no revision when the promise stays the same. ## Actions 1. Inspect Git, the plan, code, tests, docs, and history. Find repository facts. 2. Ask only about human choices that could change the result. Offer no plan while one is open. 3. When clear, summarize result, scope, acceptance, inputs, and limits; ask for correction or confirmation, then stop without plan bytes. 4. Later, write a plan or forward-only revision wi