rcourtman c03be57f0d docs(release): make releasing the default and define an achievable soak ...

The 2026-09-05 direction left release timing to open-ended judgment. Since
then no line has been cut from main and no stable has shipped, while every
candidate that passed qualification was withdrawn. Restore a fixed cycle
with a closed list of stop reasons, and point at the maintainer's one-page
release policy.

The clean-soak rule required the stable dogfood instance and demo server to
run the candidate, but both run the current stable release by design, so
no candidate could ever soak clean. Define the soak from open regression,
security and data-loss reports, preview telemetry and the candidate
observation guest where it is operational.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_015AHsrZFUgqmohpszCMpaPx

2026-09-23 14:10:42 +00:00

..

internal

docs(agents): add customer support communication guidance

2026-08-11 16:39:36 +01:00

v6

docs(release): make releasing the default and define an achievable soak

2026-09-23 14:10:42 +00:00

control_plane.json

fix(release): map 6.4.5 reliability checkpoints to release line

2026-09-11 00:23:11 +01:00

control_plane.schema.json

Map legacy stable releases in control plane

2026-04-11 13:23:07 +01:00