Split persistence into its system page, references and what's left - Persistence explains one database, a schema per owner and the queue that keeps owners off it, and why - Persistence schemas and write-behind carry the facts, checked against bootstrap c3409ba - Persistence design keeps only what isn't built: content, load workers, change sets, transfers
Point the wiki at main, now that main has the work main was fast-forwarded to bootstrap at 3bdebd6, so every ref badge, the reference pages and the README and CONTRIBUTING links now name main. Roadmap says each step is done on main and one run-time check is still owed; Branches and workflow says what main now holds. Gateway and Running a server cover the debug-level message log. Counts from run 39087772844: 724 tests in 13 applications.
Document step 3's first stage as built, at bootstrap e8da4aa The real client logs in through our own server and creates a character. Host, Gateway, Owners, Persistence, Command layer and Harness each get an explanation page checked against the merged code, and Running a server is the guide to running it. The six design pages say their first stage is built and stay the direction for the rest. Repository layout, Running the tests, Roadmap, Client protocol and Server core design catch up; Home groups pages by area now the wiki is past twenty. Counts from run 39083384598: 718 tests in 13 applications.