No `.skip` patterns in shipping tests without justification

A .skip, xit, or xdescribe without a justifying comment is a permanently-disabled test. It stops failing in CI, the broken behavior it was covering goes undetected, and because nobody knows why it was skipped, nobody knows it's safe to re-enable. AI-generated test suites often skip tests for code paths that haven't been implemented yet and never re-enable them. Over time these accumulate into a graveyard of skipped tests that silently shrink effective test coverage. ISO-25010:2011 maintainability requires that disabled tests be traceable to a documented reason.

For every .skip call that has no comment above it and no justifying text in its name, either fix the underlying issue and re-enable it, or add a comment with a tracking issue and a target date. Never leave a skip anonymous:

// Before: permanently skipped, unknown reason
it.skip('creates a user', async () => { ... })

// After option A: fix and re-enable
it('creates a user', async () => {
  const user = await createUser({ email: 'a@b.com' })
  expect(user.id).toBeDefined()
})

// After option B: document the skip explicitly
// TODO(ISSUE-423): blocked on user service migration, re-enable by 2026-Q2
it.skip('creates a user (blocked on migration)', async () => { ... })