wmj
22ad077dab
New tab under the Giving hub, alongside Zakat/Sadaqah/Khairat. Two parts: Donations: amount presets + custom amount, four frequencies (One-Time, Monthly, Quarterly, Yearly), each mapped to its own live Polar.sh checkout link (merchant of record — this app never touches payment details, same 'log intent, don't move money' principle used everywhere else). Design/copy modeled on the sibling moslem03.falahos.my app's existing Support tab, per direct reference. No donation product existed on the Polar account yet, so created one via the Polar API with the user's explicit go-ahead: 'Support Nur Falah' as 4 pay-what-you-want products (one-time + monthly/quarterly/ yearly recurring, quarterly via recurring_interval=month with count=3 since Polar has no native quarterly interval), plus a hosted checkout link for each. Verified all four resolve to genuinely distinct, live Stripe-backed checkout sessions before shipping — moslem03's own checkout.polar.sh URL pattern turned out to be stale/non-resolving; the current correct domain is buy.polar.sh via the /v1/checkout-links API, discovered from Polar's live OpenAPI spec rather than guessed. Partnership section: co-branding and white-label pitch with the VP Sales contact info given directly — info@falahos.my and WhatsApp +60132250691 — reachable via a 'View Partnership Opportunities' link from the donation card, matching moslem03's UX pattern of surfacing partnership discovery from the support flow. Covered by e2e-support.cjs (14/14) — including opening all four checkout links live and confirming each is a genuinely distinct, resolving Stripe checkout session, not a dead or placeholder link. Full regression: all suites pass (one confirmed transient flake on rerun, unrelated to this change).
Nur Falah — Estate & Waqf Suite
Horizon 1 (Prevention Suite) + Horizon 2 (Unlock Programme, pre-pilot demo) from the
Nur Falah PRDs, built as a standalone Svelte 5 + Vite PWA, styled to match the visual
system of the live moslem03.falahos.my (Nur Falah Muslim Companion) app.
Modules
| Module | Horizon | Status |
|---|---|---|
| Faraid Calculator | 1 | Shared calc core, 14 classical cases passing (src/lib/calc/faraid.test.js) |
| Asset Registry | 1 | Local-first, feeds every other module's estate total |
| Wassiyah Generator | 1 | 1/3 meter, heir-exclusion block, jurisdiction-aware export |
| Hibah Tracker | 1 | Shared marad al-mawt guardrail |
| Family Waqf Designator | 1 | Built ahead of scholarly sign-off — see below |
| Digital Beneficial Claims | 2 | Pre-pilot demo only — see below |
Important: two governance gates were overridden for this build
Per explicit product direction, this build proceeded past two gates stated in the project's own PRDs and review log:
- Family Waqf Designator (Horizon 1 PRD §8.5) is gated on scholarly sign-off.
scholarly-review-log.md(in thedigital-waqifdocs repo) tracks OPEN-01 — whether a healthy-state waqf is subject to the one-third cap — as unresolved. This module ships anyway; the in-app copy states the open question rather than presenting invented certainty. - Horizon 2 (Digital Beneficial Claims) PRD states: "No engineering work begins until Phase 0 (legal opinion + signed institutional partner agreement) is complete." No confirmation of Phase 0 completion was available. The Claims module ships as a local, non-custodial demonstration of the data model and transfer restriction only — no real legal wrapper, no institutional integration, no real claims issued. It carries a persistent in-app banner saying so.
Both are flagged here, in deploy/DEPLOY.md, and in the relevant module's source
comments so this isn't silently presented as production-ready.
Development
npm install
npm run dev # http://localhost:5173
npm run test # classical faraid test suite
npm run build
Deploy
See deploy/DEPLOY.md. Target: moslem04.falahos.my.