# AUTH — TODO

Planned work for user authentication (bearer tokens, JWT, login flow, hub authorization).

For known issues, see [`AUTH_ISSUES.md`](AUTH_ISSUES.md).
For the architectural authority, see [`../adr/0001-user-bearer-token-flow.md`](../adr/0001-user-bearer-token-flow.md) — its Follow-up sections ("Implementation", "Consumer wiring") are the master plan for what should populate this file.

## Priority legend

- **P0** blocker · **P1** important · **P2** nice-to-have · **P3** idea

## Active entries

*(No `AUTH-T-N` entries yet — topic just created. ADR 0001 Follow-up "Implementation" + "Consumer wiring" lists the master plan; granular `AUTH-T-N` entries will populate this file as implementation phases kick off and break the high-level plan into trackable units.)*

## Entry format

When adding the first entry, follow the standard `_TODO.md` shape used across topics (LOGGING, SIGNALR, BINARY), with `AUTH-T-N` ID format per [`TOPIC_CODES.md`](../../.github/skills/docs-check/references/TOPIC_CODES.md):

- ID line with `**Priority:** P1/P2/P3 · **Type:** Feature/Refactor/Bug fix/etc. · **Related:** <cross-refs>`
- Short rationale (1-2 sentences)
- Optional sections: Acceptance criteria, Migration plan, Consequences/checklist
