7 Commits

Include renames

Author	SHA1	Message	Date
Lucas WintherandClaude Opus 5.5	9477ac54b6	feat(dailies): edit the strip in place, and give weekly and monthly tasks their own row ... Giving Genshin's "To Temper Thyself and Journey Far" its five-of-seven goal meant finding it in the list, opening its sheet, saying it repeats and only then setting the goal. The strip now has an Edit mode beside Catch up that lists its events by game with their goals, opens the sheet's goal control in place, and adds any running event a game at a time. It calls the same setDaily/setGoal the sheet does, so it can store nothing the sheet would not. Weekly and monthly tasks are not due tonight, so they move to a row under the dailies, and each period can be switched off (showWeeklyTasks, showMonthlyTasks; default on, so nothing disappears on upgrade). Co-Authored-By: Claude Opus 5.5 <[email protected]>	2026-10-14 01:41:37 +02:00
Lucas WintherandClaude Opus 5.5	1fc47e2864	chore(changelog): announce the changelog, and make entries a convention ... The changelog's own entry names the commit before this one, since a commit cannot contain its own hash. AGENTS.md now asks every reader-visible change for an entry, and every multi-commit feature for a note, so the record keeps up. PRD F18 and the storage and design records describe what shipped. Co-Authored-By: Claude Opus 5.5 <[email protected]>	2026-10-13 14:27:25 +02:00
Lucas WintherandClaude Opus 5.5	bcbd3cc188	docs: record built-in weekly tasks ... Co-Authored-By: Claude Opus 5.5 <[email protected]>	2026-10-13 14:13:30 +02:00
Lucas WintherandClaude Opus 5.5	54d8424d1e	docs: record weekly and monthly tasks ... The product, storage and design records now cover F17. They say why the task and amount stores, unlike the custom-event store, never filter on load, which is the rule a future store would most likely copy wrongly. Co-Authored-By: Claude Opus 5.5 <[email protected]>	2026-10-13 13:50:08 +02:00
Lucas WintherandClaude Opus 5.5	d5ffad38c5	docs: record check-in goals ... The product, storage and design records now say what a goal is, why it never marks an event done, and why an unreadable goal is kept rather than stripped. That last rule is the one a future cleanup would most likely undo by mistake. Co-Authored-By: Claude Opus 5.5 <[email protected]>	2026-10-13 13:18:00 +02:00
Lucas WintherandClaude Opus 5.5	21a0460ea6	fix(ui): keep one lit meter tick while an event is still running ... Forty minutes left of a two-week event is under half a tick, so the meter rounded it down to an empty strip. The most urgent rows and the headline looked like events that were already over. Co-Authored-By: Claude Opus 5.5 <[email protected]>	2026-10-01 04:18:13 +02:00
Lucas WintherandClaude Opus 5.5	8a6110396a	docs: move PRODUCT and DESIGN into docs/ and list them in AGENTS ... They are reasoning for whoever touches the interface next, which is what docs/ holds, and the table in AGENTS.md is how an agent finds it. The design tooling resolves both from docs/ without configuration. Co-Authored-By: Claude Opus 5.5 <[email protected]>	2026-10-01 04:09:57 +02:00