Inside the docs folder is an archive folder. Stale and completed plans and docs get moved there.
I generate a schema.md that describes the database schema in LLM-friendly terms that lives in docs.
If there's a gnarly design or implementation design made that the LLM keeps tripping up on, I get it to document that and put it in docs.
The handoff.md doc lives in docs, and gets moved to archive once it's no longer relevant. Same for todo.md
My agents.md instructs the LLM to read the docs but ignore the archive, and acknowledge the docs it has read. So the start of every session gets a "I have read <date>design.md, <date>plan.md, schema.md, notes.md, handoff.md". It's a decent chunk of context but as the OP says, this is necessary.
I also have a skill called "assessing project drift" that looks at the archive and assesses the project on how far the code has moved from the intention, if there are any chunks of code that were relevant but have been superceded and can be removed, and if there's any egregious tech debt that should be dealt with now. The docs archive is really useful for this.