jarca-ledger-mcp/docs/batches/bat-020_20260712_monthly-settlement-evidence-next-actions-verification-hardening/planning.md

BAT-020 Planning: Monthly settlement evidence, next actions, documentation, and verification hardening

Planning Status

• Status: completed
• Profile: batch-lite
• Design Gate: no
• Design Gate Rationale: REQ-025 is a read-only hardening/documentation slice that builds on already-delivered page sections and existing docs/test patterns without introducing new persistence, service contracts, or runtime flow ownership.

Objective

Turn REQ-025 into the final hardening batch for the 월정산 page by adding evidence/next-action sections, updating docs, and strengthening completed-page verification.

Work Slices

1. Evidence + next actions UI
   • Render close-ready summary, major blockers, source coverage summary, and follow-up hints.
   • Keep wording explicitly read-only.
2. Baseline document alignment
   • Update docs/project-structure.md and docs/runtime-flows.md.
   • Touch docs/interface-contract.md only if the completed implementation actually changes an internal/external contract.
3. Verification hardening
   • Expand AppTest/pytest/smoke evidence for the completed page.

Acceptance Source

• REQ-025 Acceptance Criteria AC-1 through AC-5.

Dependencies

• BAT-018 / REQ-023 implemented page shell.
• BAT-019 / REQ-024 implemented operational sections.
• Existing read-only scope guardrails from dcy-015.

Milestones

1. Evidence/next-action sections render on the completed page.
2. Required baseline docs reflect the page flow and deferred scope.
3. Ruff + pytest and any relevant dashboard smoke evidence pass.

Risks

• Evidence wording may imply write/close capability that this scope does not implement.
• Documentation drift may occur if the final UI structure differs from the discovery summary.
• Over-broad verification edits could spill outside the monthly settlement slice.

Handoff Readiness

• Ready for implementation: after BAT-018 and BAT-019 completion.
• Lead authority needed before delivery: no additional user decision is currently open; scope is approved in dcy-015 / REQ-025.
• Kanban status: deliberately not used.