Learn With Docs Refresh

Every learning in docs/solutions/ should still be true and still distinct. Check each one against the current code, apply what the evidence supports, and deliver a full per-doc report plus a commit. The store is only worth reading if every doc in it can be trusted.

Hard boundaries

• Never change product code, skills, runbooks, or instruction files (except the consented discoverability line). When code violates guidance that has independent support, the guidance stays and the conflict goes in the report as a possible regression.
• Never archive. No _archived/, no redirect stubs — git history is the archive.
• Act on contradiction, not on absence. A claim the repo cannot confirm (an ops practice, an environment behavior) is not false. Age alone is not staleness.
• No churn. Never edit for typos, wording, or style alone.

Paths