Split the gateway into its system page, references and what's left to build - Gateway explains how the ports, connections and gate fit together and why - Gateway connections, sign-on, gate and limits carry the facts to look up, checked against bootstrap c3409ba - Gateway design keeps only what isn't built: tagged routing, the member gates, the full opcode table, the operations sink - Home, the sidebar and links to moved sections point at them
Add the generated opcode table and commands pages, bootstrap efc697d - Gateway-opcode-table and Command-layer-commands, generated from the opcode table and the server's command list - Command layer's hand-kept table and Gateway's opcode paragraph point at them; Home, the sidebar and Running a server link both - Regenerate the message pages at efc697d; 742 of 742 in run 39092971388
Regenerate the reference by the client's feature areas, bootstrap 029ceb6 Every world message now sits in the folder of the client feature it serves: 49 areas, with 127 messages still unsettled. The reference has a page per area and no Unsorted page. World entry's messages are on WorldEntry, Entity, Movement and PlayerPath, and the tagged wrapper on Connection. Counts from run 39091424166: 733 tests.
Record the verified-address answer and ClientConnector's folder fix Sign-on now answers the client's request for its verified addresses with an empty list, so the client no longer reconnects after login. ClientConnector finds the client and its settings beside itself however it's started. Re-verified against bootstrap 8b753e2, run 39089128777: 731 tests.
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.
Record the per-member gate for sending A message may be sent once it's at Purpose and every member the server sets is verified, the rest going as defaults; handling a client message still needs Fields. Decided 2026-10-18 and built with the map side, so the gateway still sends only at Fields until then. Message audit design also takes the client-identifier rule for naming values.
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.