Release: leftovers, the real dish list, and a day list that stays put (#2)

Tähteet — leftovers. Not a dish: it exists so a day can be recorded as "we ate what was already there" without inventing a meal nobody cooked. A special-flagged row created by migration 0002; never in the catalog, never editable, and excluded from the stage-2 suggester outright. It gets its own mark, a grey lidded tub — which exposed a bug where no categories drew the same icon as several. The real dish list. The seed bundle is now your December 2024 list: 37 mains, 9 sides. Letut and Pannari dropped as not-dinners, Kanakintut folded into Broilerin koipireidet, has_sides assigned by rule. The day list stays put. Choosing a day used to swap a panel in above the list and drop that day out of it, so rows below jumped up under the tap. The list is now the page; the selected day expands where it sits, with anchors so the viewport lands on the day rather than the top. Release pipeline fixed. The last release silently pushed the previous image: release declared image and push as prerequisites and your make runs -j16, so they raced. Also, push re-derived the tag by date-sorting, which is ambiguous when two tags share a commit. It now reads what image recorded, and verifies afterwards that the registry serves what was built. Co-authored-by: Esa Kataja <[email protected]> Reviewed-on: #2
2026-09-05 20:24:02 +00:00
parent e9754488db
commit 174652778b
12 changed files with 405 additions and 88 deletions
@@ -113,6 +113,23 @@ in English.
 Side dishes live in their own table and have no category. The pool is
 expected to stay small.

+### Tähteet — leftovers (stage 1)
+
+A single built-in entry, flagged `special` on the main dish table. It is
+**not food**: it exists so a day can be recorded as "we ate what was already
+there" without inventing a meal that was never cooked.
+
+- No category, which is why it cannot be an ordinary main: those must have
+  at least one.
+- Created by a migration. The household does not add, edit or delete it, and
+  it never appears in the Ruuat catalog.
+- Loggable exactly like any other entry, and shown on the log board apart
+  from the categories.
+- **The stage 2 suggester must never propose it.** It is excluded from the
+  eligible pool outright, so cooldown, category coverage (§8.1) and
+  frequency weighting (§8.2) all skip it — despite it being among the
+  most-logged entries.
+
 ### Meal log entry ("what was actually eaten") (stage 1)
 - `id`
 - `date` — SQL `DATE`, day granularity only. There is no time-of-day field