- Shipped
- May 21, 2026 at 11:04 PM UTC
- Author
- kamo
- Commit
- fc6799a
The kamo-internal app proxies every Java backend path through an explicit Next.js route handler (one per top-level segment: /commerce-markets, /pos, /leads, …). /api/security/mortgage-apps had no handler, so every call from mortgageAppsApi (used by the URLA /applications page, the Mortgage Programs settings panel, and now PipelineApplicationsTab) hit Next.js's 404 and the calling component crashed into its error boundary. That's the "404 ERROR" on /commerce?tab=market-{uuid} — the Applications sub-tab inside the market view loads via mortgageAppsApi.list() and bombed every request. - New catch-all at **************** — same shape as the commerce-markets proxy: forwardToApi with X-***-Token pass-through, JSON wrap on success, JSON wrap on error. - Streams non-JSON responses untouched (HMDA LAR CSV download **************** would otherwise be re-wrapped as JSON and corrupted). - 204 No Content (DELETE responses) propagates without a body. PipelineApplicationsTab now loads from both mortgageAppsApi.list() AND the legacy **************** and dedupes by uid. URLA wins on conflict. Both sources are gracefully .catch()'d so a backend outage on either path doesn't blow up the tab.