Record what the todo list turned into

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Ei7gCZzdd751uZtPzb1Pep

todo.md

@@ -1,11 +1,46 @@
-- Bug in the planning when it repeats yearly: It is taking the exact same dates, but the way you usually take time off is week based, so 5th-11th of october 2026 is a monday through sunday, but for 2027 it looks like I'll take time off from tuesday to the following week's monday, which is not what I will do. Instead for 2027 I will probably take 4th to 10th instead.
+# todo
-- Please just verify that if I say that I take a full week time-off, including saturday and sunday, that I will NOT actually take any vacation or PL during those days. Or rather: This should be a setting: Take PL during red days yes/no. And it should default to NO. It is impossible to take vacation during red days (and saturdays), but you can actually take PL to get more money, but you will of course loose days.
+
-- The calendar view can still get messed up, see this image: ![](image.png). All boxes should be the same size in the calendar. It is a calendar view after all. This happens when the text takes too much space. Never allow the boxes to change size.
+Everything in the previous list is done — the original wording is in git history
-- When using the preset buttons in the calendar view, we are on the right track here, but I see some issues:
+(`git show d2bc2e9:todo.md`). What landed, and what is still open, below.
-    1. The default when there's two parents is that it is set to "either parent", which should default to "both parents" because we want to be off together.
+
-    2. The alternating between PL and vacation is very annoying: It doesn't give us any benefits, just lost more admin when requesting the leave. Instead it is better to so as long chunks of each as possible. Probably something like "Parent 1 takes 3 weeks PL while parent 2 takes 3 weeks of vacation, then they switch". But this doesn't mean that we shouldn't consider all the original tips and tricks how to maximise money.
+## Done
-- There should be a "Today" button left of the month dropdown in the calendar view that jumps to today's month.
+
-- Please turn off the debug mode that the FK scraping is shown, there's a feature flag for this.
+- **Yearly periods keep their weekday.** A Mon–Sun week recurs as Mon–Sun, not as the
-- Create a how-it-works.md file explaining what the "Your profile" part of the settings is for and what the salary type and employment status plays for role when it comes to optimising the time off. How is it used.
+  same two calendar dates landing mid-week. Fixed periods only; flexible ones already
-- The "Public holidays" section in the settings, that's great! But to the right where it says "off", let's make that dynamic so I can click it and it flips (only that day that I click, not the same day the following year) to be a working day.
+  re-place themselves each year. — `224fe7a`
-- When clicking the remove button on an event in the calendar view, there should be a difference of "removing just this event" and "removing all of the events related to this period in time".
+- **Red days cost nothing, and now there is a switch.** A test states outright that a
+  full week off spends nothing on the Saturday, the Sunday or a holiday. A workspace
+  setting, off by default, lets parental benefit be drawn on those days for the money;
+  it never reaches for a vacation day, which is not legally possible there. — `b87ad0e`
+- **Calendar cells never resize.** A long holiday name no longer squeezes its week's
+  row, and every row is the same height. — `f0f537c`
+- **Presets mean both parents, in long stretches.** Two-parent households default to
+  being off together, and the funding switches once per period (3+3 over six weeks)
+  instead of flipping daily. — `f76de7b`
+- **Today button**, left of the month dropdown. — `1837154`
+- **FK scraping runs headless again** — `APP_SCRAPER_HEADLESS` in the local, gitignored
+  `backend/.env`. The committed defaults were already correct.
+- **`how-it-works.md`** — what the profile fields do to the plan.
+- **Click a holiday to make it a working day**, that date only. — `663d5fc`
+- **Removing a period offers three scopes**: this day, this year, every year. — `35e479a`
+- **A hand-drawn period is funded by the planner** by default; pinning an exact day type
+  moved behind Advanced. Double days are now offered in the UI. — `35e479a`
+- **Two parents can hold the same days.** Saving for the second parent was rewriting the
+  first parent's days. — `35e479a`
+- **Opening a period shows the dates it actually has**, not the first year's. — `1837154`
+- **A shortfall funds what it can and says what would close it**, including moving the
+  window onto Easter — the search now covers four weeks either side instead of three
+  days, and the advice is finally rendered. — `11f2a17`
+- **`dubbeldagar.md`** — answers the question, and corrects half of it.
+
+## Open
+
+- **The e2e specs have not been run.** New Playwright coverage was written for the
+  uniform grid, the drag-to-create flow and the three-way remove, but no run has
+  happened — `npm run e2e` from `frontend/` needs a real browser and a seeded backend.
+- **Dubbeldagar are not outside the 480.** `dubbeldagar.md` sets this out: the 60 are
+  combined for the couple, as assumed, but each parent still spends one of their own
+  days on a doubled date. Nothing in the engine changed on the strength of it — worth
+  confirming against Försäkringskassan before anything is built on the other reading.
+- **`ParentalLeaveFetch.dubbeldagar_left`** is scraped per parent and read by nothing.
+  Per-parent is the wrong shape for a combined pot. Flagged, not touched.