Sort the loose planning notes into folders

Reference notes move to information/, unstarted feature write-ups to
new-features/, so the repo root stops being a pile of markdown.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

ideas.md

@@ -1,7 +1,6 @@
 # Ideas
 
-Opinionated proposals from the state of the app after the calendar rework, roughly ordered by
-value. Not a backlog — things worth arguing about.
+Opinionated proposals from agents while working on the App. Agents are allowed to append ideas that they find.
 
 ---
 

new-todo.md

@@ -2,29 +2,12 @@
 
 ## High prio
 
-- Check how the "Förskolans planeringsdagar per år" is used: Automatically just removed from the count?
-    - This should be a per year "how many did you take" so that we also know the true number each year
-    to better understand how many days might go lost.
-    - This also needs to be displayed better in the overview.
+- If we have vacation days that are in risk of being lost, then the planner should run to update the kind of days used in the plan to use more vacation days (thus saving PL days).
 
-- Clicking the Ledig/Arbetsdag in the list of all red days makes the page reload and the user is scrolled to the top. Not nice UX. Instead should not scroll and the blob should simply switch once this is updated in the backend. Also, the list of "undantag" should auto-update because this is a react frontend which can update only the parts that need to do so when the data updates. The data should become stale since we do an action (flip between working and non-working) and then it should auto-refetch and thus update the UI.
-
-- How does it work when the other parent wants to login? beacuse that parent should be connected to the same
-plan and same child. This whole user flow needs to be looked over.
-
-- Inputting the number of vacation days is now only possible for the logged in parent, but not possible
-to change the other parent (if available). This should be done since we are able to change the other parent's
-PL days, so should the vacation days be possible to change
-
-- Updating the amount of vacation days now leads to needing to click save for each year in the settings, that 
-is super annoying. (And an issue we have already talked about). The way to do it is with a debounce and autosave
-WITHOUT reloading the entire page.
-
-- I don't understand the vacation calculations right now, it doesn't give me confidence: For Jacob it says that he has 30 days, 15 are planned so thus 15 are left. Then it says that only 10 are saved for next year (which is correct since I can only save what is over 20), but it says that 0 are expiring! This is super important to warn/highlight, so that Jacob takes out more vacation. And maybe that the planner should make sure to say that we should switch out PLs (if possible) to vacation to not expire any days. This would lead to more PL days, which can lead to the ability to be on time off longer in the future. Image that shows how it currently looks like here: ![](./vacation_issues.png)
+- On every event that updates the days off (i.e. the calendar is making some changes), that should trigger the planner to recalculate the best kinds of time-off for all days. 
 
 ## medium prio
 - Update all deprecated things in the backend code.
-- check the "open" in todo.md, if they should be done
 
 ## lowest prio
 

todo.md

@@ -1,27 +1,9 @@
-# todo
+- 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.
 
-Everything in the previous list is done — the original wording is in git history
-(`git show d2bc2e9:todo.md`). What is still open, below.
+- 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.
 
-## Open
+- 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.
 
-- **Rate limiting is keyed on the caller's address**, which behind a reverse proxy
-  without forwarded-header handling is the proxy's — so every user would share one
-  30/minute refresh budget, and `AuthContext.tsx` turns a failed refresh into a silent
-  logout. The e2e suite hit exactly this. Two separable calls: which proxies to trust
-  for `X-Forwarded-For`, and whether a non-401 refresh failure should log someone out
-  or retry. The `catch` there has two identical branches, which reads unfinished.
-- **A removed day is never cleaned up.** Delete the whole period and the veto rows stay,
-  so a later period covering that date still skips it. Reachable only through that day's
-  popover; there is no list of them.
-- **Undo after an "every year" edit** restores the anchor's dates across the series
-  rather than each year's previous dates, so per-year divergence from before the edit is
-  lost. Would need a per-edit snapshot.
-- **`PLANNING_ENGINE_SPEC.md` §2.1/§3.2/§10.2 and parts of `ARCHITECTURE.md`** still
-  describe the single-row recurrence model that no longer exists.
-- **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.
+- If we have vacation days that are in risk of being lost, then the planner should run to update the kind of days used in the plan to use more vacation days (thus saving PL days).
+
+- On every event that updates the days off (i.e. the calendar is making some changes), that should trigger the planner to recalculate the best kinds of time-off for all days.