The dashboards' session kept server-side: the browser holds a signed JWT
naming one random id, which the store mints with the cookie and seals the
tokens under. A cookie that doesn't verify never reaches the store.
cognito-session.ts reads the row as cookies and its token writes land here.
The dashboards' session kept server-side: the browser holds a signed JWT naming one random id, which the store mints with the cookie and seals the tokens under. A cookie that doesn't verify never reaches the store.
cognito-session.tsreads the row as cookies and its token writes land here.