* Deep region and message pages, slow pool removed
* Deep pages: soften the sparse-filter claim, name commits by content
* Deep pages: typed ranges, the bounded message since, migration 059
* Deep pages: the typed range cap and its worst case, old since
The 2.1 section read as a series of releases, with advice that no longer
applies (waiting a week before index drops that were cut). Rewrite it as one
upgrade: before, upgrade, what happens and how long, after, rollback, with
the per-area detail kept as reference. Add the slow-disk fill pacing and the
connection count to the checklist.
* Document the slow pool, slow_pool_size, the lookup-table drops, the route column drop and sequence headroom
* Document the slow pool's default of 8 connections
Templates, contract, configuration, security and design docs now say 600.
Upgrading notes how to raise a pinned 300 and why the fail2ban flood jail
still sits above it.
* docs: move design and API contract into docs/
* docs: add releases and versioning page
* docs: add configuration reference for server and web
* docs: add reverse proxy page
* docs: add upgrading page
* docs: add operations page and move backup and profiling docs
* docs: add getting packets in and security pages
* docs: add troubleshooting page
* docs(api): fold admin, activity, route and summary notes into the contract
* docs(deploy): add type 2 split deployment, finish the beacon rename, ignore secrets
* docs: rewrite README as the front door and share the contributor workflow
* docs: remove em dashes from prose and config comments
* docs: apply review fixes to type 2, upgrading, troubleshooting and first-run notes
* docs: fix upgrade order, restore steps, type 2 setup and contract details from review
* docs: keep the gitignore to deployment secrets and runtime state
MrAlders0n