Lucas Winther
94e7a189b6
Ten tasks. One through five are the domain and run in strict order: day arithmetic, types and the 6 -> 7 migration, the occurrence walk, expected charges, then the fold's second track. Six and seven (actions, import validation) need only the types. Eight and nine are the two UI surfaces. Ten is demo data, documents and screenshots. Task 2 deliberately leaves one test red. The behaviour-preservation guard — every post in every month folds identically, projected equal to remaining — is written where the risk is created and goes green in task 5, where the field it asserts on exists. Writing it out caught four things the spec could not: - A fold assertion of -4000 where the accumulators give 4000. Left in, the implementer would have changed working code to match a wrong expectation. - A second reachable cause for the walk's termination throw. Under lastCharge, a confirmation dated more than one step before the slot it claims moves the cursor backwards; a valid calendar series never can. The message now names both causes, because they need different fixes, and there is a test. - parseMoneyInput takes (text, options, fallback). The options list is what makes "30$" resolve to USD rather than the fallback. - demo-data.ts builds through actions.*, not literals, so the seeding task uses addRecurringCost with the ids already in scope. Task 10 ends by stating what screenshots do NOT prove: how it looks and feels, the overdue count against a real backlog, and whether two-stage confirmation matches how the owner actually reconciles.
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.