jacobh2
d5f33e8c7f
The dashboard stated the loss and stopped there. With Jacob at 48/48 savable
and 24 days over the cap, and Amelie at 3/48 with 45 days of headroom, those
24 days are not lost at all — transferring them before the 4th birthday saves
every one. The app never said so.
`_rule_age4_pooling_loss` already computed exactly that advice, bounded by the
FK-reported `transferable_days_left`, in finished Swedish and English. It never
ran: `age4_pooling_tip_min_child_age_years` held it back until the child turned
2. The calendar IS the plan, so gate on the plan instead — the noise case is a
newborn with nothing planned, not a young child whose parents have planned in
detail. `age4_pooling_tip_min_planned_days` (20) replaces the age gate.
Both variants drop to `info`. A projection four years out should not read as a
verdict on the user's planning; the hero carries the alarm, this card carries
the advice. The copy now leads with "plans change, this is only a projection"
and closes by pointing at keeping balances up to date, since parents will come
back and record what they actually took.
- Suppress `preserve_for_age_4` whenever `age4_pooling_loss` fires for the same
child. The pooling tip states the same loss plus the remedy and the correct
per-parent cap, so emitting both gave two contradictory "you're losing N
days" figures.
- `preserve_for_age_4` now sends `parent_cap` and its copy interpolates it. It
claimed "only 96 days can be saved" — false for a two-parent family, where
the cap is 48 each, as the Age4Bars card two rows below already showed.
- The hero grows a "How to save them" line derived from the tip itself, so the
two can never disagree on the number. Dismissing the tip retires both.
- "Försäkringskassan" in that line links to FK's BankID login carrying a `goto`
to Min föräldrapenning — the e-service showing "Dagar ni kan föra över" —
so the transfer is one click away. `translate()` returns a plain string and
word order differs between locales, so the anchor's position travels inside
the template as `{fk}` and the rendered string is split around it.
Verified in the browser: hero, link target, tip severity and the absence of
`preserve_for_age_4`, in both languages and at 390px. Note the demo seed cannot
reach this shape — it gives the surplus parent no FK snapshot at all.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01DXPBfr1v7F71t6QcbHCaaT
Föräldraledigplannerare
A planner for Swedish parental leave (föräldraledighet) — solo or with a partner — that folds in vacation days and optimizes leave over time so that as few days as possible are lost at the child's 4th birthday, after which only 96 days may be saved (48 per parent, non-poolable, as soon as the child has two or more parents).
Full-stack monorepo: TypeScript/React/Vite frontend, Python/FastAPI backend,
SQLite by default. Postgres is a partial stub, not a usable swap yet — see
backend/README.md.
Quick start
From frontend/:
npm install
npm run dev # runs uvicorn (:8000) and Vite (:5173) together
Open http://localhost:5173 (not 127.0.0.1 — Vite's dev server binds
IPv6 ::1, so only localhost resolves to it).
The backend can also run on its own, from backend/:
uv sync
uv run uvicorn app.main:app --reload --port 8000
Seed a ready-to-explore demo workspace (couple, a partner, a child, vacation history, leave wishes, a deliberate shortfall) through the normal service/repository layers — no raw SQL:
cd backend
uv run python scripts/seed_demo.py --reset
It prints the demo login (fixed credentials, safe to re-run — without
--reset it's a no-op if the demo user already exists).
The Försäkringskassan scraper (BankID login flow via Playwright) is enabled
by default. Exercise the login UI directly with npm run login from
frontend/; Chromium must be installed separately:
uv run playwright install chromium.
The app
Three tabs:
- Översikt — the headline figure for days at risk at the 4th birthday, per-parent bars against each parent's savable cap, a year-by-year timeline, and shortfall/surplus detail below the fold.
- Kalender — where leave is authored. Drag a range to create a period, click a band to edit it, click a day to change which resource funds it (sjukpenning/lägstanivå/vacation). A season-preset rail helps place common periods (summer, Christmas, Easter). Day overrides (marking a specific date as a working day or a free day, overriding the calendar) live in Inställningar, not on the calendar itself.
- Inställningar.
The calendar is the plan. There's no separate propose-then-apply step:
every edit recomputes and persists immediately, reporting what changed with
an undo. A LeaveWish is a recurring intent (e.g. "summer", "Christmas");
the allocator decides which resource — parental days, vacation, unpaid —
funds each day, without retyping days a user has pinned by hand.
First run walks a wizard: add the child, optionally add a partner (planning solo vs. together is derived from whether a partner has been added — there is no separate solo/couple choice), then set balances — fetch from Försäkringskassan via BankID, enter manually, or skip (figures are then marked as estimates).
Layout
backend/app/
entities/ persistence-layer row shapes
models/ Pydantic v2 API schemas
repositories/ abstract repository interfaces
repositories_impl/ sqlite/ (default, complete) and postgres/ (partial — one entity only)
services/ business logic — planning, tips, analytics, auth
scrapers/ Försäkringskassan scraper (Playwright)
routers/ thin FastAPI route handlers
backend/migrations/ Alembic migrations (hand-written, not ORM-generated)
backend/scripts/ seed_demo.py and other dev-only scripts
frontend/src/
pages/ route-level screens (Dashboard, Calendar, Settings, ...)
components/ presentational + composite components (BEM CSS)
hooks/ data-fetching/state (the data layer — no TanStack Query)
services/ api.ts (HTTP client) + errors.ts
context/ Auth + Workspace React context
frontend/e2e/ Playwright end-to-end specs
Routers call services; services call the repository interfaces — never
repositories_impl directly. Components consume hooks; hooks call
services/api.ts — components never call fetch directly.
Tests & gates
Backend (from backend/):
uv run ruff check .
uv run ruff format --check .
uv run pytest --cov=app --cov-report=term-missing --cov-fail-under=80
Frontend (from frontend/):
npm run typecheck
npm run lint # ESLint, zero warnings allowed
npm run coverage # Vitest, thresholds: lines 96% / functions 91% / branches 92% / statements 96%
Both suites pass comfortably above their gates (backend ~84% vs. an 80%
floor; frontend above 96/91/92/96 — see frontend/vitest.config.ts). Gates
are a regression ratchet, not a target; run the commands above for current
numbers rather than trusting a hardcoded count here, which drifts fast.
CI (.github/workflows/ci.yml) runs all of the above, plus a Playwright E2E
suite that reports but does not yet block merges.
Further reading
CLAUDE.md— conventions, stack details, model-tier rules for contributors.ARCHITECTURE.md/PLANNING_ENGINE_SPEC.md— design and rationale. Both predate parts of the current behavior; sections marked SUPERSEDED note what changed and why.backend/README.md— backend-specific setup and the reference vertical slice to copy when adding a new entity.