Update the Wiki for 1.2.0-RC1 Pin every page, link, and banner to the v1.2.0-RC1 tag instead of 7faaf4f05, and point Getting started at the RC1 artifacts on Maven Central instead of the snapshot repository. Describe the behavior that changed between the old baseline and RC1: AddressSpace browses now fail on a Bad Browse or BrowseNext result, Writes check the value shape for every ValueRank, attribute reads no longer take the node lock, connection limits can be set with system properties, and sampling groups can run on their own executor. Add these and the smaller RC1 changes to the 1.2.0 migration guide. Signed-off-by: Kevin Herron <kevinherron@gmail.com>
Frame the 1.2.0 migration guide around 1.1.x
Lock the AdjustSetpoint update and keep GDS chains Describe the hardened thermostat and client samples, and point the sample links at the commit that carries them. Signed-off-by: Kevin Herron <kevinherron@gmail.com>
Restructure the Wiki as a guide Give each page one role and a path to the next. Task pages explain the model before the rules, walk the common path with a running example, gather failures in one place, and end with next steps in sidebar order. The sidebar now lists every page in learning order, and the hub pages describe their sections in the same order. The tutorial server becomes a small thermostat that the client and server guides build on, and the code samples read like application code. Every renamed heading keeps its old anchor, and the sample links point at the source commit that carries the matching code. Signed-off-by: Kevin Herron <kevinherron@gmail.com>
Point code samples at the compiled snippet sources Mark each Java block backed by milo-wiki-examples with a snippet comment so sync_snippets.py can refresh or check it. Replace the runnable-fixture links with links to the snippet classes, and drop or restate prose that cited the removed fixtures and migration projects. Signed-off-by: Kevin Herron <kevinherron@gmail.com>
Restore the history page-budget check The readRawHistory sample rejects a nonpositive maxPages again. Point the fixture links at the commit that carries the matching code. Signed-off-by: Kevin Herron <kevinherron@gmail.com>
Rewrite the prose for readability Break dense paragraphs into one topic each and long clause chains into separate sentences. Replace slash compounds with plain words, and use lists for real enumerations. Restate fixture narration as direct statements of Milo behavior, or drop it when it only listed test coverage. State each page-level caveat once. Code blocks, headings, anchors, and link targets are unchanged. Signed-off-by: Kevin Herron <kevinherron@gmail.com>
Simplify the code samples Put each step of the rewritten helpers on its own line, with braces on every if and named intermediate values instead of nested calls. Drop result-count checks for single-operation requests and the test-only counter in the history service sample. Point the fixture links at the commit that carries the matching code. Signed-off-by: Kevin Herron <kevinherron@gmail.com>
Link Wiki references to contributor documentation Pin the source guides, tutorial README, and encoding fixture to the verified source follow-up. Describe the contributor references accurately and link migration guidance directly to the release notes. Signed-off-by: Kevin Herron <kevinherron@gmail.com>
Complete the 1.2 Wiki user guide Replace the tutorial, client, server, and reference outlines with caller-focused guidance and executable examples. Audit the release migrations against the pinned 1.2 baseline while retaining existing page URLs, anchors, and nested navigation. Signed-off-by: Kevin Herron <kevinherron@gmail.com>
Link SDK topics directly from the Wiki sidebar Signed-off-by: Kevin Herron <kevinherron@gmail.com>
Use the Wiki's native page titles Remove repeated document titles from the new guide pages while retaining their anchors. Tidy the Client hub's link descriptions. Signed-off-by: Kevin Herron <kevinherron@gmail.com>
Build the 1.2 user guide skeleton Add client, server, and shared-topic outlines with links to current examples and guides. Organize them through landing pages and Wiki navigation, and identify the guide as a 1.2.0-SNAPSHOT work in progress. Replace the old Client SDK guide with a topic hub while preserving its heading anchors. Point code-style guidance back to the source repository and retain the existing release notes. Signed-off-by: Kevin Herron <kevinherron@gmail.com>
Rewrite the Home page
Add release notes section with the 1.2.0 guide
Specify Java syntax in code blocks
WIP Client.md
Created Code Style (markdown)
Initial Home page