Fetching metadata from the HF Docker repository...
Jun 21 13:07 fix: Ctrl+Q works with Arabic keyboard (e.code) + copy button for translations 13:00 feat: Amiri Quran font + copy button + Ctrl+Q shortcut 12:48 test: final edge cases - 45 more tests (166 total), all passing 12:42 fix: Fatiha priority when query starts with Basmala + strip Basmala from search + restore honest tests 12:38 test: extended test suite - 64 more tests all passing (119 total) 12:35 test: comprehensive Quran test suite - 55 tests all passing 12:30 fix: restrict output to single surah (prevent cross-surah overflow) 12:21 fix: strip Basmala from verse 1 output (DB has it embedded) 12:09 fix: use full verse text instead of window words (fixes missing الر and edge words) 12:00 fix: use fullwidth brackets for ref delimiter to avoid [O Muhammad] collision 11:55 fix: Latin numbers for translations, Arabic-Indic only for uthmani (verified) 11:48 feat: Arabic-Indic numerals + range format (٣١-٣٣) in Quran output 11:30 fix: placeholder no longer shows over quran-applied text 11:23 fix: quran text excluded from analysis models + styled ref + score preserved 11:16 feat: apply includes surah ref + quran-applied span protects from analysis models 10:54 fix: use correct editor ID (editor-container) - root cause of apply failures 10:43 fix: simplify apply to direct textContent replace (guaranteed to work) 10:39 fix: apply uses window.find() + add translation apply button 10:34 fix: robust apply using TreeWalker text search instead of fragile Range 10:23 fix: apply replaces text properly + translation shows ref + bigger font 10:16 feat: add 'Apply' button to replace editor text with verified Quran text 10:11 fix: add quran.py + quran_master.db to Dockerfile COPY 10:10 fix: better quran import error logging to diagnose HF failure 10:04 feat: Quran verification & translation endpoint + modal UI (13 languages) 09:42 UI: add Quran verse translation to 14 languages feature in home + features page 09:39 chore: track .db files with git-lfs 09:38 feat: add Quran verse translation to 14 languages in features page 09:29 chore: remove large db file from git (HF 10MB limit) 09:27 UI: add Quran verse translation to 14 languages in feature cards 01:37 UI: swap nav order - pricing before editor (الأسعار then المحرر) 01:35 UI: remove pricing from nav, fix dialect colors to match theme, remove placeholder example 01:28 revert: restore backend to 1a76471, keep all UI/UX improvements 01:13 revert: restore backend/model files to cf07939 state, keep UI/UX changes only 01:08 fix: tooltip shows original→correction format instead of confusing label 01:03 fix: accept ص↔س/ض↔ظ/ذ↔ز spelling corrections (المدرصة→المدرسة), fix punctuation dup regex 01:01 fix: grammar/quran icons different, tooltip no strikethrough, punctuation no duplicate dots 00:54 UI: nav logo, bayyinah hover, quran icon, hero autocomplete shadow, clean tooltip, fix punctuation dup + hamza كان 00:23 Full UI/UX modernization: fix hero examples, pricing beta, Apply All cursor/format fix, design polish Jun 20 23:52 fix: block grammar كان→كأن + punctuation mid-word split (الدفت.ر) 23:45 feat: P1-P3 all 8 items - ta marbuta fix, UI feedback, caching, rate limiting, unit tests 23:34 fix: move Bayyinah section inside max-w-7xl container to prevent stretching 23:30 fix: replace Bayyinah icons with actual book-open-text logo SVG 23:25 fix: features page layout + update Bayyinah color to #14919b 23:19 feat: add Bayyinah RAG feature to home page + features page 23:13 fix: remove extra closing div causing gap above editor 23:08 update: replace Quran example with Yusuf:2 verse 23:05 feat: add Quran verification + Dialect conversion features (UI only, no backend) 22:52 feat: add Autocomplete feature to home page + features page 22:40 fix: block grammar model from removing/normalizing punctuation marks 22:34 revert: remove auto re-analyze after apply - causes grammar/punctuation cycle Grammar removes period, punctuation re-adds it. Auto re-analyze after apply
creates an infinite cycle. Analysis already auto-triggers when user types
(input event handler), which is the correct behavior.