Add Dhivehi Muraka

**Font Project Git Repo URL:** https://github.com/Viennnaa/dhivehi-muraka

**Super short description of the Font Family:**

Dhivehi Muraka is an original Thaana typeface for the Dhivehi language of the Maldives. It covers the complete Unicode Thaana block — the 24 base consonants, naviyani, the 14 Arabic transliteration letters, and all 11 fili — with Latin from Inter.

Thaana is close to unserved on Google Fonts today: Noto Sans Thaana and Noto Serif Thaana, and nothing else. This is a text family drawn specifically for Dhivehi at interface sizes, where the fili have to stay legible and apart from one another.

*Muraka* means coral. The Maldives is built from it, and this typeface was built the same way, point by point.

**Requirements:**

By opening this issue, I confirm the project meets the following requirements:

- [x] The entire font project is available in a Github repository (repo) and licensed under the [OFL](https://openfontlicense.org/open-font-license-official-text/)
- [x] I confirm that by 'entire font project', no "plus" or "pro" or other larger version of the project exists as a retail font anywhere
- [x] The source files are available in the repo
- [x] I am the sole copyright author of the entire project, or all other copyright authors have licensed their work to me under the OFL, and I commit to clearly disclosing if AI tools were used in the creation of this project.
- [x] There are no "Reserved Font Names" in the OFL license information, or in the project documentation of any known upstream projects. If there are RFNs, they are not used in whole or in part in this family name, or, I want to discuss how Google can work with my use of them.
- [x] The family name is unique according to [namecheck.fontdata.com](https://namecheck.fontdata.com/)
- [x] The name of the font family expected to appear on app menus must be very clearly communicated and definitive. It should not include any copyright holder's full names or acronyms.
- [x] The font supports at least the Google Fonts 'Latin Core' glyphset from [github.com/googlefonts/glyphsets](https://github.com/googlefonts/glyphsets)
- [x] The repo has the [Google Fonts preferred upstream repo structure](https://googlefonts.github.io/gf-guide/upstream.html)
- [x] I have read, agree with, and comply with, the full [Google Fonts contributing requirements](https://googlefonts.github.io/gf-guide/index#pre-production-getting-your-fonts-ready-for-gf)
- [x] I will maintain the repository and participate in the onboarding process (addressing, solving, and responding to issues, merging pull requests, etc)

**AI tool disclosure**

Taking the fourth checkbox seriously, in detail:

Every Thaana outline in this family was drawn by hand, by me — all 50 letters, 2,113 points, placed one at a time in a browser-based editor over several days. No AI generated any letterform. Nothing was traced from, imported from, or auto-derived from another font. An existing Thaana face was displayed on screen as a proportion reference while drawing, the way a printed specimen would be, and the build verifies on every run that no glyph shares coordinates with it — currently 50 of 50 letters clear, 0 shared points.

AI assistance (Claude) was used for the engineering around the drawings, not the drawings: the build scripts that turn my exported drawings into a TTF, the OpenType feature generation (GDEF classes, mark-to-base anchors for the fili, kerning extraction), the metadata files, and the specimen page. All of that tooling is in the repo and the build is reproducible with one command.

The Latin is [Inter](https://github.com/rsms/inter) by Rasmus Andersson, merged under the OFL and credited in the font's name ID 10. No Thaana glyph comes from it.

**Notes**

- FontBakery `check-googlefonts`: 0 FAIL, 152 PASS. Remaining warnings are hand-drawing artefacts (slightly off-round coordinates, near-vertical stems) which I left rather than regularise away, plus an unregistered vendor ID.
- Fili are zero-width marks positioned with GPOS mark-to-base anchors, so they centre on narrow and wide consonants alike rather than sitting at fixed offsets.
- Interactive specimen: https://viennnaa.github.io/dhivehi-muraka/
- I would like someone to contact me privately about design assistance for this project. My contact details are on my GitHub profile.

**Image:**

Start with the linked Dhivehi Muraka repository and the Google Fonts contributing requirements, especially the preferred upstream structure and onboarding process. Review the reported FontBakery status and build reproducibility; done means the project passes Google Fonts review with any requested issues resolved.

Written by the indexing model from the issue text.