reflock
activeA lockfile for cross-references: it flags a doc whose link still works but whose target has changed underneath it.
Why it exists
Link checkers catch a target that was moved or deleted. They miss the more common failure: the target still exists, but what it says has changed, so the doc citing it is now wrong. With agents rewriting docs and code all day, that rot piles up faster than anyone reviews it. reflock makes the check mechanical and unavoidable.
How it works
Each reference is pinned to a fingerprint of the smallest section it points at, so a typo fixed elsewhere raises no alarm. When that section changes, the reference is flagged as drifted; when it is gone, as dangling. A human or an agent re-reads both sides and re-blesses the pin.
- Mechanical, no model. No model and no network, so it is fast and predictable enough to gate commits, CI and an agent's end of turn. Judgment is only needed where something actually drifted.
- The pin lives at the reference, next to the link, so there is no central lockfile to fight over.
Where it stands
Versioned releases, installable via Homebrew or as a pre-commit hook, with one command to wire it into Claude Code as an end-of-turn gate.