[EricAndrechek]

HELD UNMERGED until the maintainer approves the lock (#596). Do not merge, do not tag.

The v2 lock, as #596 lays it out: ABI v2's description is locked, the production generation-2 fetch channel becomes every binding's default, the four packages say 2.0.0, the docs stop describing a dev pre-release, and each CHANGELOG has one 2.0.0 section.

Identity at this head

	before (v2 b7a6c3e3)	this PR
CHS_ABI_FINGERPRINT (gen.py --major 2 --fingerprint)	sha256:d53239933966e15a3c363e631a94fbba1231d84c4300337115d3ae5377bb41c2	sha256:78518cd5f88205ff4fcdbd94b137566192d7993888a6dc0d65de3357f6044b4e
shasum -a 256 include/v2/chtypes.h	047512a8144bdacafd1c86098bb3229aab6769d5151193956bdd6ff5df6cab36	6070e6229270ce59af779478cf2f4c47f0d5052cbbf632d3a68638fe6264dd7f

The fingerprint moves only with stability. The header's bytes also carry the prose that now says locked (its Stability paragraph), which is outside the fingerprint.

What changed

1. The lock. spec/abi-v2/abi.json: "stability": "locked", then regenerated with gen.py --major 2 --write. The prose in spec/abi-v2/docs.md and docs/reference/abi-v2.md says locked. The where-settings note marked for removal at the lock is removed.

2. The production channel is the default in all four bindings: active() falls back to it (Go channel.go, Python _channel.py, TypeScript channel.ts, Rust channel.rs).

   • It fetches from https://registry.wavehouse.dev/chtypes/v2 under the release key, and honors every override and pin.
   • Its cache is ~/.cache/chtypes/v2, or <cache>/v2 under an explicit cache.
   • The dev channel stays, reachable only through each binding's test seams, and the dev-channel tests select it explicitly.
   • The real-CLI tests now prove that a non-test binary speaks production.
   • These follow the production channel, read from spec/fetch-v1/constants.json or scripts/release-channel.sh: the shared cache-roots table, the CLI parity rows, the interop job's system directory, examples/chplay.sh, and release-channel.sh get <NAME>.

3. 2.0.0 in the eight places the 2.0.0-dev.N bumps changed: the three manifests, Go's bindingVersion, and the four lockfiles.

4. Docs.

   • The README, the four binding READMEs, docs/install.md, docs/quickstart.md, docs/reference/go.md and docs/guides/artifacts.md now install 2.0.0 the plain way, with Go on the /v2 module path.
   • docs/guides/fetch-v1.md ("Generation 2 after the lock") says the production channel is the default.
   • docs/limitations.md notes that its build ids are v2 development builds.

5. CHANGELOGs (CHANGELOG: consolidate the dev-era entries into one 2.0.0 section per binding #599). Each binding has one [2.0.0] section relative to 1.1.0, with the same structure in all four:

   • Added.
   • Changed, opening with one migration list from 1.x.
   • Removed.
   • Fixed.

   Pairs that cancel or supersede each other are collapsed. Entries that apply only to the dev channel are named once, in the intro. The 1.x sections are untouched.

CI that is red until the 2.0.0 libraries are published

#596's order applies: the artifact producer builds from this head, then publishes to production chtypes/v2.

• The examples and interop legs run the real CLIs, and those now fetch from production chtypes/v2. They fail until the 2.0.0 libraries are there.
• The support-v2 page check runs because this PR touches its generator, whose selftest now expects the production channel. It compares docs/support-v2.md against production, so it stays red until the page is regenerated after the first production publish (uv run scripts/support-v2/gen.py --write, RELEASING.md).

Lock-review text fixes

Prose and data only: spec/abi-v2/abi.json is untouched and the fingerprint is unchanged (sha256:78518cd5…). The header is regenerated because its comments come from docs.md.

• The decline catalog (spec/abi-v2/declines/declines.json) is re-copied byte for byte from the artifact producer: 55 → 138 entries, no id removed. The README says this file is the published catalog rule r4 freezes, documents the new misuse and export-decline classes, the load_dependence field and the retired form, and pins the new sha256; check-declines.py pins the eight classes.

• docs.md: the lock in the present tense; CHS_REJECTED no longer listed for chs_schema_describe; exact message text guaranteed only where the description quotes it; column_defaults and defer_defaults implemented and advertised in capabilities.features; the three clock knobs refused (115) by chs_set_defaults and a schema's settings; an EPHEMERAL column in columns read as ephemeral_input; macros validated but not applied (declined); the non-NULL server hedge removed; SHOW CREATE TABLE output measured compiling for 32 of 32 shapes.

• abi-v2.md: nine rules, r1 to r9.

• limitations.md: names the 2.0.0 build 20261021.191313; the EPHEMERAL entry corrected; binary parameters fixed in v2 for Go, Python and TypeScript; SHOW CREATE of a Memory table retired as fixed; the 1.0 headings made version-neutral, with their old anchors kept.

• The four CHANGELOGs, the README and the discovery guide follow the new counts.

• The reserved macro behaviour is tied to server_profile.macros. A build that applies a server profile's macros advertises server_profile.macros in capabilities.features (rule r9). Only such a build reads present macros as the complete set, with the 139 refusal. Every other build validates macros and declines a macro-reading schema.

• Stale text outside the spec is updated:

  • the "does not compile on a server yet" and macros-"expand" wording in the Go README, bindings-v1.md, the examples README, the tour comments and the four bindings' doc comments;
  • the 1.0 wording in README.md, python/README.md, docs/reference/python.md and docs/install.md, which now names no version.

Not in this PR

The goldens runners in all four bindings, and the v1-goldens and v1-real workflows, still select the dev channel for a registry run. Moving them to production waits for a production build that carries goldens.

Closes #599. Refs #596, #511

🤖 Generated with Claude Code