Introducing Signal: documentation that lives in your code

I have a confession. I have shipped more than a few projects where the documentation was a lie. Not deliberately. Nobody sits down and thinks "I'll write docs that contradict my code." It happens gradually. You refactor a method, update the logic, rename a route, and the comment block at the top of the class quietly becomes fiction. The docs say one thing. The code does another. Whoever opens that file next, usually someone who isn't you, has to figure out which one to trust. I got tired of that