0.1.8 RC1: Aggregate six fixed regression batches and publish promotion evidence #257

Parent

#248

Outcome

Aggregate the six immutable maintained-Provider route batches into the exact 0.1.8-rc.1 promotion record and publish the RC prerelease.

Responses batches:

• 0.1.8 RC1: Run the fixed GLM-5.2 Responses regression batch #287 — GLM-5.2
• 0.1.8 RC1: Run the fixed K2.7 Responses regression batch #288 — K2.7 Code
• 0.1.8 RC1: Run the fixed DeepSeek V4 Flash 0731 Responses regression batch #397 — DeepSeek V4 Flash 0731

Chat batches:

• 0.1.8 RC1: Run the fixed GLM-5.2 Chat regression batch #289 — GLM-5.2
• 0.1.8 RC1: Run the fixed K2.7 Chat regression batch #290 — K2.7 Code
• 0.1.8 RC1: Run the fixed DeepSeek V4 Flash 0731 Chat regression batch #398 — DeepSeek V4 Flash 0731

Acceptance criteria

• 0.1.8 Beta7 gate: Publish the stability and release-evidence candidate #319 is closed and the Beta7 candidate lineage is frozen.
• 0.1.8 RC1: Run the fixed GLM-5.2 Responses regression batch #287, 0.1.8 RC1: Run the fixed K2.7 Responses regression batch #288, 0.1.8 RC1: Run the fixed DeepSeek V4 Flash 0731 Responses regression batch #397, 0.1.8 RC1: Run the fixed GLM-5.2 Chat regression batch #289, 0.1.8 RC1: Run the fixed K2.7 Chat regression batch #290, and 0.1.8 RC1: Run the fixed DeepSeek V4 Flash 0731 Chat regression batch #398 are closed against one exact candidate SHA and profile version.
• Responses batches preserve the complete Beta2–Beta4 surface; Chat batches preserve the complete Beta6 text/tool/Collaboration V2 surface.
• Failed, degraded, superseded, and external-availability outcomes remain visible and cannot be overwritten by selective reruns.
• The batches are maintained-Provider release regressions, not a runtime model allowlist or restriction on custom endpoints.
• The aggregate records exact CLI version, route/catalog identities, evidence hashes, and cleanup status.
• No model fallback or cross-Provider execution appears in accepted evidence.
• Every durable artifact satisfies the bounded retention policy.
• Exact-head review, CLI/manual verification, local verification, prerelease assets, signatures, updater behavior, and provenance are green.
• 0.1.8-rc.1 is published as manual opt-in and stable 0.1.8 is not promoted automatically.
• Any product-code change after the fixed batches invalidates the record and requires a new RC candidate.

Blocked by

• 0.1.8 Beta7 gate: Publish the stability and release-evidence candidate #319
• 0.1.8 RC1: Run the fixed GLM-5.2 Responses regression batch #287
• 0.1.8 RC1: Run the fixed K2.7 Responses regression batch #288
• 0.1.8 RC1: Run the fixed DeepSeek V4 Flash 0731 Responses regression batch #397
• 0.1.8 RC1: Run the fixed GLM-5.2 Chat regression batch #289
• 0.1.8 RC1: Run the fixed K2.7 Chat regression batch #290
• 0.1.8 RC1: Run the fixed DeepSeek V4 Flash 0731 Chat regression batch #398