docs(runbook): replace the announced trial floor with a 30-day notice gate #494
Inga granskare
Etiketter
Inga etiketter
area/backups
area/ci
area/control-panel
area/identity
area/infra
area/observability
area/payments
area/security
area/storage
area/web
blocked
needs-info
needs-triage
ready-for-implementation
type
bug
type
chore
type
docs
type
epic
type
feature
type
task
wontfix
Ingen milstolpe
Inget projekt
Inga tilldelade
1 deltagare
Notiser
Förfallodatum
Inget förfallodatum satt.
Beroenden
Inga beroenden satta
Referens
bitborg/bitborg-infra!494
Läser in…
Hänvisa till i nytt ärende
Ingen beskrivning angiven.
Ta bort grenen "work/trial-notice"
Borttagning av en gren är permanent. Även om den borttagna grenen kan fortsätta existera en kort tid innan den faktiskt tas bort, kan det INTE ångras i de flesta fall. Vill du fortsätta?
The public trial copy is dropping its date. Until now every user-facing surface said the trial runs "at least until 31 August 2026", a floor, with the trial actually ending when paid subscriptions launch. That floor has passed. The new public promise is: the trial ends when paid subscriptions launch for everyone, with at least 30 days' notice.
This is the operator side of that change. No playbook was run, nothing was applied.
group_vars/all/vars.ymlThe
web_trial_opencomment described "no scheduled date, 31 August 2026 is the announced floor". It now says the trigger is paid subscriptions launching, with no date scheduled anywhere.docs/runbook.md, the trial downgrade sectionThe section was built around "31 August 2026 is a floor, not an end date", including a closing paragraph about what it would take to move the floor. That reasoning is gone. In its place: no surface carries a date, the trigger is the launch, and the public commitment is 30 days' notice, with nothing in the system scheduling either the notice or the downgrade.
The substantive change is that the notice is a step in the procedure, not a note above it. Prose above a code block is what an operator following commands top to bottom reads past. It is now numbered, and it sits immediately before the irreversible step that revokes capabilities.
The step order matters and was got wrong on the first pass. Closing the trial door comes first, then the notice, then the wait:
Notice-then-close would let a trial started during the notice window be downgraded without ever having been told, which breaks the promise for exactly the people least likely to be watching.
Follow-up, not in this branch
Issue #270 is still titled "Execute the end-of-August tier_trial → participant downgrade". Its body states an announced end date, its gate says "if subscriptions slip past end of August", and its step outline is now off by one against the runbook and predates the notice step. It also cites a runbook heading that does not exist. Being updated separately.
Verified:
pnpm mdlint,prettier -cu,ansible-lint(0 failures, 0 warnings, production profile), plus the full pre-push suite.grep -rn -iE "31 (august|augusti)|august 2026|end.of.august|announced floor" ansible/ docs/ scripts/returns nothing.