amadan
Enablement: the roll rule names the e152df30 exception for the commit column
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
1 file changed,
+4
−2
implementation/carloku-paid-launch/ENABLEMENT.md+4 −2
CI passed — run details
diff --git a/implementation/carloku-paid-launch/ENABLEMENT.md b/implementation/carloku-paid-launch/ENABLEMENT.md| index 1625a2203..51c816658 100644 |
| --- a/implementation/carloku-paid-launch/ENABLEMENT.md |
| +++ b/implementation/carloku-paid-launch/ENABLEMENT.md |
| @@ -104,8 +104,10 @@ deletion has no point of no return, so a checkout review opening during |
| it can leave an account retired in the bucket and live here, and its reap |
| refuses such an account (the new build's reap follows the bucket). A |
| reservation an older binary kept after an ambiguous failure is marked |
| -committed when the new build adds the column, so nothing withdraws it. A |
| -refusal review that was open |
| +committed in the same transaction that adds the column, so nothing withdraws |
| +it; a database that ran the unmerged build `e152df30`, which added the column |
| +without that marking, would need the marking by hand (none did: billing is |
| +off and that build was never rolled). A refusal review that was open |
| before the build is held by it: nothing is known of what was attached, so |
| no outcome is offered until the decisions in `DECISIONS-FOR-PAUL.md` |
| (1 to 4) say how such a case is closed. |