Skip to content

test(device): extract phase reducer + 35 unit/integration tests - #6

Merged
Codehagen merged 3 commits into
mainfrom
feat/authorize-device-reducer-tests
Apr 17, 2026
Merged

Codehagen merged 3 commits into
mainfrom
feat/authorize-device-reducer-tests

Conversation

@Codehagen

@Codehagen Codehagen commented Apr 17, 2026 •

Copy link
Copy Markdown
Owner

Summary

Extracts the 8-phase `Phase` state machine from `AuthorizeDeviceClient` into a pure `phaseReducer` function, then adds 35 tests on top — 20 pure-function reducer tests (100% branch coverage) and 15 thin integration tests via React Testing Library + jsdom.

This was the 1A + 2C option from the /plan-eng-review on this task: refactor to `useReducer` first, then unit-test the reducer, then add a thin integration layer. Net result: higher coverage, faster tests, durable under future phase additions.

Why a refactor before tests?

The component originally used `useState` with ~7 scattered `setPhase` call sites across a `useEffect` and 4 async handlers. Testing that shape would have forced every transition through a full component render + DOM assertion, which couples tests to markup rather than logic. Extracting the reducer turned the transitions into a pure function — test surface dropped from "render a component and stub better-auth" to "call a function with an action and expect a state." Pure reducer tests run in sub-millisecond time and don't touch jsdom.

The component itself got simpler too: the `"Try again"` handler collapses from a duplicated derivation block into a single `dispatch({ type: "SESSION_RESOLVED", session, userCode })` — same logic path the effect uses.

What's tested

Reducer (20 tests, node env, <5ms each)

  • `SESSION_LOADING` from every prior phase → loading
  • `SESSION_RESOLVED`: empty userCode, null session, undefined session, null session.user, missing email, null email (regression: better-auth string|null), undefined email
  • `SESSION_RESOLVED` as the retry path: error → signed-in when session is valid, error → signed-out when session is gone
  • `MAGIC_LINK_SENT`, `APPROVE_STARTED`, `APPROVE_SUCCEEDED`, `DENIED`, `ERROR` (dispatchable from any phase)

Integration (15 tests, jsdom, ~80ms each)

  • Effect derivation wiring: loading, signed-out, signed-in
  • `providers` prop conditional render: both, one, none; copy flip `"new provider or email"` ↔ `"new email"`
  • Magic-link handler: success → email-sent, error response → error with server message
  • Social sign-in: calls `signIn.social` with preserved userCode callback; thrown error → error with message
  • Approve: success → approved screen; RFC `access_denied` → exact `error_description`; RFC error without description → generic fallback copy
  • Deny: throws are swallowed (best-effort), denied screen still renders
  • Try again: routes back to signed-in when session is still valid

Explicitly not tested

  • E2E via Playwright — OAuth cross-origin redirects can't be unit-tested
  • Better Auth plugin internals — owned upstream
  • Visual regression — no Chromatic/Percy in this repo yet

Files

  • `apps/web/app/device/phase-reducer.ts` — pure module, Phase + PhaseAction + `phaseReducer` + ASCII state diagram
  • `apps/web/app/device/phase-reducer.test.ts` — 20 pure unit tests, node env
  • `apps/web/app/device/AuthorizeDeviceClient.tsx` — `useReducer` instead of `useState`; dispatch sites replace `setPhase`; "Try again" collapses to one dispatch
  • `apps/web/app/device/AuthorizeDeviceClient.test.tsx` — 15 integration tests, jsdom env via file-level pragma
  • `apps/web/vitest.config.ts` — new config wiring `@vitejs/plugin-react` for JSX transform + `@/*` path alias; default env stays node
  • `apps/web/package.json` — adds `jsdom`, `@testing-library/react`, `@testing-library/user-event`, `@testing-library/jest-dom`, `@vitejs/plugin-react` (all dev)

Test plan

  • `pnpm -F web typecheck` clean
  • `pnpm -F web test` — 86 tests pass (was 51; +35 new)
  • `pnpm sync:templates` — no drift (`app/device/` stays in `HOSTED_TIER_EXCLUDES`, tests don't leak into scaffolder)
  • Vercel preview deploy green
  • Manual regression: sign out → `helpbase login` → OAuth + magic-link flows still work in the browser

🤖 Generated with Claude Code

Summary by CodeRabbit

  • Tests

    • Added comprehensive test coverage for device authorization flow, including state transitions, user interactions, and error scenarios.
    • Established testing infrastructure with Vitest and React Testing Library.
  • Chores

    • Added testing dependencies and Vitest configuration for the web application.

Pulls the Phase union and transition logic out of
AuthorizeDeviceClient into a pure `phaseReducer(state, action)` so
the state machine can be tested without React, the DOM, or
better-auth mocks. Component now calls `useReducer(phaseReducer,
initialPhase)` and dispatches actions from handlers + the
derivation effect.

- apps/web/app/device/phase-reducer.ts — new pure module with the
  Phase union, PhaseAction union, `phaseReducer`, and state
  machine ASCII diagram as the file header
- apps/web/app/device/phase-reducer.test.ts — 20 unit tests,
  100% branch coverage of transitions including the
  `email ?? ""` regression from PR #3 review
- apps/web/app/device/AuthorizeDeviceClient.tsx — switches to
  useReducer; "Try again" button collapses to a single
  SESSION_RESOLVED dispatch (no duplicated derivation logic)
- apps/web/app/device/AuthorizeDeviceClient.test.tsx — 15 thin
  integration tests via @testing-library/react + jsdom covering
  the effect wiring, providers-prop conditional render, and
  async handler dispatch sites
- apps/web/vitest.config.ts — new config wiring
  @vitejs/plugin-react for JSX transform + `@/*` alias. Default
  env stays node; integration test opts into jsdom via
  `/* @vitest-environment jsdom */`
- apps/web/package.json — jsdom, @testing-library/{react,
  user-event, jest-dom}, @vitejs/plugin-react (dev deps)

Result: 86 web tests pass (was 51). +35 new tests in <1s,
typecheck clean.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@vercel

vercel Bot commented Apr 17, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
helpbase Ready Ready Preview, Comment Apr 17, 2026 7:54pm

Request Review

@coderabbitai

coderabbitai Bot commented Apr 17, 2026 •

Copy link
Copy Markdown

Warning

Rate limit exceeded

@Codehagen has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 42 minutes and 39 seconds before requesting another review.

Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 42 minutes and 39 seconds.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 05b266cd-ba0e-4577-b5e0-440eabf3e483

📥 Commits

Reviewing files that changed from the base of the PR and between 6666ff0 and 33e6aff.

📒 Files selected for processing (4)
  • apps/web/app/device/AuthorizeDeviceClient.test.tsx
  • apps/web/app/device/phase-reducer.test.ts
  • apps/web/app/device/phase-reducer.ts
  • package.json
📝 Walkthrough

Walkthrough

This PR extracts a pure state machine (phaseReducer) from the AuthorizeDeviceClient component to enable testability without React/DOM mocking. It adds comprehensive unit tests for the reducer, integration tests for the component, and configures Vitest with jsdom for React component testing in apps/web.

Changes

Cohort / File(s) Summary
State Machine Reducer
apps/web/app/device/phase-reducer.ts, apps/web/app/device/phase-reducer.test.ts
New pure state machine with Phase union type and phaseReducer function handling 7 action types. Comprehensive test suite covering all transitions, edge cases (null/undefined coalescing), and retry flows across all 8 phase variants.
Component Refactoring
apps/web/app/device/AuthorizeDeviceClient.tsx
Replaced useState-based phase management with useReducer(phaseReducer, initialPhase). Updated session resolution, error handling, and state transitions to dispatch reducer actions instead of calling setPhase directly.
Component Integration Tests
apps/web/app/device/AuthorizeDeviceClient.test.tsx
New comprehensive test suite covering session states (loading/signed-out/signed-in), provider prop visibility, magic-link flow with success/error cases, social sign-in with error handling, device approval/denial, and retry behavior. Mocks better-auth and related plugins.
Testing Infrastructure
apps/web/vitest.config.ts, apps/web/package.json
Added Vitest config with React plugin and path alias mapping (@ → apps/web). Added testing dev dependencies: @testing-library/react, @testing-library/jest-dom, @testing-library/user-event, jsdom, and @vitejs/plugin-react.
Documentation
CHANGELOG.md
Added Unreleased entry documenting the reducer extraction, test coverage additions, and Vite React + jsdom harness setup.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Possibly related PRs

Poem

🐰 A reducer hops forth, pure and clean,
No mocks of React in between,
Phase transitions tested with care,
State logic extracted with flair!
The component now lighter, the tests more fair! ✨

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Docstring Coverage ⚠️ Warning Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Write docstrings for the functions missing them to satisfy the coverage threshold.
✅ Passed checks (2 passed)
Check name Status Explanation
Title check ✅ Passed The title accurately and concisely summarizes the main change: extracting a phase reducer and adding 35 unit/integration tests, which aligns with the core refactoring and testing work described throughout the changeset.
Description check ✅ Passed The description is comprehensive and well-structured, covering motivation, technical approach, test coverage details, and files changed. It follows the template's Summary and Testing sections with clear explanations of what was changed and why.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch feat/authorize-device-reducer-tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

🧹 Nitpick comments (3)
apps/web/app/device/phase-reducer.ts (1)

6-29: Nit: the ASCII diagram has a few mis-aligned arrows/boxes.

The approving box at line 17 is indented inconsistently with the arrow from signed-out, and a couple of stray | segments (lines 9, 19) don't connect to anything. Legible, but a quick pass to tidy would make this a reliable source of truth for future contributors. Skip if you'd rather not spend time on it.

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@apps/web/app/device/phase-reducer.ts` around lines 6 - 29, The ASCII state
diagram in phase-reducer.ts has misaligned elements: move the "approving" box so
its left edge aligns under the arrow coming from "signed-out" (so the
device.approve arrow cleanly points into the box), remove the stray vertical bar
segments that don't connect (the orphaned '|' near the top and near
"approving"), and tidy spacing/indentation for the surrounding boxes
("signed-out", "approving", "approved") so arrows line up visually and the
diagram remains a clear source of truth for the device phase states.
apps/web/vitest.config.ts (1)

3-3: Optional: prefer import.meta.dirname over __dirname in this ESM config.

apps/web/package.json sets "type": "module", so __dirname is not a native ESM global — it works here only because Vite transpiles the TS config through esbuild's CJS shim. Given @vitejs/plugin-react@6 already requires Node ≥20.19, you can drop the node:path import and use the built-in import.meta.dirname for a cleaner ESM-native config.

♻️ Proposed refactor
 import { defineConfig } from "vitest/config"
 import react from "@vitejs/plugin-react"
-import path from "node:path"

 // Vitest 4's default pipeline doesn't transform JSX in .tsx test files —
 // `@vitejs/plugin-react` wires up the automatic JSX runtime so component
 // tests like app/device/AuthorizeDeviceClient.test.tsx parse cleanly.
 // Test environment defaults to node (fast); jsdom-dependent files set
 // it per-file with a `/* `@vitest-environment` jsdom */` comment.
 export default defineConfig({
   plugins: [react()],
   resolve: {
     alias: {
-      "@": path.resolve(__dirname, "."),
+      "@": import.meta.dirname,
     },
   },
 })

Also applies to: 14-14

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@apps/web/vitest.config.ts` at line 3, The config imports "node:path" and uses
__dirname which is a CJS shim; remove the node:path import and replace usages of
__dirname with the ESM-native import.meta.dirname, e.g. compute paths via new
URL('.', import.meta.url).pathname or use import.meta.dirname (Node ≥20.19)
where the code currently references __dirname so the TS/Vite config is fully
ESM-native.
apps/web/app/device/AuthorizeDeviceClient.test.tsx (1)

130-147: Copy-matched assertions are tightly coupled to UI strings.

/new provider or email/i and /new email creates one/i both key off the exact phrasing in AuthorizeDeviceClient.tsx line 207-208. That's fine today, but any copy tweak (e.g., product asks for "Signing up") will break these tests with a confusing failure. Consider either asserting on a more stable anchor (e.g., presence/absence of the divider element) or extracting the string to a constant the test imports. Not blocking.

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@apps/web/app/device/AuthorizeDeviceClient.test.tsx` around lines 130 - 147,
The test is brittle because it asserts on exact copy strings from the
AuthorizeDeviceClient component; update AuthorizeDeviceClient.test.tsx to use a
more stable anchor instead—either assert on the divider element (e.g.,
queryByRole or getByTestId for the divider) to confirm visibility/absence of the
OAuth section or export the copy constant from AuthorizeDeviceClient and import
it into the test to compare against that constant; adjust the assertions around
screen.getByText(/new email creates one/i) and screen.getByText(/new provider or
email/i) to use the chosen stable selector (divider test id/role) or the
imported constant accordingly while leaving the render( <AuthorizeDeviceClient
... /> ) and provider fixtures (noProviders) unchanged.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@apps/web/app/device/AuthorizeDeviceClient.tsx`:
- Around line 31-49: The effect is re-triggering because the session object
reference is unstable; stabilize it before dispatching SESSION_RESOLVED by
memoizing the session (e.g., with useMemo or a small hook) and use that
stableSession in the useEffect dependency array instead of raw session, or
alternatively add a guard in phaseReducer to ignore SESSION_RESOLVED when
current phase is an in-progress auth state like "email-sent" or "approving";
update the useEffect that currently calls dispatch({ type: "SESSION_RESOLVED",
session, userCode }) to use the stableSession and keep dependencies to
[sessionPending, stableSession, userCode], and/or add the guard in phaseReducer
to avoid overwriting those phases.

In `@apps/web/package.json`:
- Around line 48-59: Update the package.json engines constraint to match
`@vitejs/plugin-react`@6.0.1's required Node floor: locate the "engines" field in
package.json (root/apps/web package.json) and change the node entry to
">=20.19.0 || >=22.12.0" so the engines block enforces the correct minimum Node
versions for functions that reference `@vitejs/plugin-react` (e.g., dev/build
scripts).

---

Nitpick comments:
In `@apps/web/app/device/AuthorizeDeviceClient.test.tsx`:
- Around line 130-147: The test is brittle because it asserts on exact copy
strings from the AuthorizeDeviceClient component; update
AuthorizeDeviceClient.test.tsx to use a more stable anchor instead—either assert
on the divider element (e.g., queryByRole or getByTestId for the divider) to
confirm visibility/absence of the OAuth section or export the copy constant from
AuthorizeDeviceClient and import it into the test to compare against that
constant; adjust the assertions around screen.getByText(/new email creates
one/i) and screen.getByText(/new provider or email/i) to use the chosen stable
selector (divider test id/role) or the imported constant accordingly while
leaving the render( <AuthorizeDeviceClient ... /> ) and provider fixtures
(noProviders) unchanged.

In `@apps/web/app/device/phase-reducer.ts`:
- Around line 6-29: The ASCII state diagram in phase-reducer.ts has misaligned
elements: move the "approving" box so its left edge aligns under the arrow
coming from "signed-out" (so the device.approve arrow cleanly points into the
box), remove the stray vertical bar segments that don't connect (the orphaned
'|' near the top and near "approving"), and tidy spacing/indentation for the
surrounding boxes ("signed-out", "approving", "approved") so arrows line up
visually and the diagram remains a clear source of truth for the device phase
states.

In `@apps/web/vitest.config.ts`:
- Line 3: The config imports "node:path" and uses __dirname which is a CJS shim;
remove the node:path import and replace usages of __dirname with the ESM-native
import.meta.dirname, e.g. compute paths via new URL('.',
import.meta.url).pathname or use import.meta.dirname (Node ≥20.19) where the
code currently references __dirname so the TS/Vite config is fully ESM-native.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: d902b02c-8450-4621-9bf8-f45a5d7f7634

📥 Commits

Reviewing files that changed from the base of the PR and between 42b3785 and 6666ff0.

⛔ Files ignored due to path filters (1)
  • pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml
📒 Files selected for processing (7)
  • CHANGELOG.md
  • apps/web/app/device/AuthorizeDeviceClient.test.tsx
  • apps/web/app/device/AuthorizeDeviceClient.tsx
  • apps/web/app/device/phase-reducer.test.ts
  • apps/web/app/device/phase-reducer.ts
  • apps/web/package.json
  • apps/web/vitest.config.ts

Comment thread apps/web/package.json
Comment on lines +48 to +59
"@testing-library/jest-dom": "^6.9.1",
"@testing-library/react": "^16.3.2",
"@testing-library/user-event": "^14.6.1",
"@types/node": "^25.1.0",
"@types/pg": "^8.20.0",
"@types/react": "^19.2.10",
"@types/react-dom": "^19.2.3",
"@vitejs/plugin-react": "^6.0.1",
"@workspace/eslint-config": "workspace:^",
"@workspace/typescript-config": "workspace:*",
"eslint": "^9.39.2",
"jsdom": "^29.0.2",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Verify resolved vite/vitest versions and Node engines compatibility.
fd -t f 'pnpm-lock.yaml|package-lock.json|yarn.lock' --max-depth 3 | head -5
rg -n -C1 '"vite"|"vitest"' --type=json -g '!**/node_modules/**' apps/web package.json 2>/dev/null
fd -t f 'package.json' --max-depth 2 -x grep -l '"engines"' {} \; | head
cat package.json 2>/dev/null | jq '.engines // {}' 2>/dev/null
rg -n -C2 '^\s*"(vite|vitest)"' pnpm-lock.yaml 2>/dev/null | head -40

Repository: Codehagen/helpbase

Length of output: 215


🏁 Script executed:

# Get resolved Vite version from pnpm-lock.yaml
rg -A 5 "^\s+vite:" pnpm-lock.yaml | head -30

# Check if apps/web has explicit vite or vitest deps
cat apps/web/package.json | grep -E '"(vite|vitest)"' || echo "No vite/vitest in apps/web/package.json"

# Look for CI config files
fd -t f '\.github|\.gitlab-ci|\.circleci|\.travis' --max-depth 2

# Find Node version in CI files
fd -t f -e yml -e yaml | head -10 | xargs grep -l "node" 2>/dev/null || echo "Searching..."

Repository: Codehagen/helpbase

Length of output: 959


🏁 Script executed:

# Check Node version in CI workflows
find .github/workflows -name "*.yml" -o -name "*.yaml" 2>/dev/null | xargs grep -i "node" 2>/dev/null | head -20

# Also check root for Node engine spec
cat package.json | jq '.engines'

# Verify `@vitejs/plugin-react` 6.0.1 peer dependency requirements
rg -A 10 '@vitejs/plugin-react' pnpm-lock.yaml | head -50

Repository: Codehagen/helpbase

Length of output: 1771


Update root package.json engines to enforce the Node version floor required by @vitejs/plugin-react@6.0.1.

@vitejs/plugin-react@6.0.1 requires node: ^20.19.0 || >=22.12.0, but package.json only specifies ">=20", which is too loose. The resolved Vite 8.0.7, Vitest 4.1.3, and all testing library deps are compatible with React 19.2.4 — however, the engines constraint should be tightened in the root package.json to reflect this requirement. Update to "engines": { "node": ">=20.19.0 || >=22.12.0" } to match the plugin's documented floor.

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@apps/web/package.json` around lines 48 - 59, Update the package.json engines
constraint to match `@vitejs/plugin-react`@6.0.1's required Node floor: locate the
"engines" field in package.json (root/apps/web package.json) and change the node
entry to ">=20.19.0 || >=22.12.0" so the engines block enforces the correct
minimum Node versions for functions that reference `@vitejs/plugin-react` (e.g.,
dev/build scripts).

…sed, 1 TODO filed

Pre-landing review surfaced 12 findings across testing + adversarial
specialists. Applied all the ones worth fixing in this PR:

Auto-fixes (mechanical):
- phase-reducer.ts: freeze initialPhase + type as Readonly<Phase> so
  the exported reference can't be accidentally mutated
- AuthorizeDeviceClient.test.tsx: tighten /check/i regex to
  /for your.*sign-in link/i — prior matcher also matched "Checking
  session…" on the loading screen
- phase-reducer.test.ts: rename and re-purpose the misleading
  "empty userCode + null session" case to assert the guard ordering
  (userCode check fires before session check)

New coverage (ASK items approved):
- AuthorizeDeviceClient.test.tsx: assert Cancel button is disabled
  while approve is in flight. Without this, removing
  `disabled={approving}` from Cancel would silently break the
  "can't deny mid-approve" invariant.
- AuthorizeDeviceClient.test.tsx: assert all sign-in surfaces
  (GitHub button, email submit) disable while a social redirect is
  in flight. Prevents concurrent OAuth redirects from a
  double-click.

Filed TODO-021 for a pre-existing bug the adversarial review
surfaced: `SESSION_LOADING` clobbers non-loading phases, so a
background Better Auth session refresh wipes `email-sent` back to
the spinner. Not introduced by this refactor; worth a standalone
follow-up.

Tests: 88 pass (was 86; +2 new). Typecheck clean.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
CodeRabbit flagged a real regression path (confirmed with upstream
bug reports): better-auth's useSession() doesn't memoize its return,
so any re-render can re-fire the derivation effect even when session
data is unchanged. Without a guard, a user watching "Check your
email" gets bounced to the sign-in form when the session reference
updates.

Fix: SESSION_LOADING and SESSION_RESOLVED now only apply when the
current phase is derivable (loading / signed-out / signed-in /
error). In-progress and terminal phases (email-sent, approving,
approved, denied) ignore background session refreshes.

- phase-reducer.ts: `isDerivable()` helper + guard in both
  SESSION_* branches. Error intentionally stays derivable so
  "Try again" still routes correctly.
- phase-reducer.test.ts: +2 tests asserting preservation of
  email-sent/approving/approved/denied across SESSION_LOADING
  and SESSION_RESOLVED
- package.json: bump Node engines floor to
  `^20.19.0 || >=22.12.0` per @vitejs/plugin-react@6.0.1
- TODOS.md: drop TODO-021 (closed by this commit)

Tests: 90 pass (was 88). Typecheck clean.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@Codehagen
Codehagen merged commit da7433b into main Apr 17, 2026
3 of 5 checks passed
@Codehagen
Codehagen deleted the feat/authorize-device-reducer-tests branch April 17, 2026 19:53

This branch was successfully deployed

1 active deployment
Preview — 33e6affb Deployed Apr 17, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant