Skip to content

feat(planning): add reconciled allowances and monthly payments - #97

Draft
suvodeep12 wants to merge 119 commits into
devfrom
feat/personal-finance-planning
Draft

suvodeep12 wants to merge 119 commits into
devfrom
feat/personal-finance-planning

Conversation

@suvodeep12

@suvodeep12 suvodeep12 commented Oct 18, 2026 •

Copy link
Copy Markdown
Collaborator

Summary

Add a local spending allowance based on reconciled liquid balances, full credit-card outstanding, bills through payday and a cash reserve. Expected salary is excluded. Missing balances, unresolved activity or unconfirmed account/card coverage withhold the estimate. Refs #47, #48 and #49; this is a focused subset and does not close those issues.

Changes

  • Add signed balance checkpoints and reconciliation differences without artificial income. Reserve archived debts and support account restore.
  • Persist private payday/reserve setup and monthly bill/card reminders. Preserve paid, edited and removed occurrences; avoid reserving card payments twice.
  • Require separate explicit commitments and account/card coverage confirmations. Legacy setups without account confirmation remain incomplete until the user confirms.
  • Show the oldest tracked checkpoint on Home, explain recorded movements, and display verified versus calculated balances in Settings. No arbitrary checkpoint expiry is invented.
  • Serialize shared-connection finance operations; snapshot validated setup before queued writes. Regression checks cover legacy setup and caller mutation during the queue wait.
  • Add migration 0009_sparkling_toro. No new native dependency, environment variable or signing requirement. Preserve Rohan's Ink and Stamps design.

Testing

  • Clean committed candidate 336e0ce: frozen install; pnpm check (320 mobile tests, 142 parser tests, typecheck and lint); installed-SDK compatibility; Expo Doctor 20/20; Android/iOS/web exports; diff whitespace checks.
  • Focused planning tests and independent review found and fixed missing coverage confirmation, hidden balance freshness and a queued-input snapshot regression.
  • Fresh-origin browser with fictional data: unconfirmed coverage suppresses the allowance; explicit coverage plus INR 10,000 checkpoint and INR 1,000 reserve yields INR 9,000, excluding salary. Setup/result survives reload; verification date and verified/calculated amounts are visible. Mobile dark and desktop light layouts were inspected, with no observed console errors or horizontal overflow. Final combined export was reloaded and the persisted result rechecked.
  • Physical Motorola Edge 60 Pro / Android 17: 24 isolated fictional native seed checks on 336e0ce (18 finance, six SMS/HMAC/storage), followed by nine cold-restart checks. Temporary databases and key were removed; no real inbox or main ledger access occurred.
  • Existing isolated QA APK SHA-256 7d8f421b22588169afdb03350db4a5b331f6eae4763375dcb0c5c62584861904 was verified. Native module/config inputs are unchanged from 74bbc4b. Current JS/storage sources were tested in that development client; this does not certify a standalone release APK.
  • Three pre-existing private QA edits in the author's worktree were preserved and excluded from commits. Full production verification ran in a separate clean checkout, where all tests passed.

Risks / Notes

  • Remains draft and depends on feat(android): connect consented SMS preview and review #89. The branch contains that SMS implementation; review the planning changes separately until feat(android): connect consented SMS preview and review #89 lands. Its live-message, performance, accessibility and release gates remain open.
  • Coverage is a user confirmation, not automatic discovery of omitted accounts. A reminder is not proof of payment; the UI requires acknowledging the recorded payment/reconciliation before clearing it. Card reminders are not linked to individual cards yet.
  • Native screen navigation/TalkBack and iOS remain unverified. Automatic matching, merchant rules, full forecasts and encrypted backup remain later work. Do not use this as the sole financial record yet.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant