REQ-024 Monthly settlement operational blockers, import/account, and asset status sections

Status: Proposed
Type: Interface
Priority: High
Owner: 렛저장인
Source Discovery: docs/discovery/dcy-015_20260711_monthly-settlement-page-requirements-wireframe.md
Depends On: REQ-022, REQ-023
Created At (KST): 2026-07-11 20:56 KST

1. Intent

Complete the operational checklist half of the 월정산 page: what must be reviewed before the household can treat the selected month as settlement-ready.

Render 정산 전 검토 Blocker section.
Include unresolved counts/status for:
- uncategorized transactions
- review/cross-transfer pending items
- held/recheck items
- reconciliation/account attention indicators
- missing or stale account/asset balances
Render 거래 반영 / import 상태 section:
- account name/type/institution
- last_synced_at
- last_balance
- user-friendly status badge
- recent import batch summary
Render 자산 / 순자산 마감 상태 section:
- asset snapshot preview/closed state
- assets, liabilities, net worth
- warnings/excluded summary
- CTA to the existing 자산/마감 page when close action is needed
Respect REQ-021 import provenance and sensitive-data policy.

AC-1: Blocker section renders with user-friendly labels, not only internal code names.
AC-2: Import/account status does not expose raw local file paths or raw payloads.
AC-3: Asset status reuses existing asset snapshot service definitions.
AC-4: Each unresolved item type provides a clear existing-page CTA/menu hint.
AC-5: AppTest or equivalent dashboard test covers representative blocker/import/asset rendering.
AC-6: python -m ruff check . and relevant pytest/dashboard tests pass.

This REQ depends on the read model and page shell so it can focus only on operational completeness and sensitive-data boundaries.