JWT `alg` taken from attacker-controlled header

**Status:** **verified not exploitable today** `jsonwebtoken` 10.4 blocks
cross-family confusion. Kept because the property rides a dependency invariant, not
a local assertion.
- **Fix (defense-in-depth):** derive expected `alg` from the stored JWK and pin it;
add `aud` validation.
- **Tool:** none.
Verification half — **open here** (`auth/mod.rs`):

- [ ] Pin `alg` from stored JWK
- [ ] Add `aud` validation + `kid` handling
Rotation half — **delegated to epic (Phase 3)**, do not duplicate:

- [x] ~~Add key rotation/revocation path~~ → tracked in issuer-registration epic

**blocked by #187**

The issue points to `auth/mod.rs` as the implementation spot, so start by reading that module and the JWT verification flow. Check where `alg`, `kid`, and token claims are currently validated, then apply pinned `alg` behavior from stored JWKs and add `aud` validation in that path. Before editing, read #187 to respect the blocker context, and mark done when auth verification rejects invalid `alg`/`aud`/`kid` cases and related auth tests pass.

Escrita pelo modelo de indexação a partir do texto da issue.