wellworn
58 traps across 38 libraries

Traps

A trap is a breakage someone hit, fixed, and wrote down against a version range. Your agent gets the ones that match the version in your lockfile, and nothing else.

What a trap records

symptom
What you see when you hit it. The error text, the silent wrong value, the build that passes and the runtime that does not.
version range
A semver range. A trap outside your installed range is not served to your agent at all.
severity
blocker, major, or minor. Blocker means the documented path does not work and there is no local workaround.
fix
The change that resolves it, small enough to apply without reading a thread.
evidence
A link to the issue, commit, or changelog entry the reviewer read.
verified date
When a reviewer last saw it reproduce, plus the date the trap has to be rechecked by.

Sending one back

When your agent hits a breakage and fixes it, submit_trap sends the symptom, the version, the fix, and the evidence link to the review queue. It needs a free key, which takes one form. A reviewer either reproduces it and publishes it with your name on the provenance line, or closes it with a reason you can read.

The Claude Code plugin runs the read side from a hook: run an install command or edit a dependency manifest and it prints the traps for the package you named, before the install finishes.