## Task 1: P1 Verify Reliability and failure-path coverage for GET /api/auth/[...nextauth]

**Title:** Verify Reliability and Failure-Path Coverage for `GET /api/auth/[...nextauth]`

**Priority:** P1

**Current Behavior:** See `technical-flow-dossier.full.jsonl.zst` at `the cited evidence boundary`; the complete source/path evidence remains outside this task.

**Why It Matters:** This source-bounded verification must determine whether reliability and failure-path coverage are satisfied without changing adjacent journeys.

**Required Changes:** Do not change repository code unless independent evidence confirms a scoped gap.

**Tests to Add or Update:** Run or add only the focused test that exercises this exact boundary.

**Commands to Run:**
- `npm run build`
- `npm run lint`

**Acceptance Criteria:**
- The cited evidence is inspected and the result is recorded as pass, partial, or fail.
- No unrelated source change is introduced.

**Limitations:** This task starts from an evidence-backed Senior Review priority. Verify the exact cited path before editing and stop when the evidence no longer matches.

---

## Task 2: P1 Verify Reliability and failure-path coverage for POST /api/forgot-password/reset

**Title:** Verify Reliability and Failure-Path Coverage for `POST /api/forgot-password/reset`

**Priority:** P1

**Current Behavior:** See `technical-flow-dossier.full.jsonl.zst` at `the cited evidence boundary`; the complete source/path evidence remains outside this task.

**Why It Matters:** This source-bounded verification must determine whether reliability and failure-path coverage are satisfied without changing adjacent journeys.

**Required Changes:** Do not change repository code unless independent evidence confirms a scoped gap.

**Tests to Add or Update:** Run or add only the focused test that exercises this exact boundary.

**Commands to Run:**
- `npm run build`
- `npm run lint`

**Acceptance Criteria:**
- The cited evidence is inspected and the result is recorded as pass, partial, or fail.
- No unrelated source change is introduced.

**Limitations:** This task starts from an evidence-backed Senior Review priority. Verify the exact cited path before editing and stop when the evidence no longer matches.

---

## Task 3: P1 Verify Reliability and failure-path coverage for POST /api/forgot-password/update

**Title:** Verify Reliability and Failure-Path Coverage for `POST /api/forgot-password/update`

**Priority:** P1

**Current Behavior:** See `technical-flow-dossier.full.jsonl.zst` at `the cited evidence boundary`; the complete source/path evidence remains outside this task.

**Why It Matters:** This source-bounded verification must determine whether reliability and failure-path coverage are satisfied without changing adjacent journeys.

**Required Changes:** Do not change repository code unless independent evidence confirms a scoped gap.

**Tests to Add or Update:** Run or add only the focused test that exercises this exact boundary.

**Commands to Run:**
- `npm run build`
- `npm run lint`

**Acceptance Criteria:**
- The cited evidence is inspected and the result is recorded as pass, partial, or fail.
- No unrelated source change is introduced.

**Limitations:** This task starts from an evidence-backed Senior Review priority. Verify the exact cited path before editing and stop when the evidence no longer matches.

## Task 4: P1 Verify Reliability and failure-path coverage for POST /api/forgot-password/verify-token

**Title:** Verify Reliability and Failure-Path Coverage for POST /api/forgot-password/verify-token

**Priority:** P1

**Current Behavior:** See `technical-flow-dossier.full.jsonl.zst` at `the cited evidence boundary`; the complete source/path evidence remains outside this task.

**Why It Matters:** This source-bounded verification must determine whether reliability and failure-path coverage are satisfied without changing adjacent journeys.

**Required Changes:** Do not change repository code unless independent evidence confirms a scoped gap.

**Tests to Add or Update:** Run or add only the focused test that exercises this exact boundary.

**Commands to Run:**
- `npm run build`
- `npm run lint`

**Acceptance Criteria:**
- The cited evidence is inspected and the result is recorded as pass, partial, or fail.
- No unrelated source change is introduced.

**Limitations:** This task starts from an evidence-backed Senior Review priority. Verify the exact cited path before editing and stop when the evidence no longer matches.

---

## Task 5: P1 Verify Reliability and failure-path coverage for POST /api/register

**Title:** Verify Reliability and Failure-Path Coverage for POST /api/register

**Priority:** P1

**Current Behavior:** See `technical-flow-dossier.full.jsonl.zst` at `the cited evidence boundary`; the complete source/path evidence remains outside this task.

**Why It Matters:** This source-bounded verification must determine whether reliability and failure-path coverage are satisfied without changing adjacent journeys.

**Required Changes:** Do not change repository code unless independent evidence confirms a scoped gap.

**Tests to Add or Update:** Run or add only the focused test that exercises this exact boundary.

**Commands to Run:**
- `npm run build`
- `npm run lint`

**Acceptance Criteria:**
- The cited evidence is inspected and the result is recorded as pass, partial, or fail.
- No unrelated source change is introduced.

**Limitations:** This task starts from an evidence-backed Senior Review priority. Verify the exact cited path before editing and stop when the evidence no longer matches.

---

## Task 6: P1 Verify Authentication: Reliability and failure path coverage

**Title:** Verify Reliability and Failure-Path Coverage for `sign_in` in Sign in flow

**Priority:** P1

**Current Behavior:** See `technical-flow-dossier.full.jsonl.zst` at `the cited evidence boundary`; the complete source/path evidence remains outside this task.

**Why It Matters:** This source-bounded verification must determine whether reliability and failure-path coverage are satisfied without changing adjacent journeys.

**Required Changes:** Do not change repository code unless independent evidence confirms a scoped gap.

**Tests to Add or Update:** Run or add only the focused test that exercises this exact boundary.

**Commands to Run:**
- `npm run build`
- `npm run lint`

**Acceptance Criteria:**
- The cited evidence is inspected and the result is recorded as pass, partial, or fail.
- No unrelated source change is introduced.

**Limitations:** This task starts from an evidence-backed Senior Review priority. Verify the exact cited path before editing and stop when the evidence no longer matches.

## Task 7: P1 Verify Reliability and failure-path coverage for sign_in in handleSubmit

**Title:** Verify Reliability and Failure-Path Coverage for `sign_in` in `handleSubmit`

**Priority:** P1

**Current Behavior:** See `technical-flow-dossier.full.jsonl.zst` at `the cited evidence boundary`; the complete source/path evidence remains outside this task.

**Why It Matters:** This source-bounded verification must determine whether reliability and failure-path coverage is satisfied without changing adjacent journeys.

**Required Changes:** Do not change repository code unless independent evidence confirms a scoped gap.

**Tests to Add or Update:** Run or add only the focused test that exercises this exact boundary.

**Commands to Run:**
- `npm run build`
- `npm run lint`

**Acceptance Criteria:**
- The cited evidence is inspected and the result is recorded as pass, partial, or fail.
- No unrelated source change is introduced.

**Limitations:** This task starts from an evidence-backed Senior Review priority. Verify the exact cited path before editing and stop when the evidence no longer matches.

---

## Task 8: P1 Verify Reliability and failure-path coverage for sign_in in loginUser

**Title:** Verify Reliability and Failure-Path Coverage for `sign_in` in `loginUser`

**Priority:** P1

**Current Behavior:** See `technical-flow-dossier.full.jsonl.zst` at `the cited evidence boundary`; the complete source/path evidence remains outside this task.

**Why It Matters:** This source-bounded verification must determine whether reliability and failure-path coverage is satisfied without changing adjacent journeys.

**Required Changes:** Do not change repository code unless independent evidence confirms a scoped gap.

**Tests to Add or Update:** Run or add only the focused test that exercises this exact boundary.

**Commands to Run:**
- `npm run build`
- `npm run lint`

**Acceptance Criteria:**
- The cited evidence is inspected and the result is recorded as pass, partial, or fail.
- No unrelated source change is introduced.

**Limitations:** This task starts from an evidence-backed Senior Review priority. Verify the exact cited path before editing and stop when the evidence no longer matches.

---

## Task 9: P1 Confirm production flow controls on the account registration endpoint

**Title:** Confirm Production Flow Controls on the Account Registration Endpoint

**Priority:** P1

**Current Behavior:** See `technical-flow-dossier.full.jsonl.zst` at `the cited evidence boundary`; the complete source/path evidence remains outside this task.

**Why It Matters:** The application handles account credentials; these controls affect whether the path behaves correctly when inputs, providers, or failures are unusual.

**Required Changes:** Do not change repository code unless independent evidence confirms a scoped gap.

**Tests to Add or Update:** Run or add only the focused test that exercises this exact boundary.

**Commands to Run:**
- `npm run test`

**Acceptance Criteria:**
- The cited evidence is inspected and the result is recorded as pass, partial, or fail.
- No unrelated source change is introduced.

**Limitations:**

## Task 10: P1 Verify Protected API: Authentication and access control

**Title:** Verify Protected API: Authentication and Access Control

**Priority:** P1

**Current Behavior:** See `technical-flow-dossier.full.jsonl.zst` at `the cited evidence boundary`; the complete source/path evidence remains outside this task.

**Why It Matters:** The application handles account credentials; these controls affect whether the path behaves correctly when inputs, providers, or failures are unusual.

**Required Changes:** Do not change repository code unless independent evidence confirms a scoped gap.

**Tests to Add or Update:** Run or add only the focused test that exercises this exact boundary.

**Commands to Run:** `npm run test`

**Acceptance Criteria:**
- The cited evidence is inspected and the result is recorded as pass, partial, or fail.
- No unrelated source change is introduced.

**Limitations:**
- Static CFG or direct data-flow coverage is insufficient to prove this path.
- Unresolved calls limit path completeness for this function.

---

## Task 11: P1 Verify Payment transaction: Flow controls

**Title:** Verify Payment Transaction: Flow Controls

**Priority:** P1

**Current Behavior:** See `technical-flow-dossier.full.jsonl.zst` at `the cited evidence boundary`; the complete source/path evidence remains outside this task.

**Why It Matters:** The application handles checkout and payment; these controls affect whether the path behaves correctly when inputs, providers, or failures are unusual.

**Required Changes:** Do not change repository code unless independent evidence confirms a scoped gap.

**Tests to Add or Update:** Run or add only the focused test that exercises this exact boundary.

**Commands to Run:** `npm run test`

**Acceptance Criteria:**
- The cited evidence is inspected and the result is recorded as pass, partial, or fail.
- No unrelated source change is introduced.

**Limitations:**
- Static CFG or direct data-flow coverage is insufficient to prove this path.
- Unresolved calls limit path completeness for this function.

---

## Task 12: P2 Verify Post api forgot password reset: Resource boundary

**Title:** Verify POST API Forgot Password Reset: Resource Boundary

**Priority:** P2

**Current Behavior:** See `technical-flow-dossier.full.jsonl.zst` at `the cited evidence boundary`; the complete source/path evidence remains outside this task.

**Why It Matters:** This source-bounded verification must determine whether Resource Boundary is satisfied without changing adjacent journeys.

**Required Changes:** Do not change repository code unless independent evidence confirms a scoped gap.

**Tests to Add or Update:** Run or add only the focused test that exercises this exact boundary.

**Commands to Run:** `npm run build`; `npm run lint`

**Acceptance Criteria:**
- The cited evidence is inspected and the result is recorded as pass, partial, or fail.
- No unrelated source change is introduced.

**Limitations:**
- This task starts from an evidence-backed Senior Review priority. Verify the exact cited path before editing and stop when the evidence no longer matches.

## Task 13: P2 Verify Senior review dependencies integrations:

**Title:** Verify Senior Review Dependencies Integrations

**Priority:** P2

**Current Behavior:** See `technical-flow-dossier.full.jsonl.zst` at `the cited evidence boundary`; the complete source/path evidence remains outside this task.

**Why It Matters:** This source-bounded verification must determine whether Dependencies integrations is satisfied without changing adjacent journeys.

**Required Changes:** Do not change repository code unless independent evidence confirms a scoped gap.

**Tests to Add or Update:** Run or add only the focused test that exercises this exact boundary.

**Commands to Run:**
- `npm run build`
- `npm run lint`

**Acceptance Criteria:**
- The cited evidence is inspected and the result is recorded as pass, partial, or fail.
- No unrelated source change is introduced.

**Limitations:** This task starts from an evidence-backed Senior Review priority. Verify the exact cited path before editing and stop when the evidence no longer matches.