Clarify maintenance release qualification and platform claims

[rmcdaniel]

Change

Reconcile CLI release documentation with the organization release follow-through guide and the public platform suite's compatibility-claim gate.

• Maintenance releases require normal supported PHP command/schema tests, PHAR build/reproducibility, focused live checks, complete distribution assets and exact published-artifact verification of the affected behavior.
• Full platform compatibility claims still require every stable required runtime scenario and an attached full or provisional harness result for the suite exposed by the Server build.
• Scoped patch evidence cannot be called full platform conformance.

The old document imposed an unimplemented aggregate harness process for every tag and fixed its authority at suite 27. The current suite is 47. This correction does not invent a harness result or relax response validation, fixtures or CI.

Related: #35 and merged fix #36. The HTTP failure patch still needs its exact published CLI storage-pressure repeat before delivery is complete.

Review

Compared the organization guide's risk-based release rules and the public suite's release_gates.description, required_fixtures_must_pass and stable_runtime_scenario_coverage rules. Markdown diff is clean. No runtime or workflow changes.

[rmcdaniel]

CLI 2.1.3 release qualification:

• The HTTP failure fix is merged in Preserve HTTP errors when response envelopes are unavailable #36. The release-document correction is merged in Clarify maintenance release qualification and platform claims #37 at bc72ab546780a065d166b165cdea2853f547130b. Its remote head is deleted and verified absent.
• Every normal check passes on the exact release commit, including PHP 8.2–8.5 command/schema tests, PHAR smoke and reproducibility. Main Build 36711528685 is successful.
• Focused HTTP/client/worker regression coverage passed 72 tests and 512 assertions. Live control/worker smoke against published Server 2.4.30 passed 76 assertions, including a completion payload encoded with published PHP SDK 2.1.6. The release commit changes only the conformance document after that runtime qualification.
• This is scoped HTTP-error maintenance qualification. No full platform harness result or new aggregate compatibility claim is made.

Publish 2.1.3 through the protected release workflow, require the portable PHAR and all four native platforms plus installers and checksums, then verify the original bounded MySQL start failure using the exact published CLI with Server 2.4.30. Also use the new CLI in Server #284's published-image recovery drill. #35 remains open until the original failure repeat confirms HTTP status 500 and the proper server exit code instead of a missing-envelope diagnostic.