Cull tests

Agents pad test suites. They write tests that confirm a feature exists, that a type already proves, that a button is on the page, or that a mocked API still returns the mock. Those tests pass forever and catch nothing. This skill deletes them and keeps the ones that would still fail if someone rewrote the product from scratch.

The starting cull list is from Howaboua. The bar is Ian's: if you handed only the surviving tests to an agent and said "rebuild this," would it ship the real product?

Do this

1. List the test files you will touch. Do not scan the whole monorepo unless asked.
2. For each test, name the behaviour it would catch if that behaviour broke. If you cannot name one in a sentence, it is a delete.
3. Show a kill list and a keep list before you edit. Wait if the user wants to review. Otherwise delete the kill list and stop.
4. Do not rewrite the kept tests in the same pass. Do not add new tests unless the user asked for replacements.

Delete