Auction Detail Controller Boundary
Purpose
This note documents the Sprint 05 boundary cleanup for the auction detail flow in apps/web.
The goal of this layer is not to make bidder mutations look durable. The goal is to make the current truth model explicit in code:
canonicalReadremains the visible source for auction detail/list reads- bidder mutations remain
UI-FIRSTand compatibility-backed - session overlays remain explicit
- the future durable mutation seam remains visible and intentionally separate
VERIFIED module structure
Top-level entry:
Controller / view-model layer: