# Tasks — `@suaveplan/api-tenant-resolver-jwt`

> Every checkbox MUST reflect work actually done in this change.

## 0. Pre-flight (non-negotiable)

- [ ] 0.1 Confirm clean working tree (`git status` reports nothing) and no in-flight worktrees with uncommitted work (`git worktree list` then `git status` in each)
- [ ] 0.2 If any worktrees exist under `.claude/worktrees/`, account for each one: still-active agent, work-pending-merge, or stale-and-prune. Stale worktrees MUST be removed (`git worktree remove`) before opening a new one — code that has been lost twice on main is the failure mode this guards against.
- [ ] 0.3 Confirm the package set in `MANIFEST.md` matches `find packages -maxdepth 3 -name package.json` count. Drift here means a prior change archived without regenerating the manifest.

## 1. Spec authoring

- [x] 1.1 Read design doc (§6, §5.2a, §13.4)
- [x] 1.2 Read `openspec/changes/api-tenant-resolver/` (or contract location) for upstream interface (api-auth contains tenant-resolver chain types)
- [x] 1.3 Read `openspec/AGENTS.md` Sections 13 and 14
- [x] 1.4 Draft `proposal.md`
- [x] 1.5 Draft `specs/api-tenant-resolver-jwt/spec.md`
- [x] 1.6 Every requirement carries `**Verified by:**`

## 2. Implementation

- [ ] 2.1 Scaffold `packages/api/api-tenant-resolver-jwt/` (deps: api-tenant-resolver contract, api-types, api-worker-rpc, error, zod)
- [ ] 2.2 `src/options/jwt-tenant-resolver-options.ts` — Zod schema
- [ ] 2.3 `src/factory/create-jwt-tenant-resolver.ts` — direct surface
- [ ] 2.4 `src/proxy/create-jwt-tenant-resolver-worker-proxy.ts` — proxy surface
- [ ] 2.5 `src/error-codes.ts` — `TENANT_JWT_*` codes via `defineCodes`
- [ ] 2.6 `src/index.ts` — explicit named re-exports

## 3. Tests

- [ ] 3.1 `src/factory/create-jwt-tenant-resolver.test.ts`
- [ ] 3.2 `src/factory/create-jwt-tenant-resolver.spec-conformance.test.ts` — direct conformance
- [ ] 3.3 `src/proxy/create-jwt-tenant-resolver-worker-proxy.test.ts`
- [ ] 3.4 `src/proxy/create-jwt-tenant-resolver-worker-proxy.spec-conformance.test.ts` — proxy conformance
- [ ] 3.5 Every `it(...)` carries `{ timeout: 5000 }`

## 4. Documentation

- [ ] 4.1 Sibling `.md` per implementation `.ts`
- [ ] 4.2 README documents the chain interaction with header/subdomain resolvers (Stage 8 forward-reference)

## 5. Pre-archive verification (5-gate triple)

- [ ] 5.1 `bun run check` — clean
- [ ] 5.2 `bunx turbo lint typecheck test --filter=@suaveplan/api-tenant-resolver-jwt` — green
- [ ] 5.3 `bunx turbo test:coverage --filter=@suaveplan/api-tenant-resolver-jwt` — 100/100/100/100
- [ ] 5.4 `bun scripts/openspec-conformance.ts @suaveplan/api-tenant-resolver-jwt` — exit 0
- [ ] 5.5 `bunx turbo build --filter=@suaveplan/api-tenant-resolver-jwt` — green

## 6. Pre-archive 7-row checklist

- [ ] 6.1 `expectTypeOf` asserts the resolver returns `TenantId | undefined`
- [ ] 6.2 Zod schema at options boundary
- [ ] 6.3 Every `TENANT_JWT_*` code thrown by at least one production path
- [ ] 6.4 Strict-mode (`requirePrincipal`) tested both on and off
- [ ] 6.5 OTel instruments (`api.tenant.resolved_total{source=jwt,outcome}`) asserted with in-memory `MeterProvider`
- [ ] 6.6 Lifecycle dedup — N/A
- [ ] 6.7 No retroactive tick

## 7. Archive

- [ ] 7.1 Fold into `openspec/specs/api-tenant-resolver-jwt/spec.md`
- [ ] 7.2 Move to `openspec/archive/<yyyy-mm-dd>-api-tenant-resolver-jwt/`
- [ ] 7.3 Tick Stage 4 box in umbrella tasks
- [ ] 7.4 Refresh `MANIFEST.md`