Lucas WintherandClaude Opus 5
d542a6bdab
The precheck in `anchoredOccurrences` covered `everyNMonths` only, so a month-only starting point on an `everyNDays` or `everyNWeeks` anchored cost fell straight through to `addDays` and threw a bare "Not a day-granular IsoDate", naming no cost, several frames below `foldBalances` — the exact failure the precheck exists to prevent, for two thirds of the costs that can have it. The walk is day-precise under all three kinds, so the check is too. The rule about WHICH dates need a day was written out separately in four places (both write boundaries and both controls that offer the pairings). It now lives once, in `granularity.ts`, alongside the second, different rule the next commits need: an anchored cost has no slots, so its latest CHARGE's own `Purchase.date` is the anchor the series steps from, whatever the kind. Three comments corrected to describe the code that exists: - `stepFrom` and `anchoredOccurrences` both claimed neither write boundary rejects a month-only `startDate`. Both do, and have since this model landed. Pointing the reader at the closed hole is why the open one — the CHARGE's own date — survived four reviews. - `Anchoring`'s doc still said confirming the occurrence early is the whole mechanism. An anchored cost has no occurrence to confirm; recording a charge is the mechanism. - `Occurrence.date` described slot identity as universal (it is calendar-only), and `confirmedBy` did not say it is unconditionally null on the anchored path. Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>
Budget 2.0
A personal budgeting PWA. Envelope-style monthly budgets with rollover, split purchases, finance plans, multi-currency, and JSON/ODS export. All data lives in your browser — there is no server and no account.
Development
bun install
bun run dev # dev server with hot reload, on :3000
bun test # run the test suite
bun run build # production build into dist/
Self-hosting with Docker
docker build -t budget2 .
docker run --rm -p 3000:3000 budget2
To serve from a subpath, build and run with BUN_PUBLIC_BASE_PATH:
docker build -t budget2 --build-arg BUN_PUBLIC_BASE_PATH=/budget/ .
docker run --rm -p 3000:3000 -e BUN_PUBLIC_BASE_PATH=/budget/ budget2
GitHub Pages
Pushing to main builds and deploys to Pages automatically, using
/<repository-name>/ as the base path. Enable Pages with "GitHub Actions" as
the source in the repository settings.
Your data
Everything is stored in this browser's IndexedDB. Export regularly from Settings → Your data: the JSON export is both your backup and how you move your budget to another device.
Both destructive actions there — Import, and "Reset everything" — download a backup of your current data before replacing it, and abort if that download fails. Reset puts the app back to a brand-new install: the three starter posts, the DKK/USD/EUR currency table, this month at zero income, no purchases.
Known limitations
- Data is per-browser. There is no account and no sync. If you clear this browser's site data, or move to a different browser or device, your budget is gone unless you exported it first. The JSON export is not just a nice-to-have backup — it is the only way to move a budget between devices.
- Installing and offline use are unverified. The manifest ships the SVG plus 192×192 and 512×512 PNG icons, and the service worker demonstrably installs, activates and precaches every asset — but nobody has yet confirmed that Chrome offers its "Install app" prompt, or loaded the app with the network actually cut. It works as a regular tab regardless.
Documentation
docs/ARCHITECTURE.md— layers, data flow, and why the non-obvious choices are what they are.docs/PRODUCT.md— who this is for and what must never break.AGENTS.md— the rules for changing this codebase, and the test that catches each one when broken.CLAUDE.mdandGEMINI.mdpoint at it.docs/DECISIONS.md— an index of the choices that shaped the app, and what each was chosen over.docs/TODO.md— what is still queued.docs/specs/— one design document per piece of work, each recording the alternatives that were rejected.docs/plans/— task-by-task implementation plans.