Align 0.2.0 release documentation with verified full run 27

[KeyffMS]

OPENAI_COMPLIANCE.md still described the historical run #25 and an outstanding finite C08 prerequisite after full run #27 had already verified and committed that proof. The changelog also split intended 0.2.0 changes between Unreleased and 0.2.0, so generated version-specific release notes omitted part of the qualified release.

This PR:

• updates the compliance checklist and current qualification record from the committed Isolate Codex 0.152 runtime contracts and declare PlanAnvil roles #27 summary, retaining the actual executed source SHA, historical Fix Codex runner variant dispatcher #25 timeout and C13 non-ephemeral limitation;
• consolidates all intended 0.2.0 changes into one pending-publication version section without changing VERSION or the qualified product;
• adds CI regressions comparing the current compliance metadata and finite C08 checkbox with the qualification index/summary, and checking source-bound qualification in the version's release notes;
• records the remaining signed-tag publication steps and keeps C09 observer reliability (Investigate intermittent receipt observation in hosted C09 CLI conformance #37) as an explicit open follow-up.

The active Protect main ruleset was reverified: seven required checks, strict up-to-date policy, PR-only squash, conversation resolution, and no bypass actors are already present. No ruleset change is needed.

Validation: PR CI #126 passed all eight jobs on head 4237e22ac7ab8aad29387ce036337cb916c63bbd: Ubuntu/macOS/Windows on Python 3.11/3.14, real-CLI loopback conformance, and distribution/release-candidate validation. All three new documentation checks passed; the distribution suite ran 196 tests (two real-CLI classes are skipped there and executed in the dedicated conformance job). Local shell execution is unavailable because the workspace disk is full; no local Python result is claimed for this change. The new record was compared against the committed #27 index/summary before submission. Product/runtime files and immutable qualification evidence are unchanged, so this documentation reconciliation does not require a new live run. Production publication still requires a clean strict release check and a GitHub-verified signed annotated tag.

Closes #17. Its baseline 2.3 qualification resolution is demonstrated by full #27; ephemeral spawning remains an explicitly documented upstream limitation.