Lucas WintherandClaude Opus 5
bdb2b9d80f
The step stripped `occurrenceDate` from an anchored cost's charges and left `Purchase.date` alone. Under schema 7 those dates are legitimately month-only: a monthly cost's grid was month-granular, and `confirmOccurrence` wrote `date: overrides.date ?? occurrenceDate`, so every one-click confirmation of a month-granular anchored bill was stored without a day. An anchored cost has no slots, so after the upgrade that date IS the anchor the series steps from — a realistic schema-7 dataset therefore migrated cleanly and then threw out of every money route on first load. The owner has a phone bill; this is their data, not a hand-edited file. The day comes from the `occurrenceDate` about to be stripped when that slot falls in the same month, because it is the day the owner actually settled; otherwise the 1st, the same convention the `startDate` expansion already uses. A slot in a DIFFERENT month is not borrowed from — that would move the purchase, and moving money is what this step must not do. Extending an unshipped step rather than appending a new one: 7 -> 8 exists only on this branch, so no stored dataset has been through it. The regression test builds a schema-7 dataset the app itself would have written and folds the result, rather than only inspecting the shape. A second test pins the agreement the two halves of this fix have to keep: `parseDatasetJson` migrates before it validates, so everything this step produces must satisfy the import boundary the next commit tightens. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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.