# docs/archive/

One-off planning docs, session notes, and historical fix reports that
were load-bearing during their originating PR but aren't actively
referenced by ongoing work. Kept here (rather than deleted) so they
remain greppable for context on why a piece of code was written the
way it was.

If you find yourself reaching for one of these to understand current
code, consider whether the surfaced context belongs in a more
discoverable place (the originating issue, a comment near the relevant
code, or `docs/architecture/`).