A tool checks whether code changes make docs stale

A new tool checks whether documentation still matches the code it describes. A team can connect specific claims in a document to exact code areas, such as a token refresh function or authentication middleware. When that code changes, the tool decides whether the meaning changed or whether the edit was harmless.

Added comments, renamed variables, and formatting changes pass. A changed comparison rule or an added or removed await fails because it may change behavior. The tool works with fixed rules only, without models, embeddings, API keys, or network calls.

The goal is to stop shared project context from becoming wrong as more engineers and agents work in the same codebase.