Phase 16: Petal authenticates for itself

Petal is now an OIDC client in its own right rather than trusting a header
from the proxy. The Phase-0 Resolver seam was the only integration point:
main.go picks the session store when Authentik is configured and the static
local user otherwise, and no handler or query moved for either.

internal/auth gains three pieces. session.go issues an opaque cookie token
and stores only its SHA-256, so a database copy yields nothing usable; the
30-day expiry slides on every request, throttled to one write an hour, and
logout deletes the row rather than just the cookie. oidc.go runs the
authorization-code flow with state, nonce and PKCE, and discovers the
provider lazily and on retry — an Authentik outage should block new logins
without stopping Petal booting or invalidating live sessions. users.go
provisions accounts from the token's claims and gates them on an allowlist
that matches emails as well as subject ids, since a subject is an opaque
uuid that doesn't exist until someone has already logged in once.

Migration 0010 lands sessions, images and users.pair_lang together. The
images table closes the capability-URL hole the Phase-0 audit flagged: a
hash was previously enough to fetch anyone's picture. Rows are keyed
(name, user_id) so one file can have several owners and deduplication
survives; a stranger gets 404 rather than 403, the cache header drops to
private, and files already on disk are claimed at startup or every image
already pasted into a document would 404.

On the frontend a single 401 interceptor feeds a warm bilingual sign-in
overlay, drawn over a still-visible editor because nothing has been taken
away. Behind it is the part that matters: a save that comes back 401
stashes its body to localStorage before anything else and stops the
auto-save loop, and reopening that document after signing in merges the
draft back and saves it. An expired session must not cost writing.

Writing the round-trip test against a stub identity provider turned up a
real bug: the one-shot state/nonce/PKCE cookies were cleared in a defer,
which runs after the redirect has written the response header, so the
clearing Set-Cookie was silently dropped and they lingered for their full
ten minutes.

Also swaps the emoji favicon for a drawn sakura, which renders as Petal's
own rose palette everywhere instead of whatever each platform's font
decides, and doubles as the app tile in Authentik.

Migration 0010 verified against a VACUUM INTO copy of the live millenia
database: counts intact, FTS still matching, the one existing image
claimed.

Claude-Session: https://claude.ai/code/session_016y6gyuHkQXPiEuW8RGQyua

web/src/api/client.ts

@@ -150,11 +150,45 @@ export interface MechanicsFinding {
   explanation: string
 }
 
+// Who's writing. Mirrors the backend db.User.
+export interface Me {
+  id: string
+  email: string
+  display_name: string
+  created_at: string
+  pair_lang: string
+}
+
+// Thrown when the server says the session is gone. Callers can tell it apart
+// from a real failure — losing your session is not the same as a save going
+// wrong, and the auto-save has to treat them very differently.
+export class UnauthorizedError extends Error {
+  constructor() {
+    super('not signed in')
+    this.name = 'UnauthorizedError'
+  }
+}
+
+// Sessions expire, so *any* call can come back 401 — including the auto-save
+// that fires 1.5s after every keystroke. One place notices, and the app reacts
+// once, rather than each call site inventing its own answer.
+let unauthorizedHandler: (() => void) | null = null
+
+export function onUnauthorized(handler: () => void) {
+  unauthorizedHandler = handler
+}
+
+function signedOut(): UnauthorizedError {
+  unauthorizedHandler?.()
+  return new UnauthorizedError()
+}
+
 async function req<T>(path: string, init?: RequestInit): Promise<T> {
   const res = await fetch(`/api${path}`, {
     headers: { 'Content-Type': 'application/json' },
     ...init,
   })
+  if (res.status === 401) throw signedOut()
   if (!res.ok) {
     const detail = await res.text().catch(() => '')
     throw new Error(`${res.status} ${res.statusText}${detail ? `: ${detail}` : ''}`)
@@ -164,6 +198,10 @@ async function req<T>(path: string, init?: RequestInit): Promise<T> {
 }
 
 export const api = {
+  // The signed-in writer. With auth unconfigured (local development) this is
+  // the hardcoded local user, so the frontend needs no separate mode for it.
+  me: () => req<Me>('/me'),
+
   listDocs: () => req<DocSummary[]>('/docs'),
   createDoc: () => req<Document>('/docs', { method: 'POST' }),
   getDoc: (id: string) => req<Document>(`/docs/${id}`),
@@ -254,6 +292,7 @@ export const api = {
     const form = new FormData()
     form.append('image', file)
     const res = await fetch('/api/images', { method: 'POST', body: form })
+    if (res.status === 401) throw signedOut()
     if (!res.ok) {
       const detail = await res.text().catch(() => '')
       throw new Error(`${res.status} ${res.statusText}${detail ? `: ${detail}` : ''}`)
@@ -370,6 +409,7 @@ export async function streamSuggestionChat(
     body: JSON.stringify({ messages }),
     signal,
   })
+  if (res.status === 401) throw signedOut()
   if (!res.ok || !res.body) {
     const detail = await res.text().catch(() => '')
     throw new Error(`${res.status} ${res.statusText}${detail ? `: ${detail}` : ''}`)