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.
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).
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.
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).
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.
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-badge every code page to bootstrap fadf745 Branches-and-workflow and Running-the-tests describe nothing the CONTRIBUTING.md change touched; the verified dates move to the day of the check.
Set the documentation format for building out the core Documentation-standards gains a system's page set (design, explanation hub, references, guides), generated reference for the code's registries, a Where the code lives table on every page with a ref badge and none on index pages, a path-based re-verify check, Home by area past twenty pages, and the three kinds of reader. Server-core-design gains the systems table that points at each system's current page. House style names messages with their opcode beside them. Home drops its ref badge; Running-the-tests, Codec-design and Roadmap gain their code tables.
Bring the wiki up to the codec's first stage at bootstrap 4bb1920 - Add the codec, its generator, their tests, the hot-path files and packages to the repository layout, with 206 tests. - Describe the hot-path tier as built: the switch, the ban list, the rules it raises, and where analysers stop. - Run the format check after the build everywhere, since it loads the generator. - Record the review's union selector and aligned blob rules, and move step 2 to stage 1 of 3.
Bring the pages up to the enforced build at bootstrap 490ed16 - Explain build enforcement, the pinned analysis level and every suppression with its reason. - List the commit message, em dash and format checks CI runs before the build, with fixes. - Use the renamed identifiers: ServerPathInitialize, HousingNeighborhoodInfoEntry. - Point the roadmap at run 38682391315, seven of seven on SDK 10.0.402.
Add the code standard, workflow, tests guide and repository layout - Explain the code standard's choices and why the build holds them. - Explain the branches, the dispatch-only test workflow and its guard rails. - Add a guide to running the tests locally and in CI, and a reference to every project, test and root file.