test(emailAuth): add unit tests for success flows and conflict paths

[Copilot]

The emailAuth route tests only covered validation/error paths, leaving the primary success flows and conflict cases untested.

Changes

• Refactored mock setup — replaced inline vi.fn() chains with vi.hoisted()-extracted handles (mockLimit, mockVerifyPassword, mockInsertValues) so individual tests can override return values via mockResolvedValueOnce

• Added missing test cases:

  • POST /auth/login — user found but password wrong → 401
  • POST /auth/login — valid credentials → 302 to /
  • POST /auth/register — email already in DB → 409
  • POST /auth/register — all valid → 302 to /, asserts db.insert().values() called

it("should redirect to / on successful login", async () => {
  mockLimit.mockResolvedValueOnce([{ email: "user@example.com", name: "Test User", passwordHash: "salt:hash" }]);
  mockVerifyPassword.mockResolvedValueOnce(true);
  // ...
  expect(response.status).toBe(302);
  expect(response.headers.get("Location")).toBe("/");
});

---

💬 Send tasks to Copilot coding agent from Slack and Teams to turn conversations into code. Copilot posts an update in your thread when it's finished.