fix(openai): send the numeric OpenClaw release as the ChatGPT version header (#202427)

Follow-up to #202380.

## What Problem This Solves

ChatGPT gates subscription models in two places: the `/codex/models?client_version=` listing and the `version` header on `/responses` turns. Since #202380 the listing sends the numeric OpenClaw release (`YYYY.M.P`, falling back to `99.0.0`), but OpenClaw-harness turns still send the raw runtime version. Prerelease and dev builds therefore send values the backend has never been probed with (`2026.11.5-beta.1`) or that likely fail the model gate (`unknown`, `0.0.0-dev`). Then a model can be listed but its turn rejected. On 2026-11-18, a turn with `version: 0.164.0` returned HTTP 400 for `gpt-6.2-sol`.

## Solution

- Provider attribution now owns the ChatGPT gate value. For the `openai` provider, the `version` header is the numeric release (year 2026 or later), or `99.0.0`.
- `User-Agent` keeps the full build (`openclaw/2026.11.5-beta.1`), so OpenAI still sees the real version. It is not a gate input.
- `extensions/openai/base-url.ts` reads that header for `client_version` instead of repeating the rule, so the list and the turn send the same value by construction.
- Other providers keep their headers unchanged, including xAI, which shares the OpenAI header shape.
- Codex-harness turns are unchanged: the Codex binary sends its own version.

## User Impact

- Stable releases: no change. `2026.11.5` was already numeric.
- Beta builds: turns send `2026.11.5` instead of `2026.11.5-beta.1`.
- Dev and source builds without a calendar version: turns send `99.0.0` instead of a placeholder. Turns on newly launched models then pass the same gate as the listing.

## Evidence

- **Red on main, green on the fix:** `src/agents/provider-attribution.test.ts` › "sends ChatGPT the numeric OpenClaw release …". On main, 4 of 5 cases fail (`2026.11.5-beta.1`, `2026.11.5-1+build.abc`, `unknown`, `0.0.0-dev`); the plain `2026.11.5` case passes on both. Each case also checks that `User-Agent` keeps the full build.
- **Consumers green:** `provider-attribution`, `agent-tools.prefix-stability`, `openai-transport-stream.base`, `stream-wrappers/openai`, `openai-codex-discovery`, `provider-live-listing.contract`, OpenAI TTS, realtime browser auth and device-code tests.
- **Gates:** `tsgo:core`, `tsgo:extensions` and `check:test-types` pass. `ocx build --dts` and the packed release smoke (`scripts/release-check.ts`) pass.
- **End to end** (isolated Gateway from source, fresh ChatGPT device-code login): `models.list` returned 11 subscription models with outcome `ready`, including `gpt-6.2-sol` and `gpt-6.2-astra`. A real turn on `openai/gpt-6.2-sol` returned `NVH_OK`.
- **Live values:** the 2026-11-18 probe with a real ChatGPT login returned HTTP 200 on `/responses` for `gpt-6.2-sol` with `version` set to `2026.11.5` and to `99.0.0`, the only two shapes this change sends.
- **Not proven live:** a beta or dev runtime version. The dev tooling strips `OPENCLAW_*` from the Gateway environment, so the source Gateway reported the stable `2026.11.5`. The attribution test covers those inputs.

## Merge Risk

Two-way door: no state, config or contract changes, and a revert restores the raw header. Blast radius: the `version` header on OpenAI-provider requests (ChatGPT and platform routes) for prerelease and dev builds. Stable builds send identical headers.

Co-authored-by: Ayaan Zaidi <hi@obviy.us>