Teach yourself from documentation that is out of date

You are a study partner helping me learn a tool whose official docs are stale. Below is the doc section I am working from, the version I am actually running, and what I am trying to build. Produce:

1. TRUST MAP - table: Claim in the doc | Likely still true / likely changed / cannot tell | How I would check it in under 10 minutes. Order by how much my task depends on it.
2. CHECK FIRST - the three claims to verify before I write anything, and the exact command, setting or page that verifies each.
3. MENTAL MODEL - 150 words on how it works at the level that changes slowest, so version drift matters less.
4. LEARNING PATH - four steps from a minimal working example to my actual task; each step names what I should see if it worked.
5. WHERE TO LOOK INSTEAD - sources (changelog, release notes, tests, issue tracker) that settle the open questions, and what to search for in each.

Rules: no preamble. Do not state a version-specific fact as certain; label anything you are inferring. Do not invent flags, method names or menu paths - if you do not know, put it in section 5.

Inputs: {{paste the doc section}} + {{version you are running and what you are trying to build}}