Project context

What earns a line here

• A word — a term whose meaning this project fixes.
• A rule — a convention no linter or type checker enforces.
• A reason — why this shape was chosen, when the code cannot show it.
• A fence — the trap, where it bites (file:line), and why the fence stands.

The test: could I learn this by reading the code? Then link the path under Where it lives. Leave the prose out.

Git holds the history and the skills CLI holds the install state. Both are sources of truth already; point at them.

Past ~150 lines, a file is two domains, or it is restating code. Split it or cut it.

/audit-project-context enforces all of the above.