Point the documentation at 0.33.0-rc1000, and open the 0.34.0 line

[ipjohnson]

The release pull request for v0.33.0-rc1000. Both halves ship with the tag rather than after it, for the reasons the release skill records.

The open line moves to 0.34.0

RELEASE_LINE in build-package.yaml names the line previews are stamped under, which is the line currently open — not the last one released. Releasing 0.33.0-rc1000 while it still said 0.33.0 would stamp every subsequent preview 0.33.0-previewNNNNNN, which sorts below the release, and the feed could serve a preview over it. That is not hypothetical: it sat at 0.23.0 through the whole of v0.30.0-rc1000.

Next minor, and the sequence skips numbers on purpose — there was no 0.7.0, and 0.23.0 through 0.29.0 were skipped so the consolidation got a number of its own.

The documentation sweep is the workflow's own guard, run early

release.yaml's Check the documented version is this one is step 464. Push to nuget.org is step 416. So that guard fires after the packages have shipped, which is how it failed v0.31.0-rc1000 with a published release and a red run.

57 citations across 22 pages: every copyable PackageReference, <HardenedVersion> and dotnet new install line under docs/ outside design/, plus the prose line in reference/packages.md that names the current line. design/ is left alone, because those are maintainer notes that cite historical versions on purpose, and no line mentioning Hardened.Amz. was touched — it is frozen at v0.22.0-rc1000.

Preflight

Run before this branch existed, and all clean:

• On main, synced, clean.
• v0.33.0-rc1000 is not already a tag.
• No open pull requests, so nothing is missing the cut.
• The pack list covers every packable project: 65 listed, 71 packable, and the six unlisted are the template scaffolding under src/Templates/**/templates/ that are content rather than packages. Nothing is listed-but-not-packable.
• npm run build in docs/ — no dead links.

What this release contains

The whole of the 0.32 template trial's remediation, in five pull requests:

#327	The scaffold's DocumentStatusTests compares the document to the server, and the container-per-request rule that #315 shipped silently is written down
#328	A contract's servers is published, and HOAG032 names four inert declarations across both rungs
#329	A Smithy blob under @httpPayload is an operation a client can call
#330	dotnet new refuses the union host conflicts at instantiation
#331	An event stream can be asserted in the mode it deploys in

Plus #326, covering the entry-point rung where its assembly is measured.

The dry run and the tag follow once this merges.

🤖 Generated with Claude Code