got a piece of feedback at work that i keep chewing on. i’d fixed some broken links on a site by hand. the reply was that the job wasn’t the links, it was a check at the hugo level that catches every dead link in the build.

so the fix is a symptom and the guard is the cure. a rule without a guard is a wish. if you want it held, put it in the harness: a linter in ci, a commit-msg hook, a build that fails loud instead of a page that quietly goes empty.

on the radium theme an errorf on a missing schema caught a publisher draft page exactly like that. the build found the bug, nobody’s eyes did.

honestly this is the real split between vibe coding and engineering. one clean line of code proves nothing. the question is whether the rule survives when you stop looking at it.