Test bodies are not empty or TODO-only

An empty it('creates a user', () => {}) body or one containing only // TODO passes unconditionally in every test runner — it shows green in CI, increments the test count, and contributes nothing. AI coding tools scaffold test stubs frequently and treat them as "complete" once the file is syntactically valid. The downstream effect: the team believes behavior is tested when it isn't, and a growing backlog of TODO-only tests never gets implemented because they never fail to remind anyone. ISO-25010:2011 testability requires that tests verify actual behavior.

Implement or delete every empty or TODO-only test body. Use it.todo() instead of it('name', () => { /* TODO */ }) — it.todo is semantically correct and most runners surface it as a pending test rather than a pass:

// Before: passes silently, zero verification
it('creates a user', () => {})
it('verifies password', () => { /* TODO */ })

// After option A: implement with real assertions
it('creates a user', async () => {
  const user = await createUser({ email: 'a@b.com' })
  expect(user.id).toBeDefined()
})

// After option B: mark as genuinely pending
it.todo('creates a user') // shown as pending in vitest/jest output, not a pass