| Comment: | land ci-rfc |
|---|---|
| Timelines: | family | ancestors | descendants | both | trunk |
| Files: | files | file ages | folders |
| SHA3-256: |
75c0ffe751a49f840117a2bc7634260b |
| User & Date: | dmestas on 2026-08-29 01:46:49.782 |
| Other Links: | manifest | tags |
|
2026-08-29
| ||
| 01:48 | land ci-2 check-in: 6ce967a4db user: dmestas tags: trunk | |
| 01:48 | merge trunk closed check-in: 4e8bb73332 user: dmestas tags: ci-2 | |
| 01:46 | land ci-rfc check-in: 75c0ffe751 user: dmestas tags: trunk | |
| 01:14 |
settings: every panel confirms the same way, in the palette's green
The description form got a Save/Saved swap; the other panels still said nothing at all. Worse, three of them redirected to ?saved=1, which had quietly stopped meaning anything when the flash cookie replaced it — a regression I left behind an hour ago. Six exit paths across five handlers were still writing it. They all set a named flash now. The name matters: a page carries six Save buttons, and a bare boolean would light every one of them for a single save, telling the reader that everything was written when one thing was. Green comes from --add, the token that already marks a passing run and an open glyph, so 'it worked' is one colour across the forge. Webhooks is deliberately untouched: it is a LIST with Save, Pause and Delete per row, so lighting 'the' Save would need to know which row. Different shape, not this pattern. The visibility test pinned ?saved=1; it now asserts the flash, which is the contract rather than the spelling of a mechanism. check-in: 2f0c4fcb50 user: dmestas tags: trunk | |
| 00:26 | rfc 0009: CI — verdicts on landings, spec, premerge, runners closed check-in: 56d87626d9 user: dmestas tags: ci-rfc | |