Feedback suite clean slate rebuild

When building The Suite (forge-suite, Next/React/TS over lifeos Postgres), do a full clean-slate rebuild, not an incremental port. Use the existing apps (finances Flask app + finance.db, the workspace Flask app, Hevy, etc.) as a reference for features and proven logic (especially money/finance logic), but rebuild properly in lifeos. Do not mirror or cling to old data stores, schemas, or structures. Old surfaces get retired once their Suite replacement is trusted (e.g. finance.db + the Flask finances app are decommissioned after the Suite finance module is live; the SimpleFIN FIN Bridge is repointed to write lifeos Postgres directly, not synced).

Why: clinging to what already exists is exactly how bloat accumulates (two data stores, dead columns, ported cruft, sync layers). The whole point of the rebuild is one clean data layer (lifeos + RLS) with custom-faced modules. Single source of truth.

How to apply: model each domain fresh in lifeos (workspace-scoped + RLS); migrate only the SOURCE data, and regenerate derived/cache tables rather than importing them as baggage; repoint the live pipelines to Postgres; delete the old store + app after verifying. Reference old code for logic, never copy its architecture. Pairs with [[feedback_robust_over_quick]].