docs/ has no entry point for a successor operator

[Gerrrt]

The runbooks under docs/runbooks/ are written for someone competent who doesn't know this estate — which is the right reader, and they're good at it. But nothing in the repo actually addresses that person. There's no page saying what this estate is, what to check on day one, or which runbook to open in what order.

That's the difference between "the documentation is good" and "someone else could pick this up."

It matters because of where the alternative currently points: Gerrrt/Lemmiwinks was built to let the family operate the estate, and it can't — that audience can't run pfSense and VLANs from a wiki (Gerrrt/Lemmiwinks#7). The realistic reader for deep operational docs is a technical trustee or a paid MSP arriving cold. This repo is where they'd land, and it has no front door.

One page — docs/runbooks/successor-handover.md, or a README section

• What the estate is, in a paragraph: pfSense on morpheus, six VLANs, one compose stack on prometheus, SNMP and log-based observability.
• What to check first, in order.
• What fails soonest if nobody touches anything — TLS expiry, the UPS battery (Replace the UPS battery, then delete the silence and enable scheduled self-tests #93), and the fact that nothing schedules any backup, digest check or key verification (Nothing schedules any backup, digest check or key verification #77). This is the section that matters most and the one that doesn't exist anywhere today.
• Where the secrets are and what's needed to decrypt them — noting The age key has one holder and one copy #106, since a successor who can't decrypt has nothing.
• What can be switched off without consequence, and what can't.

Almost all the content already exists, spread across the runbooks and the nine ADRs. What's missing is the single page that orders it for someone who arrives without the context — and an explicit note that this repo, not the wiki, is the operator-facing one.