204 Commits

This Branch

This Branch

All Branches

Author	SHA1	Message	Date
soroush.asadi	2a24798a59	feat(audit): show actor full name + role in logs, click to view details ... Logs showed the raw User ID (ActorName was almost never stored) and an English role enum. Now: - AuditController resolves each entry's actor to the employee's CURRENT full name and localized role at read time (joins Employees with IgnoreQueryFilters, so it also names soft-deleted staff and fixes all historical rows — no migration). - The audit table renders "Full name (Role)" with the role localized (fa/en/ar); the name is a button that opens an employee-details dialog. - New EmployeeDetailsDialog: fetches the employee and shows name, role, phone, base salary, and an "Open in HR" link; handles removed staff gracefully. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-06-21 11:24:06 +03:30
soroush.asadi	6d71770f2e	fix(auth): redirect already-signed-in users away from the register page ... Mirrors the login guard: visiting /register while authenticated redirects to the dashboard home (/) instead of showing the form. Gated on _hasHydrated; shows a brief redirecting state. Reuses the existing auth.redirecting string. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-06-21 11:11:10 +03:30
soroush.asadi	fd1f985597	fix(auth): redirect already-signed-in users away from the login page ... Visiting /login while authenticated now redirects to the app (/pos) instead of showing the login form again. Guarded on _hasHydrated so the not-yet-rehydrated (null) session isn't misread, and renders a brief "redirecting" state instead of flashing the form. fa/en/ar strings added. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-06-21 10:39:27 +03:30
soroush.asadi	d261c13175	docs(website): note KDS station tabs in the kitchen-display guide ... Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-06-21 10:29:15 +03:30
soroush.asadi	958addf734	feat(kds): filter the kitchen display by station (kitchen / bar) ... Complements the separate kitchen/bar printers with an on-screen split. The live order DTO now carries each item's prep station (MenuItem → Category → KitchenStation), and the KDS shows station tabs (All / Kitchen / Bar / …) that appear only once ≥2 stations are in play. Selecting a station shows just the tickets — and just the items within each ticket — for that station, so bar staff see drinks and kitchen staff see food. Single-station cafés see the board unchanged. fa/en/ar strings added. Note: order status is still per-order (one advance button); the split is for viewing/printing, not per-item status. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-06-21 10:27:40 +03:30
soroush.asadi	8703e9cf87	docs(website): knowledge-base guide for printing (receipt, kitchen, bar) ... Documents the new separate kitchen/bar print stations plus the customer receipt (factor): how to set printer IPs, create Kitchen/Bar stations, route menu categories to a station, and what auto-prints at send-to-kitchen vs payment. fa/en; auto-listed on /docs and in the sitemap. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-06-21 09:58:22 +03:30
soroush.asadi	fb6a20eaa1	feat(print): separate kitchen & bar printers via print stations UI ... The print engine already routed items to per-station printers (MenuCategory → KitchenStation.PrinterIp, falling back to the branch kitchen printer) and prints the customer receipt to the receipt printer — but there was no UI to set it up. This exposes it: - Settings → "Kitchen & bar printers": create/edit/delete print stations, each with its own printer IP/port, with a per-station test print (gated by ManageKitchenStations). - Menu category editor: a "Print station" dropdown to route each category to a station (food → Kitchen, drinks → Bar); no station = branch kitchen printer. Result: kitchen and bar tickets print on separate printers, while the customer factor/receipt keeps printing on the receipt printer. fa/en/ar strings added. No backend/migration changes — purely wiring the existing capability. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-06-21 09:56:14 +03:30
soroush.asadi	97bd63015f	docs(website): knowledge-base guides for notifications & roles + sitemap docs pages ... The recent dashboard features shipped without knowledge-base coverage. Adds two fa/en guides at meezi.ir/docs: - "Notifications & sound" — bell/unread count, configurable sound (chime + volume + preview), desktop/Windows popups, browser-tab counter, and click-to-navigate to the related page. - "Roles & permissions" — base roles, defining custom roles via the permission matrix (CRUD + sensitive actions), assigning them, and how page/action access is enforced. Also fixes a standing SEO gap: the sitemap listed only /docs, never the per-feature /docs/{slug} pages — now all guide pages (fa+en) are included so the whole knowledge base is crawlable. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-06-21 07:19:23 +03:30
soroush.asadi	3dfcb1585b	feat(notifications): click a notification to jump to its related page ... Every notification surface now deep-links to where the staff member needs to act: - bell dropdown: clicking an actionable notification navigates and closes the dropdown (platform broadcasts still expand inline to show their text) - notifications page: rows navigate to the right page - in-app toast: gains a "View" action button - desktop/Windows popup: clicking it focuses the tab and navigates Routing is now permission-aware via a single resolver (notification-routes.ts): a new-order alert sends a kitchen user to /kds, a cashier to /pos, and a floor user to /tables — never to a page their role can't open; a waiter call → /tables. This also fixes the old bug where table_call_waiter (which carries a referenceId) wrongly routed to /kds. Toast/desktop clicks navigate client-side through a small event bridge mounted in the dashboard shell. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-06-21 06:08:18 +03:30
soroush.asadi	2cff5051ac	feat(rbac): gate pages and action buttons in the UI by permission ... Nav already hides pages a role can't view (NAV_REQUIRED_PERMISSION). This wraps the sensitive/CRUD action controls in <Can permission> so users only see what they can do (server still enforces): - POS/orders: void → VoidOrder, cancel → VoidOrder, transfer → EditOrder, pay/split → HandlePayments - menu/inventory/coupons/customers/reservations/expenses/taxes/branches: add/edit/delete buttons → the matching Create/Edit/Delete permission - reports CSV export → ExportReports; SMS send → SendSms, settings → ManageSmsSettings - home dashboard: revenue/orders KPI queries gated on ViewReports so non-report roles don't 403 on the landing page (Refund/discount/comp/cash-drawer have no UI control yet — no buttons to gate.) Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-06-21 05:58:56 +03:30
soroush.asadi	53d90fa357	feat(rbac): full permission catalog in the custom-role matrix UI (fa/en/ar) ... Mirrors the expanded backend catalog on the client: the Permission type and the custom-role permission matrix now expose all ~80 capabilities grouped into 16 sections (admin, branches, menu, inventory, taxes, staff, tables, orders, register, queue/kitchen, delivery, customers, coupons, marketing, reports, expenses), each with fa/en/ar labels. Nav visibility now maps each page to its View permission; taxes & branches become permission-driven (managers can view), leaving billing as the sole hard owner-only nav gate. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-06-21 05:49:11 +03:30
soroush.asadi	7a5ea75b50	feat(rbac): enforce permissions on every café write endpoint ... Closes the gap where the custom-role matrix was defined but unenforced — most write endpoints only checked café membership, so the API would accept writes a role's UI hid. Adds EnsurePermission(...) to all mutating/sensitive endpoints across 32 controllers, mapped to the granular catalog: - menu/inventory/coupons/customers/expenses/reservations/taxes/branches → CRUD perms - tables/queue/kitchen-stations/print-settings → manage perms - orders → ProcessOrders / EditOrder / VoidOrder / UpdateOrderStatus / HandlePayments, payment corrections → ManageFinancials - HR → CreateStaff / ManageSchedules / ReviewLeave / View+ManageSalaries / ManageStaffCredentials (self-service clock-in/leave preserved) - reports → ViewReports, export → ExportReports, audit → ViewAuditLog - billing → ManageBilling, sms → SendSms/ManageSmsSettings, reviews → ManageReviews, discover/public profile → ManageDiscoverProfile, café settings → ManageCafeSettings, custom roles → ManageRoles Removes legacy [Authorize(Roles=...)] attributes that would have overridden the permission model (orders, branch-menu, pos-device, print). Manual discount/comp have no backend endpoint yet (discounts come from coupons) — gated on the POS UI. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-06-21 05:43:07 +03:30
soroush.asadi	236013f53c	feat(rbac): full-CRUD permission catalog + per-role matrix ... Expands the authorization catalog from 21 coarse page-level permissions to a granular set: View/Create/Edit/Delete per record module, plus distinct permissions for sensitive actions (VoidOrder, RefundOrder, ApplyDiscount, CompOrder, OpenCashDrawer, ExportReports) and the previously-uncovered pages (customers/CRM, SMS, reviews, financials, audit log, attendance, schedules). RolePermissions now derives Manager as "everything except owner-only governance" and gives Cashier/Waiter/Chef/Delivery sensible day-to-day defaults; owners refine further via custom roles. Effective permissions already flow to the client through AuthService, so no token-shape change is needed. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-06-21 05:27:02 +03:30
soroush.asadi	170a9aa7ac	feat(dashboard): Notifications & sound settings panel (fa/en/ar) ... New Settings → "Notifications & sound" leaf to make the alert channels changeable: toggle sound (+ picker with live preview + volume slider), enable desktop notifications (permission flow + test button), toggle the tab unread badge and in-app toasts. Strings added for fa/en/ar. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-06-21 05:08:39 +03:30
soroush.asadi	149a4d88cd	feat(dashboard): configurable notification sound, desktop popups & tab unread badge ... Per-device notification preferences (localStorage) drive three new alert channels in the dashboard shell, all fed by the existing SignalR NotificationReceived events: - Sound: 6 selectable procedural Web Audio chimes + volume, no asset files. - Desktop/Windows popups via the Notification API, fired only when the tab is backgrounded (in-app toast covers the focused case). - Unread count on the browser tab: (N) title prefix + numbered favicon badge. useOrderAlerts is now the single orchestrator (sound + toast + desktop), each gated by prefs; topbar feed enableToasts disabled to avoid double toasts. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-06-21 05:08:02 +03:30
soroush.asadi	aebfa825cd	feat: custom roles with per-permission matrix for café owners ... - Owner can define named custom roles (e.g. Barista, Supervisor) with color, description, and a fine-grained permission set (21 permissions across 7 categories: admin, menu, staff, customer, reports, ops, kitchen) - Employee assigned a custom role gets its permissions embedded in the JWT at login (customPerms claim) and parsed by TenantMiddleware — overrides the static EmployeeRole matrix for all API permission checks - New endpoints: GET/POST/PATCH/DELETE /api/cafes/{id}/custom-roles and PUT /api/cafes/{id}/employees/{id}/custom-role for assignment - Dashboard Settings → Team & Staff → Custom Roles panel with grouped checkbox matrix, group-level toggles, color preset picker, CRUD forms, and employee-count display; translations in fa/en/ar - EF migration adds CustomRoles table + nullable CustomRoleId FK on Employees - POS slip now shows per-item notes on both thermal print and bill preview Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>	2026-06-21 03:12:43 +03:30
soroush.asadi	73a5e5183b	fix(seed): IgnoreQueryFilters on all seeder queries + sitemap invalid date guard ... DemoSeedService / DemoMenuSeeder: Add IgnoreQueryFilters() to every seeder lookup (Taxes, MenuCategories, MenuItems). Soft-deleted rows still hold their PKs; without this a second seed run after user-deletion throws a PK collision on the Tax or category that was soft-deleted but is still in the index. sitemap.ts: Guard new Date(post.date) against empty / missing frontmatter date fields. new Date("") = Invalid Date → broken <lastmod> in sitemap XML. Fall back to the build-time date when the post date is absent or invalid. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>	2026-06-20 15:54:07 +03:30
soroush.asadi	1daa6d452c	fix(admin): admin OTP login always failed — rate-limit key clobbered the OTP ... The admin send-otp used the SAME Redis key ("otp:admin:{phone}") for both the OTP value and the per-hour attempts counter. After storing the code and SMSing it, the rate-limit StringIncrementAsync ran on that same key, turning the stored value into code+1 (e.g. SMS said 337835, Redis held 337836). verify-otp then compared the entered code to the incremented value, never matched, and returned INVALID_OTP → 400. Admin OTP login could never succeed. Give the attempts counter its own key ("otp:admin:attempts:{phone}"), exactly like the main API (otp:{phone} vs otp:attempts:{phone}). Password login was unaffected. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-06-17 08:42:45 +03:30
soroush.asadi	24fbbcb01c	fix(admin): don't prefill a fake phone on the admin login in production ... The admin login OTP tab hard-coded phone "09120000001" as the initial value. In production that placeholder belongs to no SystemAdmin, so hitting "send code" returns NOT_FOUND → 404 (which WCDN then repaints as an HTML error page) — it looked like the login endpoint was broken. Keep the convenience prefill in development only; ship an empty field in production so the admin types their real number (e.g. the registered admin phone). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-06-17 00:44:57 +03:30
soroush.asadi	a967e5d211	fix(admin): keep admin panel logged in — refresh the token instead of dying at 7 days ... Prod diag showed every /api/admin/* call returning 401 with "IDX10223: token expired, ValidTo 06/09" — the admin access token was 6 days dead and nothing renewed it, so cafes/tickets/integrations/settings all loaded empty. The admin web (unlike the café dashboard) had NO refresh logic at all: it only ever sent the access token, and its 401 handler early-returned on any error code before the login redirect, so the admin wasn't even bounced to login — pages just showed no data. Client (admin-client.ts): add a silent refresh-on-401 mirroring the dashboard — one shared in-flight POST /api/admin/auth/refresh for a burst of 401s, replay the original request on success, force-logout only on a definitive 4xx, and ride out a transient failure (API restarting during deploy) without logging out. Backend (AdminAuthService): make refresh non-rotating + sliding (reuse the presented refresh token and re-store it) instead of revoke-and-mint, so the dashboard's many concurrent refreshes don't race the rotated token — same fix already applied to the main API. Also bump admin tokens 7d/30d → 30d/365d to match the main API, so the session is long-lived even before the first refresh round-trip. tsc clean; Admin.API builds clean. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-06-15 20:57:21 +03:30
soroush.asadi	82d1cf8e9e	fix(auth): stop logging users out on every deploy ... Diagnostic on prod confirmed the backend keeps sessions valid across deploys (stable 64-char JWT key, 30-day access tokens, 62 refresh tokens persisting in Redis with appendonly; redis/db never restart on deploy). The forced logout was client-side: 1. The axios refresh path treated ANY refresh failure as "session gone" and nuked the tokens. During the ~30s API restart window of a deploy, the refresh POST gets a 502/timeout (transient) → user kicked to /login. Now refresh distinguishes a definitive 4xx (truly invalid/expired refresh → log out) from a transient network/5xx failure (reject + keep the session; retry later). Refresh tokens are opaque Redis GUIDs, so they survive even a key rotation — the only thing that was breaking sessions was this over-eager logout. 2. PWA service worker served a stale app shell after an update, pointing at JS chunks the new build replaced. Added skipWaiting + clientsClaim + cleanupOutdatedCaches and a NetworkFirst handler for navigations so the HTML and its chunk refs always match the live deploy; hashed static stays CacheFirst. Net: a normal update no longer logs anyone out. tsc clean. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-06-15 20:42:38 +03:30
soroush.asadi	837805b6b8	fix(brand): real Meezi launcher icon for meezi_app (was default Flutter) ... Replaced the placeholder Flutter launcher icons in all 5 mipmap densities (48/72/96/144/192) with the real Meezi mark, ready for the Android APK build. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-06-15 19:52:34 +03:30
soroush.asadi	d4d7b7e679	feat(website): full Meezi knowledge base with per-feature wireframes ... Turns the static /docs page into a real help center. Every feature now has a detail page at /docs/{slug} with a minimal wireframe mockup + concrete Persian how-to steps (English mirror), grouped into 6 sections. - guide-data.tsx: typed GUIDE_FEATURES (21 features — pos, tables, kds, queue, reservations, menu, inventory, crm, coupons, sms, reviews, reports, expenses, shifts, taxes, hr, branches, subscription, settings, qr-menu, koja) with fa/en title, tagline, 5–8 steps, tips, tier badge, group, wireframe variant. - wireframes.tsx: 7 reusable minimal line-art variants (board/order/menu/list/ dashboard/form/phone), brand-colored, RTL-aware. - docs/[slug]/page.tsx: dynamic guide page (hero, wireframe + numbered steps, tips, prev/next, support CTA); generateStaticParams + generateMetadata; 404 for unknown slugs. - docs/page.tsx: module cards now sourced from GUIDE_FEATURES, grouped, linking to the detail pages. Verified via SSR: index lists all 21, detail pages render titles + wireframe, en mirror 200, unknown slug 404, tsc clean. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-06-15 19:00:10 +03:30
soroush.asadi	32a7cf5b25	ops: nightly DB backup + self-hosted uptime monitoring ... Backup (production data-loss protection — was none): - meezi-backup sidecar in docker-compose.yml runs pg_dump nightly at 02:00 Tehran, gzip, 14-day rotation, atomic .partial→final, into ./backups (persists across deploys; rsync off-box per RESTORE.md). - Wired into the deploy job (up -d --no-deps backup); takes one dump on boot. - scripts/backup/pg-backup-loop.sh + RESTORE.md (restore + off-box guidance). Monitoring: - docker-compose.monitoring.yml: Uptime Kuma stack (own volume), stood up once, independent of app deploys. - Caddyfile status.{$DOMAIN} route; docs/monitoring.md lists the exact monitors (incl. /q guest-menu 200 check) + TLS-expiry alerts (catches the ~90-day cert breakage early) + alert-channel setup. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-06-15 18:45:07 +03:30
soroush.asadi	d407f0b3e9	fix(brand): real Meezi icon/favicon on website + admin (was missing) ... - web/website: manifest referenced /icon-192.png and /icon-512.png that didn't exist (broken favicon). Added the real transparent Meezi mark (32/180/192/512) + wired icons into metadata. OG image stays dynamic. - web/admin: had no metadata or icons at all. Added title template, favicon/apple icons (icons/ dir), themeColor, noindex. Dashboard + Koja already carry the real logo; web apps are now consistent. Mobile launcher icons will be handled with the Android packaging task. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-06-15 18:37:21 +03:30
soroush.asadi	72ab09189c	fix(brand): real transparent Meezi icon + guest-menu image placeholder ... - Icons/favicon were a plain solid-green square (a 547B placeholder). Replaced with the actual Meezi mark (green rounded square + menu lines) on transparent corners, generated at 32/48/180/192/512 + a full-bleed green maskable-512. Wired 32/48 favicon + 180 apple-touch-icon into the panel and /q metadata. Copied the same icons to Koja for consistent branding. - Guest QR menu showed blank muted boxes for items without a photo. Added a minimal themed café-cup placeholder (MenuImageFallback) across all four layouts so the menu looks intentional. (Admin/POS already had placeholders.) Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-06-15 18:17:52 +03:30
soroush.asadi	456a446850	feat(meta): per-page titles + favicon/app icons + PWA across the panel ... The app had no metadata anywhere — pages showed no <title> and no favicon or app icon. Added: - Root metadata in [locale]/layout: title default + "%s — میزی" template, description, icons (favicon + apple-touch-icon → /icons), manifest link, appleWebApp, themeColor viewport, noindex (private panel). - Per-page title on all 22 dashboard route pages (داشبورد, منو, گزارش‌ها, …). - Guest menu (/q) layout: own title + icon + manifest. PWA + favicon now use the Meezi icon everywhere. Verified via SSR: titles render (e.g. "منو — میزی") and icon/manifest/apple-touch-icon links present. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-06-15 15:47:00 +03:30
soroush.asadi	4523c8861f	feat(ui): grouped thousands separators for price/amount inputs ... Price fields showed raw digits (1490000) while typing — hard to read for Toman amounts. New shared MoneyInput groups as you type (1,490,000), accepts Persian/Arabic digits, and reports a raw digit string so callers keep parsing unchanged. Applied to menu item price, branch price override, expense amount, and payment-correction replacement amount. Displays already group via formatCurrency (incl. the QR guest-menu preview). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-06-15 15:46:25 +03:30
soroush.asadi	a855cf1d80	feat(auth): admin-issued café recovery key login ... Platform admins can generate a permanent recovery key per café (admin panel → Cafés). The café Owner uses it to sign in when OTP access is lost; once authenticated, all server-side data syncs as normal (data is per-café on the server, the device only caches it). Backend: - Cafe.RecoveryKeyHash (SHA-256, unique index) + RecoveryKeyCreatedAt; migration - RecoveryKeyGenerator util: MZ-XXXXX-XXXXX-XXXXX-XXXXX, ~190-bit entropy, stored as SHA-256 (API-token pattern — raw key shown once, never retrievable) - Admin: POST/DELETE /api/admin/cafes/{id}/recovery-key (key returned once); café list now reports HasRecoveryKey + RecoveryKeyCreatedAt - Login: POST /api/auth/login-key → exact-hash lookup → resolves café Owner → issues normal JWT; rate-limited (auth-otp), suspended/no-owner guarded, logged Admin UI: per-café generate / regenerate / revoke with one-time reveal + copy. Dashboard login: discreet "ورود با کلید بازیابی" link → key field. fa/en/ar. 86 tests pass; all tsc clean. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-06-15 15:10:11 +03:30
soroush.asadi	76d4434581	fix(qr): guest menu 500 (SSR) + remove café discovery from owner panel ... 1. The /q/{code} guest menu returned HTTP 500 on every load. Root cause: menu-item-model-viewer.tsx did a top-level `import "@google/model-viewer"`, a browser-only lib that touches `self` at module evaluation. Next pulled it into the server module graph (page → qr-guest-menu → qr-menu-3d-sheet → model-viewer) and SSR crashed with "self is not defined". Now the library is imported lazily inside useEffect (client-only); a poster placeholder shows until the custom element registers. Verified /q/* now returns 200. 2. Removed the "discover" (browse other cafés) item from the café owner sidebar — café discovery belongs in Koja, not the owner panel. The owner still manages their OWN Koja listing from Settings. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-06-15 15:08:48 +03:30
soroush.asadi	9765491f6f	fix(prod): payment/tax gateways never fake success outside Development ... Production-readiness audit fixes — every mock fallback is now gated on IsDevelopment; in production these paths fail loudly instead: - ZarinPal/Tara/SnappPay init: missing credentials returned a MOCK payment URL whose callback verified as paid — a café could activate a paid plan without paying. Now: "Payment gateway is not configured." - Tara/SnappPay verify: a forged MOCK-* trace/token on the callback was accepted as a verified payment in any environment. Now rejected outside Development. - Taraz (سامانه مودیان): returned a fake MOCK-TARAZ tracking code as if invoices reached the tax authority. Now returns an honest error (the real integration is not built yet). - Admin integrations: NextPay/Vandar removed — they were listed but have no gateway implementation (selecting them silently used ZarinPal). - docker-compose: ASPNETCORE_ENVIRONMENT default flipped Development → Production so a missing env var can never run prod in dev mode. 86 tests pass. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>	2026-06-12 10:16:01 +03:30
soroush.asadi	00649d0248	feat(sms): bring-your-own-provider — cafés use their own SMS account ... The platform no longer sells SMS. Each café saves its OWN Kavenegar API key + sender line (new Cafes columns + migration) and campaigns are sent and billed through that account. Backend: - GET/PUT /sms/settings (Manager/Owner; key echoed masked, verified against the provider before saving) - campaign + balance use the café's credentials; SMS_NOT_CONFIGURED error when missing; plan-tier SMS gating removed everywhere (PlanLimitChecker, SmsMarketingService, billing status) - platform Kavenegar config stays ONLY for login OTPs (env/DB) - design-time DbContext factory so `dotnet ef migrations add` works without booting the host Dashboard: - SMS screen: provider-settings card, not-configured callout, campaign form disabled until configured; quota bar removed (usage stays as info) - subscription screen + plan comparison no longer show SMS limits Admin panel: - Kavenegar/SMS section removed from integrations (request field now optional; stored OTP config untouched) - SMS limit field removed from the plan editor - nav label "درگاه و پیامک" → "درگاه پرداخت و AI" fa/en/ar translations. 86 tests pass; all tsc clean. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>	2026-06-12 09:23:50 +03:30
soroush.asadi	615d5348de	fix(subscription): plan comparison + checkout read the live plan catalog ... The merchant plan page hard-coded 4 tiers, prices and a feature matrix that drifted from the admin-editable platform catalog (Starter tier missing, stale prices/features). PlanComparison and CheckoutScreen now consume /platform/plans + new /platform/features-catalog: - columns = active plans by SortOrder (incl. Starter), names from DisplayNameFa/En, prices from MonthlyPriceToman - limit rows from PlanLimitsData (int.MaxValue → "نامحدود") - feature rows from the feature catalog, ticked via FeatureKeys - checkout validates the ?plan= param against isBillableOnline and prices from the catalog — no more client-side price constants fa/en/ar limit-row labels added. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>	2026-06-12 08:16:29 +03:30
soroush.asadi	74f46a4781	fix(dashboard): Set spread → Array.from for CI tsconfig target ... Local tsconfig.json has uncommitted target changes, so `[...voidIds]` passed locally but failed CI's tsc (TS2802, target < es2015). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>	2026-06-12 01:30:21 +03:30
soroush.asadi	c47922414a	feat: اصلاح سند payment corrections + audit-log & daily P&L views ... Backend: - POST /orders/{id}/payments/corrections (Manager/Owner): void wrong payments (marked Refunded, never deleted) and/or record replacements atomically; mandatory reason; requires an open register shift; full before/after written to the immutable audit trail. - GET /orders/closed?date= — closed orders of one Iran-calendar day, paged, the browsing surface for corrections. - CalculateExpectedCash now subtracts cash refunds so corrections keep the drawer expectation honest. Dashboard (reports screen now has three tabs): - عملکرد و سود: existing KPIs/charts + new day-by-day breakdown table (orders, revenue, expenses, net profit per Jalali day). - اصلاح سند: closed-orders browser with payment chips + correction dialog (void checkboxes, replacement rows, live balance, reason). - گزارش عملیات: filterable audit-log viewer (category, Jalali range, branch) with expandable structured details. fa/en/ar translations included. 86 backend tests pass; dashboard tsc clean. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>	2026-06-12 01:24:19 +03:30
soroush.asadi	2a4cf1d20b	feat(dashboard): Jalali date pickers + mobile/tablet responsive shell ... Full Persian calendar: - New JalaliDateField — Shamsi popover picker (Saturday-first weeks, Persian digits, امروز shortcut); wire format stays ISO Gregorian YYYY-MM-DD. Falls back to the native input for the en locale. - Replaces all 5 native type="date" inputs (Gregorian-only pickers): reservations, expenses from/to, reports from/to. - Reservations list date now renders Jalali instead of the raw ISO string; branches purge timestamp now formats with fa-IR. Responsive shell (mobile + tablet): - New MobileNav: hamburger in the topbar (< md) opening an RTL-aware slide-over drawer with all nav destinations, permission-filtered, Escape/backdrop close and body scroll lock. - Desktop sidebar hidden below md; header center cluster (clock/plan) hidden below md; language switcher hidden below sm. - Main content padding scales p-3 → p-4 → p-6. - Verified at 375px and 768px: no horizontal overflow, drawer and Jalali picker fully functional. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>	2026-06-11 23:10:38 +03:30
soroush.asadi	d811b7d6d5	feat(dashboard): simplify navigation — frequency-based IA ... The sidebar had 22 items in 5 accordion groups, all defaulting closed: first visit showed five vague headers and zero destinations, there was no Dashboard/Home link at all, and rare pages (taxes, subscription) had equal weight with POS. Restructured around usage frequency: - Flat primary (always visible, no header): Dashboard, POS, Tables, Kitchen, Queue, Reservations, Menu, Reports - Two collapsible groups: Customers & marketing (crm, coupons, sms, reviews, discover) and Café management (inventory, expenses, shifts, taxes, hr, branches) - Footer utility icons: settings, subscription, support - Removed "notifications" from the nav (duplicate of the topbar bell) Other fixes folded in: - Deleted [locale]/page.tsx which redirected "/" to /pos — it made the POS exit button a no-op loop and left OverviewScreen unreachable. "/" now renders the overview home; login still lands on /pos. - Branch gating moved from group-level to an item whitelist (BRANCH_ALLOWED_NAV_KEYS) — also closes the hole where branch accounts could deep-link to /reports etc. past the RouteGuard. - RouteGuard now checks footer items too (subscription stays gated). - revalidate=300 on the locale layout: Next emitted s-maxage=31536000 and the WCDN edge kept serving year-old HTML shells after deploys. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>	2026-06-11 22:06:59 +03:30
soroush.asadi	e0c786fcd1	ci: drop AIA cert fetch — mirror chain is fixed at the source ... Run 77 diagnostics proved http://yr.i.lencr.org/ connects but never responds from the runner (national filtering), so fetching ISRG Root YR at build time can never work. Meanwhile the mirror's fullchain.pem now serves the complete chain: leaf → YR2 → ISRG Root YR cross-signed by ISRG Root X1, which IS in every stock trust store — verified with strict curl (ssl_verify_result=0) and openssl verify. Replace both Trust steps with a cheap s_client sanity check that fails early with a pointer to the server-side fix if the cert regresses on its ~90-day renewal. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>	2026-06-11 21:29:31 +03:30
soroush.asadi	bafbfbcadf	ci: fix Trust step crash in sh — replace pipefail with POSIX set -eu ... Gitea act runner v0.6.1 ignores `shell: bash` step overrides and always executes with `sh -e {0}`. The `set -euo pipefail` on line 2 caused sh to exit immediately with "Illegal option -o pipefail" before any curl/openssl ran. Replace with POSIX-compatible `set -eu` in both api-build and admin-api-build trust steps so the diagnostic curl output is finally visible. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>	2026-06-07 08:28:52 +03:30
soroush.asadi	206cd7d3c3	ci: fix Trust step — add shell: bash (act runner defaults to sh, no pipefail) ... set -euo pipefail is bash-only; Gitea act runner used sh by default so the step crashed on line 1 before curl even ran. Adding shell: bash lets the step actually execute and surface the real AIA/cert output. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>	2026-06-07 08:17:54 +03:30
soroush.asadi	7b77bb4722	ci: verbose diagnostic Trust step to pinpoint PartialChain cause ... Previous attempt used curl -sf which silently swallows failures, so we never knew if ISRG Root YR was actually fetched. This run: • set -euo pipefail → step fails fast and loudly on any error • curl -v → shows connection result / error in log • openssl verify → confirms cert bundle is good before restore • openssl s_client → shows full chain verify against live mirror If the AIA URL (http://yr.i.lencr.org/) is unreachable from the runner, the step will fail HERE rather than silently at dotnet restore. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>	2026-06-07 08:09:18 +03:30
soroush.asadi	1db8a8f08c	fix(ci): fetch ISRG Root YR root cert at build time + belt-and-suspenders ... The prior Trust step added only the YR2 intermediate to the OS trust store. dotnet's X.509 chain builder requires a self-signed ROOT as the trust anchor (it does not enable OpenSSL's X509_V_FLAG_PARTIAL_CHAIN), so intermediate-only still caused PartialChain. New approach (two jobs: api-build, admin-api-build): 1. curl http://yr.i.lencr.org/ (plain HTTP AIA) → ISRG Root YR DER → convert to PEM → add to /usr/local/share/ca-certificates/ 2. cp YR2 intermediate (docker/nexus-mirror-ca.crt) → same dir 3. update-ca-certificates (OS method) 4. cat both certs >> /etc/ssl/certs/ca-certificates.crt (belt-and-suspenders: directly appends to the OpenSSL bundle dotnet reads on Linux, works even if step 3 is a no-op) If the AIA fetch fails (network block) step 4 still appends the intermediate, which may work if dotnet ever enables partial chains. Fetch failure is non-fatal (echo warning + continue). Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>	2026-06-07 07:34:52 +03:30
soroush.asadi	82145b0d21	feat(pos2): add dashboard exit button to POS board header ... POS runs in the (fullscreen) layout which strips the sidebar. Adds a Home → داشبورد button at the top-left of the table board so users can navigate back to the dashboard without being stuck. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>	2026-06-07 07:23:14 +03:30
soroush.asadi	59486cdf24	fix(pos2): wait for branch before fetching menu + add left category sidebar ... Race fix: orderBranchId now returns `undefined` (not null) while the /branches query is in flight. usePos2Menu treats undefined as "not yet determined" and skips the fetch, preventing getBranchMenu(cafeId, null) → empty array. Once branchesFetched=true, orderBranchId resolves to the correct branchId (or null for café-wide fallback). Layout: desktop order screen now shows a left vertical category sidebar (116 px, md+) instead of horizontal chips, giving the classic POS sidebar feel. Horizontal chips kept for mobile (<md). Menu grid columns adjusted. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>	2026-06-07 07:10:03 +03:30
soroush.asadi	f02f78a97c	fix(pos): POS v2 menu empty — resolve a valid branch like classic POS ... The menu/tables are branch-scoped. v2 used the raw stored branchId, which is null or stale for users who never opened the classic POS (it has no branch picker), so getBranchMenu returned an empty menu. Now v2 fetches /branches, auto-selects the first valid branch (self-healing the stored id), and loads the branch menu + tables + order submission against that resolved branch — matching the classic POS exactly. Also adds a visible "menu failed to load / retry" state instead of a silent empty grid. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-06-04 06:17:37 +03:30
soroush.asadi	cc0933c514	fix(auth): don't log out fullscreen routes (POS/queue) on refresh ... The (fullscreen) layout redirected to /login whenever user.accessToken was falsy — but on a page refresh that fires before Zustand finishes rehydrating the persisted auth from localStorage, so an authenticated user was bounced to login on every refresh. Gate the redirect on _hasHydrated (and show a loader while rehydrating), matching RouteGuard. Tokens themselves are already long (30d access / 365d refresh), so sessions now survive refreshes as expected. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-06-04 05:56:11 +03:30
soroush.asadi	7c35984096	feat(pos): default the pay sheet to Card ... Card is now the pre-selected payment method (and split rows default to Card), matching Iran's card-dominant payments. Card already sits first in the selector. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-06-04 05:38:13 +03:30
soroush.asadi	bf0ca68fa6	feat(pos): show Card first in pay sheet, keep Cash as default ... Reorder the payment method tabs to کارت / نقدی / تقسیم (Card first, most common in Iran) while keeping Cash as the pre-selected default method. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-06-04 05:32:26 +03:30
soroush.asadi	6778c32028	feat(pos): POS v2 feature parity + promote to default /pos ... Completes the four POS v2 roadmap items: 1. Real split payments — split tab records N separate payment rows (equal split, last row takes the remainder), each row toggles Cash/Card; posts payments[]. 2. Card-terminal push — confirmPay sums Card amounts and calls requestPosPayment (POS device) before recording; surfaces POS_DEVICE_* errors. 3. Customer + coupons + loyalty — reuses PosCustomerPicker (attach/search/create) and validates coupons via /coupons/validate (discount in totals). Pay sheet offers loyalty redemption (1 point = 100 toman) when a customer is attached. 4. Promote to default — /pos now renders POS v2 (full-screen, café-themed); the classic terminal moves to /pos-classic with its sidebar+topbar chrome. The "نسخه کلاسیک" link points there. Order submission already carried customerId/guestName/guestPhone/couponId via the shared cart store, so customer + coupon flow straight through send + pay. tsc --noEmit clean. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-06-04 05:16:52 +03:30
soroush.asadi	75a0a1c834	feat(pos): wire POS v2 to live data (board, orders, payments) ... POS v2 is now a real, working point of sale at /[locale]/pos2 (was a static mock). It reuses the existing data layer so it shares the React Query cache and offline pipeline with the classic POS: - Table board ← fetchCafeTableBoard (Free/Busy/Reserved/Cleaning, live totals, guest-QR badge); polls every 15s. Open a free table to start an order; open a busy table to hydrate its existing order (GET order → cart hydrateFromOrder). - Order screen ← real branch/café menu + categories, bound to useCartStore (add/qty/remove). Send via submitOrderToApi (online + offline outbox) then re-hydrate; "ارسال (n)" shows the pending (unsynced) line count. - Pay sheet ← POST /orders/{id}/payments. Cash (numpad + change), Card, and a Split helper (records the full amount; split is cashier guidance for now). - Online/offline badge, loading/empty states, toasts, busy overlay, and a "نسخه کلاسیک" link back to /pos. The static design mock stays at /[locale]/pos2-preview (dev-only, 404 in prod). tsc --noEmit clean. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-06-04 00:16:37 +03:30