10 most recent check-ins occurring on or after 2026-08-29 01:14:56.
More ↑
|
2026-08-29
| ||
| 01:49 | land ci-4 check-in: 7932145520 user: dmestas tags: trunk | |
| 01:49 | land ci-3 check-in: 60726f18bb user: dmestas tags: trunk | |
| 01:49 | merge trunk closed check-in: d4621cf095 user: dmestas tags: ci-3 | |
| 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:44 | ci: say when the target moved; offer update only then closed check-in: c9fd67b3b7 user: dmestas tags: ci-7 | |
| 01:29 | ci: the decision card closed check-in: b3ad657cf8 user: dmestas tags: ci-6 | |
| 01:22 | ci: checks panel wraps and orders for attention check-in: 36b81060d6 user: dmestas tags: ci-5 | |
| 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 | |