Skip to content
Tadhkir
▾
General

Changelog

What changed in Tadhkir, and when

Changelog

All notable changes to Tadhkir are documented here.

The format follows Keep a Changelog, and the project adheres to Semantic Versioning.

Started 2026-08-03. History before this date lives in docs/BUILD_STATUS.md, the reports in docs/report/, and the git log.


[Unreleased]

Added

  • The schools flyer pack and the /schools landing page. Three flyers, because three different people read them: what an affiliate posts in a school-owners group, the A4 one-pager left on a proprietor's desk, and the notice a school sends parents in all five languages its parents read. Every word is in lib/flyers/school-copy.ts and every number in it is derived — the price from BASE_MONTHLY, the notice counts from the template library, the open rate from the benchmark that records its source — so the printed paper and the website cannot disagree. A test asserts no flyer claims a customer outcome, which site-facts.ts forbids until the attribution engine can measure one. /schools is the page the flyers' QR codes open; it exists separately from /verticals/school_ng because a bursar is buying a way to make a fee notice arrive, not "WhatsApp retention".

  • One capture path for every flyer. components/flyers/capture.ts now owns the palette, the QR and the html2canvas capture, and SocialFlyerGenerator was moved onto it. That path has broken in production twice for reasons invisible in the markup; flyer-capture.test.ts fails if any generator imports html2canvas, declares its own BRAND/CAPTURE_ID, or hides its capture wrapper its own way.

  • Vertical pricing (ADR 0020) — events, civic and payments now state a price. vertical_pricing is the single source of truth, admin-editable at /api/admin/vertical-pricing, seeded from code and cached. Events are £0.20 per registered attendee with the first 50 of every event free; civic is £1,500 per 90-day window including 10,000 messages, then £0.09 each; payments stays on the ordinary plan ladder with no cut of what a customer collects. Nigeria lands on ₦150 per attendee and ₦1,150,000 per window. Every price is asserted against its own Meta cost, so an edit that drops one below cost fails the suite.

  • Our per-message cost is recorded for the first time — UK utility ~£0.016, UK marketing ~£0.046. Event and payment reminders are utility; civic broadcasts are marketing at roughly 3x, which is why civic cannot be priced off the events rate.

  • Payments vertical, self-serve — /dashboard/payments and /api/payments/requests. Six new UTILITY templates (payment_request and payment_receipt in EN/AR/SW); until now the only customer-facing payment template in the product was university_uk_payment_en, so a plumber or a landlord had nothing to send. Settlement marks the request paid and sends a receipt, idempotently. See docs/features/payments-vertical.md.

  • Civic campaign engine — /civic had advertised GOTV broadcasts, volunteer coordination and ward reporting since launch with nothing behind it. Campaigns, licensed windows (Paystack and Stripe), CSV import with per-row rejection reporting and de-duplication, a bounded-concurrency dispatcher that re-checks the licence per message, and MARKETING-category templates in English, Hausa and Pidgin. See docs/features/civic-campaigns.md.

  • /api/business/profile — the dashboard shell had no way to ask which vertical it was rendering for.

Changed

  • Event reminders no longer draw the monthly plan allowance. They are billed per attendee, so metering them as well charged the organiser twice for the same message. billedSeparately switches off the allowance only — the opt-out gate, the pause hold and the BYOEN gate all still apply.
  • The event dispatcher can now actually deliver an event. It took 50 jobs per run, four runs an hour — ~4,800 a day against the ~8,000 a 2,000-person conference needs, so its 1-hour reminder took ten hours to drain and arrived the next morning. Now waves of 8 inside a 20s budget, with the GitHub Actions job looping until the queue reports empty.

Fixed

  • The managed retainer was priced but never sold. MANAGED_RETAINER_MINOR was keyed GBP/USD/NGN while the seed loop supplies lower-case gbp/usd/ngn, so every lookup returned undefined and no managed_pro or managed_business row was ever written. Nothing failed loudly — an absent key is not an error — so the figures sat in the source looking correct. With the keys fixed, the route's hardcoded ['events','civic','payments'] allowlist replaced by knownVerticalKeys(), and a managed_retainer branch added (it had been falling through to "ask the plan ladder"), the endpoint now quotes £399/£799, $399/$799 and ₦185,000/₦350,000 with the per-message overage. A test asserts every model the seed produces has a branch.

  • /schools and /faq were behind the login wall. The middleware's publicPaths is hand-written and had neither. It fails in the one way nobody notices: a signed-in operator testing the link sails through, while every visitor from a flyer or a search result meets a login form. /faq had been linked from the footer the whole time. public-paths.test.ts now checks every internal link the footer and nav render against the list — and that the gate still gates /dashboard and /admin.

  • Vertical landing pages dropped the affiliate's referral code. /civic?ref=ABC → "Request a Demo" → bare /signup: no code, no cookie, no commission, for as long as the civic flyers have been in the field. A landing page sets no cookie and the signup page reads ?ref= off its own URL, so the code died in between. lib/referral.ts routes a referred visitor through /api/affiliate/click, which records the click and sets the 90-day cookie.

  • Paystack annual prices ignored plan_pricing. annualLabel came from the static table unconditionally, so after the Nigerian correction a visitor saw ₦22,500/month beside ₦149,000/year — the annual figure for the superseded ₦14,900. Starter's term was advertised at a third under its price, Professional's at half. The same drift followed any admin price edit, in every Paystack market. BASE_MONTHLY.ngn and the BILLING_PLANS labels were stale too, which mattered more: that seed is what loadPricing() falls back to when the database is unreachable.

  • Every pay link was labelled university_tuition. Harmless while the university flow was the only caller; a silent misroute the moment a second one existed.

Added (earlier)

  • Payments & collections vertical at /payments, the route behind payments.tadhkirapp.com. The subdomain had been declared in FEATURE_SUBDOMAINS since the rewrite was written with no route behind it, so the middleware rewrote the host to a 404. Markets and settlement currencies are derived from MARKET_FACTS, not restated.
  • /pay/success — the page a pay-link lands on after the card is charged. StripePayLinkProvider had always set success_url to /pay/success, which did not exist: the last thing a payer saw after sending their tuition instalment was a 404. The link now carries our own reference through, so the page can show the payer something they can quote.
  • docs/features/subdomains.md — the three independent requirements a feature subdomain needs (Cloudflare record, Netlify domain alias, route + public path), how to tell from the response headers which one is broken, and the checklist for adding a new one.

Fixed

  • /payments and /pay/ are now public paths. Pay-link payers are our customers' students and tenants; they have no Tadhkir account and were being redirected to /login on the apex.
  • Config-driven affiliate commission (ADR 0012) — commission_tiers, commission_market_rates and commission_overrides are the single source of truth for every rate, editable at /admin/commission without a deploy. Only the four-tier structure stays in code. The payout webhooks, the affiliate dashboard, the affiliate landing page, the homepage and the FAQ all read the same cached loader.
  • Civic commission is payable. The 25% civic rate had been advertised since launch with no code path behind it; civic referrals were silently paid the ordinary tier rate. It is now an override applied from the referred business's vertical.
  • Public-claim single source of truth (src/lib/site-facts.ts) — market status with per-market evidence, vertical and language counts derived from the shipped registries, and benchmarks that cannot be declared without a citable source.
  • Security & compliance section on the homepage: six substantiated badges (GDPR/UK GDPR, NDPR, EU data residency, row-level tenant isolation, PCI-handled payments, one-tap opt-out) plus DPA and privacy links, in all 11 locales.
  • Regression tests — 51 copy-drift tests plus 36 commission tests covering rate resolution, the civic override and config integrity; they fail if any locale hardcodes a count or reintroduces an unsourced outcome multiplier.
  • Footer link to /civic, which was previously reachable only via affiliate flyer URLs.

Changed

  • Affiliate rates now match what is paid. The dashboard displayed 15/15/20/20 while the payout code paid 10/10/12/15 — a UK partner saw 15% and was paid 10%. Published rates are now the paid rates: 10/10/12/15, +5 points in the Nigeria and Africa markets (documented publicly for the first time).
  • The affiliate worked example is computed from the visitor's own currency and the live rate, replacing a hardcoded, arithmetically wrong "£356".
  • getTier / getCommissionRate are async and accept the referred business's vertical.
  • Homepage stats now read from the claim SSoT; the open-rate figure carries a visible footnote identifying it as a WhatsApp channel benchmark rather than a customer result.
  • Vertical count corrected to the real figure (92) and derived, across the homepage, /about, /faq, /verticals, the WhatsApp simulator and the footer.
  • Interface-language count corrected to 11 and derived; Nigerian message-template languages (Yoruba, Hausa, Igbo, Nigerian Pidgin) are now stated publicly as message languages, distinct from interface languages.
  • Affiliate worked example relabelled from the non-existent "Super tier" to Gold; the FAQ now uses the real tier names.
  • Footer contact addresses each carry a purpose label; the duplicate email list in the legal address line is removed.
  • docs/compliance-privacy-guide.md: hosting sub-processor corrected from Vercel to Netlify.

Removed

  • The unsubstantiated "3.4× average return-visit uplift" hero statistic, along with /about's conflicting 98% open rate and /civic's unsourced "3× higher reply rate" and "18+ countries active" figures.

Deferred (owner decision)