## Release verdict: **BLOCK — not releasable**

### P0

- **Frontend and backend household read contracts are incompatible.**  
  `frontend/src/api/household.ts:142-155` expects:
  - overview monthly KPI fields,
  - `{items,total}` transactions,
  - `{review_count,groups}` review data,
  - `GET /household/imports`.

  The backend exposes incompatible aggregate/list shapes and no canonical imports GET at `src/jarvis_finance/api/routers/budget.py:210-233`. Runtime probes confirmed:
  - overview: `200`, but wrong aggregate shape;
  - transactions: `200 []`, filters ignored;
  - review: `200 {candidates, receipt_links, unsafe_groups_can_confirm}`;
  - imports: `404`.

  The overview can throw while rendering `data?.data_status.label` (`frontend/src/pages/HouseholdOverviewPage.vue:25-28`); transactions/review cannot render their returned data.

- **Review preview/confirm is entirely non-functional.**  
  The frontend posts to `/household/review/preview` and `/household/review/confirm` (`frontend/src/api/household.ts:145-146`; `frontend/src/pages/HouseholdReviewPage.vue:58-72`), but neither route exists after the review GET at `src/jarvis_finance/api/routers/budget.py:231-233`. Both runtime probes returned `404`. Therefore none of the advertised transfer/income/expense/duplicate/category/split/Migros/ignore actions can be completed.

- **Selected account mapping is not bound to the import request and can misrepresent the target account.**  
  The UI asks the user to select a mapping (`frontend/src/pages/HouseholdImportsPage.vue:19-22`) but sends only `profile`, CSV text, and an optional `source_reference` (`:92-95`). The options API does not return `source_reference` (`src/jarvis_finance/services/household_import.py:152-160,658-666`), and `mapping_id` is never sent. The backend instead resolves the account from account references inside the CSV (`:65-89,398-402`). A user can select mapping A while the CSV resolves to mapping B, yet the impact header still names A (`HouseholdImportsPage.vue:28`). This is a wrong-account/data-integrity risk.

### P1

- **Technical IDs are present in the DOM.**  
  Mapping IDs are rendered as `<option value>` attributes, and the hashed `reference_hint` is displayed in option text (`frontend/src/pages/HouseholdImportsPage.vue:19,75`). This violates the explicit no IDs/fingerprints-in-DOM requirement.

- **Tests provide false confidence by mocking contracts that the backend does not implement.**  
  `frontend/src/pages/HouseholdUx.test.ts:32-48` invents the expected overview, transaction and review responses.  
  `frontend/src/api/household.test.ts:10-29` stubs every URL as successful—including the nonexistent imports GET—and never exercises FastAPI/OpenAPI. All focused frontend tests pass despite the runtime 404s and response-shape drift.

- **A duplicate legacy transaction surface remains.**  
  `/planning/budget/transactions` redirects correctly, but `/planning/budget/expenses/actual` still mounts the old `BudgetTransactionsPage` (`frontend/src/router/index.ts:64,78`) rather than redirecting to the canonical household transaction route with preserved filters.

### P2

- **Exact viewport acceptance is untested.**  
  CSS has sensible 1100/900/700/420 breakpoints (`frontend/src/style.css:99-126`), but no test renders 1440/820/390 or asserts `scrollWidth <= clientWidth`. `overflow: clip` (`:40`) can hide overflow rather than prove its absence. The existing UX test only checks class/surface presence (`frontend/src/pages/HouseholdUx.test.ts:60-76`).

- **The frontend hardcodes the 5 MB limit instead of using server-provided limits.**  
  `frontend/src/pages/HouseholdImportsPage.vue:16,88` can drift from `max_file_bytes` returned by the options contract.

## Positive checks

- Canonical frontend routes exist, and the converted legacy redirects preserve query/hash via `householdRedirect` (`frontend/src/router/index.ts:38-39,57-101`).
- Import preview→confirm resends the same in-memory files and both fingerprints (`HouseholdImportsPage.vue:100-117`).
- No account auto-create path was found; mappings require existing active linked budget/canonical accounts.
- Raw CSV and fingerprints are not written to URL, localStorage, or sessionStorage.
- Technical `<details>` sections are closed by default.
- Household GET probes were provider-free and mutation-free: SQLite `total_changes` delta was `0`.

## Verification run

- Focused frontend tests: **6 passed**
- Frontend production build/typecheck: **passed**
- Household backend golden tests: **16 passed**
- `git diff --check`: **passed**
- Runtime API contract probes exposed the failures above.

**Files modified:** none.