461cd8421c6e004ba7eea498fc8853487a06ec52
Known bug per BACKEND-API-REFERENCE.md §5: the client has dedicated session-expired/invalid-signature recovery screens fully built, but the mapper only ever derived the error code from HTTP status, never the response body - so a real 401 with error.code: 'TOKEN_EXPIRED' rendered the generic 'Unauthorized' screen instead. Frontend half of the fix: prefer error.code from the body when present (mapped via authErrorCodeFromBackendCode), fall back to status-derived code otherwise. Stays dormant until the backend actually sends the code, per the doc. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Description
No description provided
Languages
TypeScript
71.4%
HTML
15.3%
SCSS
11.9%
Shell
1.3%
JavaScript
0.1%