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.
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.
Document PlayerState at purpose, bootstrap 48bb36d 0x025E is PlayerState, verified to its purpose: the player's own values, kept apart from the unit, which the client doesn't need to finish entering the world. Roadmap no longer says it carries items and abilities. Reference pages regenerated; counts unchanged, run 39061867784.
Document the movement messages at bootstrap 1b7e100 Taking control, ending it and the zone change are verified to their fields, and the movement messages to their purpose. Client protocol walks the receipt, the zone change and movement after a grant; MovementInterval is the period of the client's movement timer, not how often it sends. 0x0635 is client to server only. Counts from run 39057431917: 51 read to fields, 1,068 unverified.
Compare the same bits on every path, at bootstrap cb7a9f0 The facts check now accepts a run of fields split differently from the client's when the totals meet and nothing depends on the split, and fails a message at fields that splits a value the client reads whole. 1,087 agree and 43 are pinned. Codec design and Message audit design carry the rule and the gate; counts from run 39054474869, 318 tests.
Document UnitCreate's members and PlayerUnit's faction refusal The reference pages are regenerated at bootstrap 7e90db0 with UnitCreate's members, stats and type arms documented. Client protocol and Roadmap say a PlayerUnit refused for a missing base faction still sets the player, so the client refuses every later one. Counts unchanged, run 39049099887.
Document TaggedMessage and correct which messages travel tagged 0x038C is TaggedMessage, verified to its fields: one message under a tag fixed by its opcode. The client sends tagged messages before the world as well as in it, and sends others on their own, so pregame isn't untagged as the pages said. What each tag stands for is our reading, not yet verified. Counts from run 39006780626: 48 read to fields, 1,071 unverified.
Document UnitCreate at purpose, bootstrap c136cc7 0x0262 is UnitCreate, verified to its purpose. The facts check treats two more pairs of forms as the same bits, which with three corrected arms settles 48 pins: 1,030 agree and 104 are pinned. The reference pages are regenerated; counts from run 39003475287, 289 tests.
Document LoginRequest at fields, bootstrap f1e5c15 LoginRequest is verified to its fields, so pregame has 41 of its 42. The reference pages are regenerated, which also corrects how many strings a realm notice carries. Client protocol says what the login request holds and drops its own trust row; counts from run 38973272246: 47 read to fields, 1,072 unverified.
Document world entry at bootstrap 7c68ecc Six world-entry messages verified to their fields: the reference pages regenerated, Client protocol follows the conversation to the end of the loading screen, and Roadmap's milestone one table takes their names and the client's WorldReady. Counts from run 38972717843: 273 tests, 46 read to fields, 1,073 unverified. Repository layout carries the reference tool's two new tests.
Publish the generated message reference at bootstrap 58cb3ba Messages and a page per area, generated by Tools/NexusTomorrow.ProtocolReference at 58cb3ba: 1,119 messages on 40 pages. Home, the sidebar, Client protocol, Codec design and Message audit design link it. Repository layout gains the Tools folder, the generator and its tests; the counts move to 271 tests in six applications. Code pages re-verified against 58cb3ba, run 38964363277.
Record the build reorder: step 2 closed, the audit alongside step 3 The codec's third stage closed after its review at c6b56e9, and the core skeleton starts on the messages already verified rather than after the whole audit, so the project can stop depending on the old server; milestone one's messages are checked first and the rest alongside the build. Roadmap marks step 2 done and step 3's pregame stage planned and waiting on review; the audit page records decision 2's change with its reason; Codec-design closes stage 3.
Re-verify against bootstrap c6b56e9, pins that carry their problem Each facts-check pin records the exact problem it covers, and the check fails when that text changes (run 38955532713, 263 of 263; counts unchanged).
Add Client protocol, the pregame conversation as far as it's verified An explanation page for how the 16042 client talks to a server: its three connections, the envelopes and keys, the greeting's build and protocol checks, and the pregame conversation from logging in through character select, realm select and transfers to entering the world, named by the verified declarations. Sign-on is labelled as carried over from the old code. Linked from Home, the sidebar, Roadmap and the audit page.
Record pregame done for milestone one, at bootstrap b9b7eea Character creation reaches Fields: 40 of pregame's 42 messages are verified to their fields (run 38939303230, 263 of 263; 40 read to fields, 1,079 unverified). LoginRequest stays at Purpose and 0x03EF unverified. Roadmap names milestone one's next areas.
Record the character list and world entry at Fields, at bootstrap 585b32a Pregame has 39 messages verified to their fields (run 38935110817, 263 of 263; 39 read to fields, 1,080 unverified); two stay at Purpose. EnterWorld's three floats are a point the world loads around, not the character's position, so milestone one's table says so.
Record pregame's value sets, 36 messages at Fields, at bootstrap 25218fd Checking the values the client's interface names raised twelve pregame messages to Fields; five stay at Purpose until both readings agree on their last fields (run 38925236863, 263 of 263; 36 read to fields, 1,083 unverified). The audit page states the rule for naming a value.
Correct the cross-build agreement after the facts table's fix The two clients' trees agree on 1,145 of 1,154 sides: correcting ten rows exposed a union in 0x098B, where the builds differ in one arm as well as in the two out-of-range selector values.
Publish the first verified area, pregame, at bootstrap cd601a0 41 pregame messages carry the names the client check gave them, 24 verified to their fields; the facts table corrected ten of its own rows, so 1,022 messages agree and 152 disagreements are pinned (run 38915570345, 263 of 263). Roadmap names EnterWorld in milestone one's table, Repository-layout and Codec-design name the shared and envelope messages, and the audit page states the two-reading rule and the progress line.
Re-verify against bootstrap 64dba89 at the close of the audit's full-layout step CI gains a method-words check beside the em dash scan; Code-standard, Repository-layout, Running-the-tests and Branches-and-workflow list it. Message-audit-design marks the full-layout step done after its review (run 38879621476, 263 of 263; 1,015 of 1,119 agree, 157 pinned, none verified yet).
Say where the audit's feature areas come from Areas come from the client feature each message serves; the client didn't allocate opcodes in feature blocks, so neither the opcode numbers nor the old code's folders draw the lines. The order after milestone one's areas is by size.
Describe the tree check and every message declared, at bootstrap 7072554 The facts check compares each declaration's full tree with the client's, names a disagreement by opcode, side and path, and treats two pairs of indistinguishable forms as equal; 157 disagreements are pinned. Every one of the client's 1,119 messages is declared, 1,015 agreeing with the client (run 38877202011, 263 of 263; it ran the identical tree of 7072554). The layout tree's union example is now a plain test layout, no longer tied to 0x01C3.
Describe the facts table's layout trees, at bootstrap bd2ec2c The client facts table is schema 2: every side carries the client's full layout tree, its widths come from the tree, and three client envelopes keep widths with no tree. The trees hold for both clients. The facts check still compares empty paths, at 873 agreeing and 55 pinned (run 38876037239, 252 of 252).
Describe the layout tree, at bootstrap 9f13a55 Codec-design gains the layout tree: its one-line text form, the node kinds, worked examples and how a disagreement's path is named, and the generator now emits each declared message's tree (WireLayout.TreeText and Tree, carried in WireLayoutData), held to the empty path the facts check proves. Message-audit-design marks the generator's trees built; Repository-layout and Roadmap take run 38863032351, 251 of 251.
Leave how feature areas are drawn open on the audit page The first area's messages don't all fall in one block of opcodes, so the boundary rule is still being settled; an area's name groups messages and claims nothing about them.
Re-verify against bootstrap cb985d3 with the stricter verification rules A message at Purpose needs a name of its own in place of its neutral number, and a member keeping its neutral name at Fields begins its summary with 'The client gives this value no meaning.' (run 38857101195, 224 of 224). The blame-ignore list now skips the neutral rename too.
Re-verify against bootstrap 2ee1445 at the close of the audit's first stage The verification check reads every wire member whatever its accessibility, across all three model projects (run 38855029660, 223 of 223).
Re-verify against bootstrap 9c93c58 with the wire models under the analysers Network.World and Network.Auth no longer opt out of the analysers, code style or nullable reference types, and nothing suppresses NTC003 or NTC006 (run 38852967763, 221 of 221). Code-standard loses three suppression rows and the nullable exception, Repository-layout its Off column and first known edge, Codec-design its NoWarn sentence; the audit's step 3 is marked done.