Record a project note

Capture useful project knowledge that doesn't fit a more specific type. Notes are the catch-all bucket — lower-signal than decisions, but still worth keeping. Aha moments, TILs, gotchas, code smells, and durable TODOs all live here.

When to fire

• You discovered a non-obvious thing about the codebase ("cargo test --workspace triggers FTS triggers in tmpdir-shaped tests").
• You found a workaround for a tool quirk.
• You hit an "aha" — surprising behaviour, broken assumption, root cause after debugging.
• You're flagging a code smell or refactor candidate that should outlive this session.
• The user said "jot this down" / "note that" / "worth recording" without naming it a decision.

Tie-breakers vs siblings:

• Note vs decision — does it carry a commitment with a why? If yes, vestige-record-decision.
• Note vs preference — is it a user opinion / convention? If yes, vestige-record-preference.
• Note vs question — is the answer known? If no, vestige-record-question.

How to invoke