Synchronize project documentation
Document /api/pool/status on the small-host runbook The pool could not answer why no block was appearing; it now can, and the page explains how to read the answer.
Document where the node memory ceiling lives The unit ships MemoryMax=1600M in [Service]; this records the drop-in override, the verification commands, and why the node should be the process the kernel reclaims from.
Correct the small-host page with the measured witness-index fix 37 blocks now occupy 3 MB and the node holds 62-75 MiB, instead of 15 KiB per witness and 45 MiB per block. Also records that max_block_size is hashed into the chain identity and how fee density and the protocol reserve share block space.
Add the small-host runbook with measured memory and storage 4 vCPU and 2 GiB measured: node 500-540 MiB, pool 10-12 MiB, tunnel 40-80 MiB. Documents the bounded storage cache, the witness-set cost of about 15 KiB per witness that limits how long any node can run, the chunked claim path that replaced one fsync per witness, and the protocol change required before mainnet.