Lucas WintherandClaude Opus 5
19087737eb
Every guard this model shipped with checked the COST's `startDate` granularity. Nobody checked the CHARGE's. An anchored (`lastCharge`) cost has no slots, so `anchoredOccurrences` takes the latest charge's own `Purchase.date` as its anchor and steps forward from it — and `Purchase.date`'s documented shape allows "YYYY-MM". Both write paths accepted that and the next fold took every money route down, with no way to recover from the UI: the anchoring select is disabled on a charged cost, there is no delete action, and the walk's precheck sits before the `endedFrom` break, so ending the cost does not help either. It was reachable by default, not by accident: `emptyDraft` seeds `date: monthId`, so a new purchase starts month-only, and the dialog offered every anchored cost regardless. `updatePurchase` accepted the same shape when "use the month only" truncated the date of an existing anchored charge. `requireSourcePairing` now takes the RESOLVED date, so an update touching only the date is checked against the source already stored. Both boundaries also route a day-shaped value through the domain's own parser, the way each already does for `startDate`: "2026-02-30" is day-granular and calendar-impossible, and `PURCHASE_DATE` lets it through, so it would otherwise import clean and throw from the same frame. Both files now ask `startDateNeedsDay`/`chargeDateNeedsDay` rather than restating the rule, and `parseDatasetJson`'s doc no longer claims more than it checks. 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.