Restaurant POS

Superadmin can now create a catering-only plan that gives tenants access to only catering features — no POS, Orders, Kitchen, Tables, Bookings, Promo/Coupon codes, or Disputes.
Plan creation UI simplified: a single "Plan Category" dropdown (Normal Plan / Catering Plan) replaces the old 5-toggle setup.
Normal plans can still optionally add Catering, Inventory, Waste Management, or Attendance as extra modules via checkboxes.

Database migration to prevent an access outage

The new gating required a one-time backfill so existing tenants didn't lose access to core operations (POS/Orders/etc.) the moment this shipped.
Ran the backfill across all plans; verified no tenant lost unintended access.
One live tenant (pizzeria) is on a catering-only plan and now correctly has restricted access — flagged for their awareness since it's a real access change, not a bug.

Dispute management module merged in

Pulled in the dispute-handling feature (dispute schema, service, controller, and the two frontend dispute pages/dialogs) from a separate branch.
Scoped the merge to only the dispute code — deliberately left out unrelated large changes on that branch (e.g. a PhonePe payment integration) to avoid introducing unfinished/unrelated work.
Had to write two small supporting functions (a dispute email notification, and a refund-processing helper) so the dispute code works standalone without the PhonePe dependency.
Verified everything compiles cleanly with zero errors on both backend and frontend.