--- /dev/null
+# Matangi — Source Investigation
+
+**Model**: Claude Opus 4.6
+**Date**: 2026-03-03
+**Status**: complete
+
+## METADATA.pb Source Block (current)
+
+```
+source {
+ repository_url: "https://github.com/thegraphicant/Matangi"
+ commit: "a806f5ac9093cab670d0ce25a2cf5639bcc000ca"
+ files {
+ source_file: "OFL.txt"
+ dest_file: "OFL.txt"
+ }
+ files {
+ source_file: "fonts/variable/Matangi[wght].ttf"
+ dest_file: "Matangi[wght].ttf"
+ }
+ files {
+ source_file: "article/ARTICLE.en_us.html"
+ dest_file: "ARTICLE.en_us.html"
+ }
+ files {
+ source_file: "article/matangi-01.jpg"
+ dest_file: "matangi-01.jpg"
+ }
+ files {
+ source_file: "article/matangi-02.jpg"
+ dest_file: "matangi-02.jpg"
+ }
+ files {
+ source_file: "article/matangi-03.jpg"
+ dest_file: "matangi-03.jpg"
+ }
+ files {
+ source_file: "article/matangi-04.jpg"
+ dest_file: "matangi-04.jpg"
+ }
+ files {
+ source_file: "article/matangi-05.jpg"
+ dest_file: "matangi-05.jpg"
+ }
+ files {
+ source_file: "article/matangi-06.jpg"
+ dest_file: "matangi-06.jpg"
+ }
+ files {
+ source_file: "article/matangi-07.jpg"
+ dest_file: "matangi-07.jpg"
+ }
+ branch: "main"
+ config_yaml: "sources/config.yaml"
+}
+```
+
+## Repository Analysis
+
+**Repository**: https://github.com/thegraphicant/Matangi
+**Owner**: The Graphic Ant (thegraphicant)
+**Designer**: The Graphic Ant (Devanagari + Latin sans-serif)
+**Primary Script**: Devanagari (`Deva`)
+**Date added to Google Fonts**: 2025-04-29
+
+The upstream repository was found in the fontc_crater_cache. It contained a `.glyphs` source file and a `config.yaml` for gftools-builder. The repository had a clean working tree at the time of inspection.
+
+### Repository Structure (at commit a806f5a)
+
+```
+article/
+ ARTICLE.en_us.html
+ MATANGI-01.jpg through MATANGI-07.jpg
+fonts/
+ ttf/ (static TTFs: Light through Black)
+ variable/Matangi[wght].ttf
+ webfonts/ (woff2 files)
+sources/
+ config.yaml
+ Matangi.glyphs
+OFL.txt
+README.md
+```
+
+### Commit History (upstream)
+
+The upstream repo had 18 commits total. Key merge commits:
+
+1. `81c6848` (2025-05-16) - Merge PR #1 from yanone/main: Initial setup with binaries and file extensions
+2. `c67a7d9` (2025-05-21) - Merge PR #4 from yanone/main: File renaming
+3. `a806f5a` (2025-06-24) - Merge PR #5 from simoncozens/fix-rendering: Adjusted conjunct subcategories and rebuilt fonts
+
+The commit `a806f5a` was HEAD of the `main` branch and the latest commit in the repository.
+
+## Onboarding History
+
+Matangi went through three PRs to google/fonts:
+
+### PR #9481 — Initial Onboarding (merged 2025-05-21)
+- **Title**: "Matangi: Version 3.002 added"
+- **Author**: Yanone
+- **Referenced commit**: `81c68488ff396d1264c6e9d195f106ff85e124ec` (Merge PR #1 from yanone/main)
+- This was the initial addition of the font to google/fonts.
+
+### Source Info Update (PR #9490, commit 26254ae, 2025-05-21)
+- Author: Felipe Sanches
+- Updated the commit hash from `81c6848` to `c67a7d9` (Merge PR #4 from yanone/main)
+- Added `config_yaml: "sources/config.yaml"` field
+
+### PR #9615 — Version 3.003 Update (merged 2025-06-27)
+- **Title**: "Matangi: Version 3.003 added"
+- **Author**: Emma Marichal
+- **Referenced commit**: `a806f5ac9093cab670d0ce25a2cf5639bcc000ca`
+- Multiple fixes: removed latin-ext subset, bumped version, fixed image filename casing (MATANGI -> matangi), added images back
+
+### PR #9658 — Version 3.004 Update (merged 2025-07-10)
+- **Title**: "Matangi: Version 3.004 added"
+- **Author**: Emma Marichal
+- **Referenced commit**: `a806f5ac9093cab670d0ce25a2cf5639bcc000ca` (same as PR #9615)
+- Bumped version, removed article, updated OFL.txt
+- The article directory was removed from google/fonts in this PR (commit 7c76f9b "remove useless article") but images remained via the METADATA.pb source_file mappings
+
+## Build Configuration
+
+**Config location**: `sources/config.yaml` (in upstream repo)
+**Config present at referenced commit**: Yes
+
+```yaml
+sources:
+ - Matangi.glyphs
+buildOTF: false
+buildTTF: true
+buildWebfont: true
+buildStatic: true
+buildVariable: true
+```
+
+The config.yaml existed at all three referenced commits (81c6848, c67a7d9, a806f5a) and was identical throughout. It referenced the `.glyphs` source file for building.
+
+No override config.yaml existed in the google/fonts family directory.
+
+## Findings
+
+### Commit Hash: Correct
+The commit hash `a806f5ac9093cab670d0ce25a2cf5639bcc000ca` in METADATA.pb correctly points to the latest commit in the upstream repository (HEAD of main). This is the commit referenced in both PR #9615 and PR #9658. The font binary in google/fonts (711948 bytes) matches the size of the variable font at this commit in the upstream repo.
+
+### Config YAML: Correct
+The `config_yaml: "sources/config.yaml"` field correctly points to a valid gftools-builder config in the upstream repo. The config references `Matangi.glyphs` as the source.
+
+### Repository URL: Correct
+The `repository_url` field matches the upstream repository's remote URL.
+
+### Image Filename Casing Mismatch (Minor Issue)
+The METADATA.pb `source_file` entries for article images reference lowercase filenames (e.g., `article/matangi-01.jpg`), but the actual files in the upstream repo at commit `a806f5a` are uppercase (e.g., `article/MATANGI-01.jpg`). This mismatch would cause gftools-packager to fail on case-sensitive filesystems (Linux) but would work on case-insensitive filesystems (macOS). The images in google/fonts are lowercase and have been significantly compressed (e.g., MATANGI-01.jpg: 790KB upstream vs matangi-01.jpg: 111KB in google/fonts), suggesting they were reprocessed externally rather than copied directly via the source_file mapping.
+
+### Source Block: Complete
+All required fields are present: repository_url, commit, config_yaml, branch, and files mappings.
+
+## Recommended Source Block
+
+The current source block is complete and correct. No changes are recommended. The image filename casing mismatch is a minor issue that does not affect the source metadata integrity -- the images appear to have been reprocessed externally regardless.
+
+```
+source {
+ repository_url: "https://github.com/thegraphicant/Matangi"
+ commit: "a806f5ac9093cab670d0ce25a2cf5639bcc000ca"
+ files {
+ source_file: "OFL.txt"
+ dest_file: "OFL.txt"
+ }
+ files {
+ source_file: "fonts/variable/Matangi[wght].ttf"
+ dest_file: "Matangi[wght].ttf"
+ }
+ files {
+ source_file: "article/ARTICLE.en_us.html"
+ dest_file: "ARTICLE.en_us.html"
+ }
+ files {
+ source_file: "article/matangi-01.jpg"
+ dest_file: "matangi-01.jpg"
+ }
+ files {
+ source_file: "article/matangi-02.jpg"
+ dest_file: "matangi-02.jpg"
+ }
+ files {
+ source_file: "article/matangi-03.jpg"
+ dest_file: "matangi-03.jpg"
+ }
+ files {
+ source_file: "article/matangi-04.jpg"
+ dest_file: "matangi-04.jpg"
+ }
+ files {
+ source_file: "article/matangi-05.jpg"
+ dest_file: "matangi-05.jpg"
+ }
+ files {
+ source_file: "article/matangi-06.jpg"
+ dest_file: "matangi-06.jpg"
+ }
+ files {
+ source_file: "article/matangi-07.jpg"
+ dest_file: "matangi-07.jpg"
+ }
+ branch: "main"
+ config_yaml: "sources/config.yaml"
+}
+```
--- /dev/null
+# Mate — Source Investigation
+
+**Model**: Claude Opus 4.6
+**Date**: 2026-03-03
+**Status**: complete
+
+## METADATA.pb Source Block (current)
+
+The source block in `ofl/mate/METADATA.pb` is already fully populated:
+
+```
+source {
+ repository_url: "https://github.com/etunni/mate"
+ commit: "2ea8febc952610379af663b1651411493d34beea"
+ config_yaml: "sources/mate.yaml"
+ files {
+ source_file: "OFL.txt"
+ dest_file: "OFL.txt"
+ }
+ files {
+ source_file: "fonts/mate/ttf/Mate-Regular.ttf"
+ dest_file: "Mate-Regular.ttf"
+ }
+ files {
+ source_file: "fonts/mate/ttf/Mate-Italic.ttf"
+ dest_file: "Mate-Italic.ttf"
+ }
+ branch: "master"
+}
+```
+
+## Repository Analysis
+
+**Repository**: https://github.com/etunni/mate
+**Owner**: Eduardo Tunni (etunni)
+**Branch**: master (only branch)
+**Accessible**: Yes (HTTP 200)
+
+The upstream repository was set up by Emma Marichal (emmamarichal) via PR #1 to the owner's repo, merged on 2023-02-24 by Eduardo Rodriguez Tunni. The repository has exactly one commit — the merge commit `2ea8febc952610379af663b1651411493d34beea`.
+
+### Repository Structure
+
+```
+AUTHOR.txt
+CONTRIBUTORS.txt
+OFL.txt
+README.md
+requirements.txt
+documentation/
+ image1.png, image2.png, image3.png
+fonts/
+ mate/
+ otf/ Mate-Regular.otf, Mate-Italic.otf
+ ttf/ Mate-Regular.ttf, Mate-Italic.ttf
+ webfonts/ Mate-Regular.woff2, Mate-Italic.woff2
+ matesc/
+ otf/ MateSC-Regular.otf
+ ttf/ MateSC-Regular.ttf
+ webfonts/ MateSC-Regular.woff2
+sources/
+ Mate.glyphs
+ Mate-Italic.glyphs
+ MateSC.glyphs
+ mate.yaml
+ matesc.yaml
+```
+
+The repo contains sources and pre-built binaries for both Mate and Mate SC font families. The sources are `.glyphs` files (GlyphsApp format).
+
+### Cached Repo Status
+
+The cached clone at `fontc_crater_cache/etunni/mate/` was clean (no local modifications, up to date with origin).
+
+## Onboarding History
+
+### Original Addition
+
+The Mate font was originally added to Google Fonts in the initial commit (`90abd17b4`, 2015-03-07).
+
+### Update via gftools-packager
+
+The font was updated via PR #5930 on google/fonts:
+- **PR title**: "Mate: Version 1.003; ttfautohint (v1.8.4.7-5d5b);gftools[0.9.24] added"
+- **Author**: Emma Marichal (emmamarichal)
+- **Merged by**: Marc Foley (m4rc1e) on 2023-03-01
+- **Commit**: `65c9b9722` — "[gftools-packager] Mate: Version 1.003; ttfautohint (v1.8.4.7-5d5b);gftools[0.9.24] added"
+- The commit message explicitly states: "taken from the upstream repo https://github.com/etunni/mate at commit 2ea8febc952610379af663b1651411493d34beea"
+
+### Source Block History
+
+1. The initial source block (repository_url, commit, files, branch) was added by gftools-packager in commit `65c9b9722` (2023-02-24).
+2. The `config_yaml: "sources/mate.yaml"` field was added and `branch` was removed in commit `53995c52a` (2025-03-25) — "[METADATA.pb] Populate font sources related fields for a few font families" by Felipe Sanches.
+3. The `branch: "master"` field was re-added in commit `f19b6da7d` (2025-03-26) — "revert removal of branch values on METADATA.pb files" by Felipe Sanches, as gftools-packager may still rely on that field.
+
+## Build Configuration
+
+The upstream repo contains a config.yaml at `sources/mate.yaml`:
+
+```yaml
+sources:
+ - Mate.glyphs
+ - Mate-Italic.glyphs
+outputDir: "../fonts/mate"
+```
+
+This is a valid gftools-builder configuration. The `config_yaml` field in METADATA.pb correctly points to `sources/mate.yaml`.
+
+Note: The repo also contains `sources/matesc.yaml` for the Mate SC family (a separate family in google/fonts).
+
+## Findings
+
+### Binary File Verification
+
+Both TTF files in google/fonts are byte-identical to the files in the upstream repo at the referenced commit:
+- `Mate-Regular.ttf`: MD5 `7b63a0807aee78be5f88e75974251dc5` — **match**
+- `Mate-Italic.ttf`: MD5 `7169eb8afa4d442f410baded248b1b1c` — **match**
+
+### Commit Hash Verification
+
+The commit hash `2ea8febc952610379af663b1651411493d34beea` was verified:
+- It is the only commit in the upstream repository (a merge commit from 2023-02-24)
+- It is explicitly referenced in the gftools-packager commit message and PR #5930 body
+- The binary files at this commit match those in google/fonts
+- **Confidence: HIGH** — the commit hash is correct
+
+### Summary
+
+The source block is complete and accurate. All fields are populated correctly:
+- Repository URL is valid and accessible
+- Commit hash is verified (only commit in the repo, binary match confirmed)
+- Config YAML path points to a valid gftools-builder configuration
+- File mappings are correct
+- Branch is correctly set to "master"
+
+No corrections are needed.
+
+## Recommended Source Block
+
+The current source block is already correct. No changes recommended:
+
+```
+source {
+ repository_url: "https://github.com/etunni/mate"
+ commit: "2ea8febc952610379af663b1651411493d34beea"
+ config_yaml: "sources/mate.yaml"
+ files {
+ source_file: "OFL.txt"
+ dest_file: "OFL.txt"
+ }
+ files {
+ source_file: "fonts/mate/ttf/Mate-Regular.ttf"
+ dest_file: "Mate-Regular.ttf"
+ }
+ files {
+ source_file: "fonts/mate/ttf/Mate-Italic.ttf"
+ dest_file: "Mate-Italic.ttf"
+ }
+ branch: "master"
+}
+```
--- /dev/null
+# Matemasie — Source Investigation
+
+**Model**: Claude Opus 4.6
+**Date**: 2026-03-03
+**Status**: complete
+
+## METADATA.pb Source Block (current)
+
+The source block was present and fully populated:
+
+```
+source {
+ repository_url: "https://github.com/YADAMSS/Matemasie-Font"
+ commit: "a6dbde5f9eb448066e8c751ee4c5b4146a7fbc99"
+ files {
+ source_file: "OFL.txt"
+ dest_file: "OFL.txt"
+ }
+ files {
+ source_file: "fonts/ttf/Matemasie-Regular.ttf"
+ dest_file: "Matemasie-Regular.ttf"
+ }
+ files {
+ source_file: "ARTICLE.en_us.html"
+ dest_file: "article/ARTICLE.en_us.html"
+ }
+ files {
+ source_file: "documentation/social-media-posts/1440px-x-765px/1/1.png"
+ dest_file: "article/1.png"
+ }
+ files {
+ source_file: "documentation/social-media-posts/1440px-x-765px/1/2.png"
+ dest_file: "article/2.png"
+ }
+ files {
+ source_file: "documentation/social-media-posts/1440px-x-765px/1/3.gif"
+ dest_file: "article/3.gif"
+ }
+ files {
+ source_file: "documentation/social-media-posts/1440px-x-765px/1/4.png"
+ dest_file: "article/4.png"
+ }
+ branch: "main"
+ config_yaml: "sources/config.yaml"
+}
+```
+
+## Repository Analysis
+
+**Repository**: https://github.com/YADAMSS/Matemasie-Font
+**Owner**: YADAMSS (Adam Yeo)
+**Branch**: main
+**Cached**: Yes, at `YADAMSS/Matemasie-Font` in the upstream repos cache.
+
+The upstream repository was built from the googlefonts project template. It contained:
+- **Source files**: `sources/Matemasie.glyphspackage` (Glyphs 3 package format)
+- **Config**: `sources/config.yaml` with gftools-builder configuration
+- **Font binary**: `fonts/ttf/Matemasie-Regular.ttf` (pre-built)
+- **Build system**: Makefile and GitHub Actions workflow (`build.yaml`)
+- **Documentation**: Article HTML, social media assets, proofs
+
+The repository had only one branch (`main`) and the entire visible history consisted of a single commit (`a6dbde5`), which was a merge of PR #34 ("Restore Actions with change to build.yaml") dated 2024-10-09. This indicated the repository was force-pushed or rebased at some point, squashing all prior history.
+
+### Force-Push Evidence
+
+Multiple commit hashes referenced in google/fonts history no longer existed in the upstream repo:
+- `f8b28b0ecb71e4556e18b2f4af23ca151243cac0` (referenced in PR #7875 body)
+- `05f20fba79c6e780b125220555909646f29b999c` (referenced in onboarding commit `f4e074ab6` message)
+- `982fb1ec023f63c0da05a11a2bec15efd1470484` (referenced in PR #8208 body)
+- `a53371edff5c32131e93492ccb7618f4c567fbe0` (referenced in update commit `7e509860f` message)
+
+All of these hashes were lost when the repo was apparently reset/force-pushed. The only surviving commit was the final `a6dbde5` merge commit.
+
+### config.yaml
+
+The config file at `sources/config.yaml` contained:
+
+```yaml
+sources:
+ - Matemasie.glyphspackage
+familyName: Matemasie
+autohintOTF: False
+```
+
+This was a valid gftools-builder configuration referencing the `.glyphspackage` source.
+
+### Binary Verification
+
+The font binary in google/fonts (`ofl/matemasie/Matemasie-Regular.ttf`) was verified to be identical to the one in the upstream repo (`fonts/ttf/Matemasie-Regular.ttf`):
+- MD5: `d2e20b8efc02a584dd916c92a1f7cfaa`
+- Size: 143,128 bytes
+
+This confirmed that the current HEAD commit (`a6dbde5`) contained the same font file that was onboarded.
+
+## Onboarding History
+
+### Initial Onboarding (PR #7875, merged 2024-07-17)
+
+- **Title**: "Matemasie: Version 1.001; ttfautohint (v1.8.4.7-5d5b) added"
+- **Author**: Nathan Willis (@n8willis)
+- **Commit in google/fonts**: `f4e074ab6` (2024-07-10)
+- **Upstream commit cited in body**: `f8b28b0ecb71e4556e18b2f4af23ca151243cac0`
+- **Upstream commit cited in commit message**: `05f20fba79c6e780b125220555909646f29b999c`
+- **Files added**: METADATA.pb, Matemasie-Regular.ttf, OFL.txt, article/ARTICLE.en_us.html
+
+The discrepancy between the PR body and the commit message hashes was notable. This was a known gftools-packager behavior where the commit message could reference a different hash than the PR body if the packager ran at a different time or the upstream was updated between runs.
+
+### Article Update (PR #8208, merged 2024-10-01)
+
+- **Title**: "Matemasie: Update article"
+- **Author**: Nathan Willis (@n8willis)
+- **Commit in google/fonts**: `7e509860f` (2024-10-01)
+- **Upstream commit cited in body**: `982fb1ec023f63c0da05a11a2bec15efd1470484`
+- **Upstream commit cited in commit message**: `a53371edff5c32131e93492ccb7618f4c567fbe0`
+- **Files changed**: METADATA.pb (source block expanded), article images and HTML added
+
+This update added social media images, expanded the ARTICLE.en_us.html, and updated the source block in METADATA.pb with file mappings. The font binary was not modified in this commit.
+
+### Additional Related PRs
+
+- **PR #7989** (merged 2024-08-01): "Matemasie description" by Viviana Monsalve (@vv-monsalve)
+- **PR #8035** (merged 2024-08-16): "Add designer: Adam Yeo" by Viviana Monsalve
+- **PR #8229** (merged 2024-10-01): "Matemasie image size fix" by Viviana Monsalve
+- **PR #8253** (merged 2024-10-03): "Matemasie is failing to push" by Rod Sheeter (@rsheeter)
+
+### Source Block Enrichment (Batch 2/4, commit 4ad8ac6)
+
+The commit `4ad8ac6` (2025-03-31) by Felipe Sanches updated the source block:
+- Changed commit hash from `a53371edff5c32131e93492ccb7618f4c567fbe0` to `a6dbde5f9eb448066e8c751ee4c5b4146a7fbc99`
+- Added `config_yaml: "sources/config.yaml"`
+
+The new hash `a6dbde5` was the only commit remaining in the repository after the force-push, and it was sourced from fontc_crater's targets list.
+
+## Build Configuration
+
+- **Config file**: `sources/config.yaml` in the upstream repo
+- **Source format**: Glyphs 3 package (`.glyphspackage`)
+- **Build tool**: gftools-builder (via Makefile)
+- **Override config in google/fonts**: None (not needed; config existed in upstream)
+- **METADATA.pb config_yaml field**: `sources/config.yaml` (correct)
+
+## Findings
+
+1. **Source block is complete**: The METADATA.pb contained all necessary fields — repository_url, commit, branch, config_yaml, and file mappings.
+
+2. **Commit hash is the best available**: The referenced commit `a6dbde5` was the only commit available in the upstream repository. Since all prior history was lost due to a force-push, this was the only valid reference. The binary font file at this commit matched the one in google/fonts, confirming it contained the correct sources.
+
+3. **Repository was force-pushed**: The upstream repository lost its entire commit history at some point (likely around the Oct 9, 2024 merge of PR #34). All previously referenced commit hashes (from PRs #7875 and #8208) no longer existed. This was a known risk with designer-maintained repositories.
+
+4. **config.yaml is valid**: The upstream `sources/config.yaml` correctly referenced the `Matemasie.glyphspackage` source file.
+
+5. **No corrections needed**: The current source block accurately represented the state of the upstream repository.
+
+## Recommended Source Block
+
+The current source block was correct and complete. No changes were needed:
+
+```
+source {
+ repository_url: "https://github.com/YADAMSS/Matemasie-Font"
+ commit: "a6dbde5f9eb448066e8c751ee4c5b4146a7fbc99"
+ files {
+ source_file: "OFL.txt"
+ dest_file: "OFL.txt"
+ }
+ files {
+ source_file: "fonts/ttf/Matemasie-Regular.ttf"
+ dest_file: "Matemasie-Regular.ttf"
+ }
+ files {
+ source_file: "ARTICLE.en_us.html"
+ dest_file: "article/ARTICLE.en_us.html"
+ }
+ files {
+ source_file: "documentation/social-media-posts/1440px-x-765px/1/1.png"
+ dest_file: "article/1.png"
+ }
+ files {
+ source_file: "documentation/social-media-posts/1440px-x-765px/1/2.png"
+ dest_file: "article/2.png"
+ }
+ files {
+ source_file: "documentation/social-media-posts/1440px-x-765px/1/3.gif"
+ dest_file: "article/3.gif"
+ }
+ files {
+ source_file: "documentation/social-media-posts/1440px-x-765px/1/4.png"
+ dest_file: "article/4.png"
+ }
+ branch: "main"
+ config_yaml: "sources/config.yaml"
+}
+```
--- /dev/null
+# Mate SC — Source Investigation
+
+**Model**: Claude Opus 4.6
+**Date**: 2026-03-03
+**Status**: complete
+
+## METADATA.pb Source Block (current)
+
+```
+source {
+ repository_url: "https://github.com/etunni/mate"
+ commit: "2ea8febc952610379af663b1651411493d34beea"
+ config_yaml: "sources/matesc.yaml"
+ files {
+ source_file: "OFL.txt"
+ dest_file: "OFL.txt"
+ }
+ files {
+ source_file: "fonts/matesc/ttf/MateSC-Regular.ttf"
+ dest_file: "MateSC-Regular.ttf"
+ }
+ branch: "master"
+}
+```
+
+The source block was already fully populated. The `repository_url` and `commit` fields were added by the gftools-packager commit (dbbe08276, 2023-02-24). The `config_yaml` field was added later by commit 53995c52a (2025-03-25). The `branch` field was removed in that same commit but subsequently restored by commit f19b6da7d.
+
+## Repository Analysis
+
+- **Repository**: https://github.com/etunni/mate
+- **Owner**: Eduardo Rodriguez Tunni (etunni)
+- **Default branch**: master
+- **Total commits**: 1 (the entire repo consists of a single merge commit)
+- **Only commit**: `2ea8febc952610379af663b1651411493d34beea` (2023-02-24) — "Merge pull request #1 from emmamarichal/master"
+
+The repository was set up by merging PR #1, submitted by Emma Marichal, which added the complete Mate family sources (Mate, Mate Italic, and Mate SC) along with compiled font files, config files, and documentation.
+
+### Source files
+
+- `sources/MateSC.glyphs` — Glyphs source for Mate SC (familyName: "Mate SC", dated 2023-02-22)
+- `sources/Mate.glyphs` — Glyphs source for Mate Regular
+- `sources/Mate-Italic.glyphs` — Glyphs source for Mate Italic
+- `sources/matesc.yaml` — gftools-builder config for Mate SC
+- `sources/mate.yaml` — gftools-builder config for Mate (Regular + Italic)
+
+### Compiled fonts in upstream
+
+- `fonts/matesc/ttf/MateSC-Regular.ttf` — Pre-compiled TTF
+- `fonts/matesc/otf/MateSC-Regular.otf`
+- `fonts/matesc/webfonts/MateSC-Regular.woff2`
+
+## Onboarding History
+
+1. **Initial onboarding** (2015-03-07): Mate SC was first added to Google Fonts in the initial commit (90abd17b4). No upstream repo existed at that time.
+
+2. **Upstream repo creation and update** (2023-02-24): Emma Marichal created the upstream repository structure and submitted PR #1 to etunni/mate with cleaned source files, build configs, and compiled fonts. Eduardo Tunni merged it on the same day. Emma's PR comment: "Here you can find Mate and Mate SC upgrade. As usual, I cleaned the files, added missing kerning groups etc."
+
+3. **google/fonts PR #5931** (2023-02-24, merged 2023-03-01): Submitted by Emma Marichal. Used gftools-packager to update Mate SC in google/fonts from upstream repo at commit `2ea8febc`. The PR contained two commits:
+ - `dbbe08276`: "[gftools-packager] Mate SC: Version 1.003" — font binary update
+ - `fd93ee8b5`: "Mate SC: description updated"
+
+4. **Binary verification**: The `MateSC-Regular.ttf` in google/fonts has an identical SHA-256 hash (`7aa5db42e899619bf2ecac412fc5668a3ea5d5cdc0af05cf95656c10fdfb50a0`) to the file at `fonts/matesc/ttf/MateSC-Regular.ttf` in the upstream repo at the referenced commit. This confirms the commit hash is correct.
+
+## Build Configuration
+
+The upstream repo contains `sources/matesc.yaml` at the referenced commit:
+
+```yaml
+sources:
+ - MateSC.glyphs
+outputDir: "../fonts/matesc"
+```
+
+This is a valid gftools-builder configuration. The source path (`MateSC.glyphs`) is relative to the config file's location in the `sources/` directory. The output directory points to `fonts/matesc/` relative to the repo root.
+
+The `config_yaml` field in METADATA.pb correctly points to `sources/matesc.yaml`.
+
+## Findings
+
+- **Source block is complete and correct.** All fields (repository_url, commit, config_yaml, files, branch) are populated with accurate values.
+- **Commit hash verified.** The upstream repo has only one commit, which is exactly the one referenced in METADATA.pb. The binary font file in google/fonts matches the one in the upstream repo byte-for-byte.
+- **Config file verified.** The `sources/matesc.yaml` file exists at the referenced commit and contains a valid gftools-builder configuration pointing to the `MateSC.glyphs` source file.
+- **No corrections needed.** The existing metadata is accurate and complete.
+
+Note: Mate SC shares the upstream repository (etunni/mate) with the "Mate" family, which has its own separate config at `sources/mate.yaml`.
+
+## Recommended Source Block
+
+The current source block is correct. No changes are needed.
+
+```
+source {
+ repository_url: "https://github.com/etunni/mate"
+ commit: "2ea8febc952610379af663b1651411493d34beea"
+ config_yaml: "sources/matesc.yaml"
+ files {
+ source_file: "OFL.txt"
+ dest_file: "OFL.txt"
+ }
+ files {
+ source_file: "fonts/matesc/ttf/MateSC-Regular.ttf"
+ dest_file: "MateSC-Regular.ttf"
+ }
+ branch: "master"
+}
+```
--- /dev/null
+# Maven Pro — Source Investigation
+
+**Model**: Claude Opus 4.6
+**Date**: 2026-03-03
+**Status**: complete
+
+## METADATA.pb Source Block (current)
+
+The source block in `ofl/mavenpro/METADATA.pb` currently reads:
+
+```
+source {
+ repository_url: "https://www.github.com/m4rc1e/mavenproFont"
+ commit: "a694ee80d067e6f8cad700930e78ce395d4949e6"
+ config_yaml: "sources/config.yaml"
+ files {
+ source_file: "fonts/variable/MavenPro[wght].ttf"
+ dest_file: "MavenPro[wght].ttf"
+ }
+ files {
+ source_file: "OFL.txt"
+ dest_file: "OFL.txt"
+ }
+ branch: "main"
+}
+```
+
+## Repository Analysis
+
+### Repository History
+
+Maven Pro has a complex upstream repository history:
+
+1. **`googlefonts/mavenproFont`** (https://github.com/googlefonts/mavenproFont) — The original upstream repo, created 2017-03-13 under the googlefonts organization. Last pushed 2023-06-19. This was the repository initially referenced in METADATA.pb when the source block was first added in the "Update upstreams" commit (c891a9b8, 2024-03-04).
+
+2. **`m4rc1e/mavenproFont`** (https://github.com/m4rc1e/mavenproFont) — A fork of the googlefonts repo, created 2018-04-04 by Marc Foley. Marc used this fork to prepare the Version 2.103 update in February 2025. The METADATA.pb now points to this fork.
+
+### Current Upstream Repo (m4rc1e/mavenproFont)
+
+- **Default branch**: main
+- **Total commits (on main)**: ~30 (history stretching back to the original repo)
+- **Key recent commits** (Feb 6-7, 2025, by Marc Foley):
+ - `a694ee8` — "regenned fonts" (2025-02-07, the referenced commit)
+ - `86a23da` — "fix Lslash" (2025-02-07)
+ - `144085d` — "regen fonts" (2025-02-07)
+ - `a43a9e5` — "update copyright string, sigh" (2025-02-07)
+ - `fee7a8a` — "bump requirements" (2025-02-07)
+ - `0c55e03` — "upgrade upload-artifact" (2025-02-06)
+ - `e872218` — "bump version" (2025-02-06)
+ - `9a6093e` — "update license" (2025-02-06)
+ - Multiple other prep commits from the same two days
+
+### Source Files
+
+Located at `sources/` in the repo:
+- `sources/MavenPro.glyphs` — Glyphs source file (534,604 bytes)
+- `sources/config.yaml` — gftools-builder configuration
+
+### Build Configuration
+
+The `sources/config.yaml` contains:
+
+```yaml
+sources:
+ - MavenPro.glyphs
+axisOrder:
+ - wght
+familyName: Maven Pro
+stat:
+ MavenPro[wght].ttf:
+ - name: Weight
+ tag: wght
+ values:
+ - name: Regular
+ value: 400
+ linkedValue: 700
+ flags: 2
+ - name: Medium
+ value: 500
+ - name: SemiBold
+ value: 600
+ - name: Bold
+ value: 700
+ - name: ExtraBold
+ value: 800
+ - name: Black
+ value: 900
+```
+
+### Output Verification
+
+The variable font `fonts/variable/MavenPro[wght].ttf` from the upstream repo at commit `a694ee8` has SHA-256 hash `bc994ed80baaec6ea61d7cb631f49466a1deb29d4363138021a96931f9faae9a`, which is **identical** to the file in `ofl/mavenpro/MavenPro[wght].ttf` in google/fonts. This confirms the binary was taken directly from the upstream repo's pre-built output.
+
+## Onboarding History
+
+### Timeline
+
+1. **Initial addition** (2011-05-25): Maven Pro was added to Google Fonts (`date_added` in METADATA.pb).
+
+2. **Multiple updates** over the years: v2.000 (2016), v2.002 (2017), v2.003 VF (2018), v2.100 (2019), v2.101 STAT fix (2021), v2.102 hotfix (2022).
+
+3. **Source block first added** (2024-03-04, commit c891a9b8): The "Update upstreams" commit added a bare source block pointing to `https://github.com/googlefonts/mavenproFont` (no commit hash, no config_yaml, no files).
+
+4. **Version 2.103 update** (2025-02-07, commit ec6798de, by Marc Foley): This commit updated the font binary and enriched the source block with the commit hash, files mapping, and branch. It changed the repository URL from `googlefonts/mavenproFont` to `m4rc1e/mavenproFont`. The commit message explicitly states: "Taken from the upstream repo https://www.github.com/m4rc1e/mavenproFont at commit a694ee80d067e6f8cad700930e78ce395d4949e6."
+
+5. **config_yaml field added** (2025-04-03, commit be712aef, PR #9051, by Felipe Sanches): Added the `config_yaml: "sources/config.yaml"` field to complete the source block.
+
+### Relevant PRs
+
+- **PR #9051** (merged 2025-02-07): "Maven Pro: Version 2.103 added" — Marc Foley's update that refreshed the font and set up the source block pointing to his fork.
+
+## Build Configuration
+
+- **config.yaml exists**: Yes, at `sources/config.yaml` in the upstream repo
+- **gftools-builder compatible**: Yes, uses standard gftools-builder format with Glyphs source
+- **Override needed**: No, the upstream repo has a proper config.yaml
+- **METADATA.pb config_yaml field**: Correctly set to `sources/config.yaml`
+
+## Findings
+
+### URL Issue (Minor)
+
+The `repository_url` in METADATA.pb uses `https://www.github.com/m4rc1e/mavenproFont` (with `www.` prefix). This returns HTTP 301 redirecting to `https://github.com/m4rc1e/mavenproFont`. While functional, the canonical form without `www.` would be more standard. This was set by Marc Foley in the Version 2.103 commit and is the URL he used consistently in both the METADATA.pb and commit message.
+
+### Fork vs. Original Repo
+
+The METADATA.pb points to Marc Foley's personal fork (`m4rc1e/mavenproFont`) rather than the organization repo (`googlefonts/mavenproFont`). This is intentional: Marc prepared the v2.103 update in his fork, and the specific commit `a694ee8` exists only in his fork (the googlefonts repo was last pushed in 2023). The fork relationship is confirmed via GitHub API.
+
+### Source Block Completeness
+
+The current source block is **complete**:
+- `repository_url`: Set (points to m4rc1e fork)
+- `commit`: Set and verified (`a694ee8`)
+- `config_yaml`: Set and verified (`sources/config.yaml`)
+- `files`: Correctly mapped (variable font + OFL.txt)
+- `branch`: Set to `main`
+- Binary file hash match: Confirmed
+
+### Commit Hash Verification
+
+The commit `a694ee80d067e6f8cad700930e78ce395d4949e6` was made on 2025-02-07 at 10:44:35 UTC by Marc Foley, with message "regenned fonts." The google/fonts commit adding Version 2.103 was made 45 seconds later at 10:45:20 UTC. The binary files are byte-identical. The commit is the latest (HEAD) on the main branch of `m4rc1e/mavenproFont`. This is definitively the correct commit.
+
+## Recommended Source Block
+
+The current source block is already complete and correct. The only minor improvement would be normalizing the URL to remove the `www.` prefix:
+
+```
+source {
+ repository_url: "https://github.com/m4rc1e/mavenproFont"
+ commit: "a694ee80d067e6f8cad700930e78ce395d4949e6"
+ config_yaml: "sources/config.yaml"
+ files {
+ source_file: "fonts/variable/MavenPro[wght].ttf"
+ dest_file: "MavenPro[wght].ttf"
+ }
+ files {
+ source_file: "OFL.txt"
+ dest_file: "OFL.txt"
+ }
+ branch: "main"
+}
+```
+
+**Note**: The only change from current is `www.github.com` to `github.com`. This is a cosmetic normalization; the `www.` URL works via redirect.
--- /dev/null
+# Maven Pro VF Beta — Source Investigation
+
+**Model**: Claude Opus 4.6
+**Date**: 2026-03-03
+**Status**: incomplete (early access, no METADATA.pb, deprecated by main Maven Pro variable font)
+
+## METADATA.pb Source Block (current)
+
+No METADATA.pb exists for this family. The directory `ofl/mavenprovfbeta/` contains only:
+- `DESCRIPTION.en_us.html`
+- `EARLY_ACCESS.category` (value: "Sans Serif")
+- `MavenProVFBeta.ttf`
+- `OFL.txt`
+
+This is an early access family that was never graduated to the main catalog with a full METADATA.pb.
+
+## Repository Analysis
+
+### Upstream Source Repository
+
+The source for Maven Pro VF Beta was `m4rc1e/Maven-Pro` (https://github.com/m4rc1e/Maven-Pro), which contained the `.glyphs` source at `sources/MavenPro.glyphs`. This repository was the original working repository for the Maven Pro redesign by Joe Prince, maintained by Marc Foley.
+
+The variable font binary was **not** built directly from this repo. Instead, Marc Foley used a separate build tool repository, `m4rc1e/gfvf` (https://github.com/m4rc1e/gfvf), described as "Variable Fonts for GF" — a rough build chain for generating beta variable fonts for Google Fonts Early Access. The `gfvf` script (`generate_variable_fonts.py`) traversed source repositories, found `.glyphs` files with multiple masters, renamed the family to append "VF Beta", and generated variable fonts using `fontmake`.
+
+### Repository Status
+
+- **m4rc1e/Maven-Pro**: Active, not archived. Last commit: `51ae64ef` (July 4, 2017). Contains `sources/MavenPro.glyphs` but no `config.yaml`. Only has static font output in `fonts/` directory (no variable font output).
+- **m4rc1e/gfvf**: Active, not archived. Created October 20, 2017. This was a build automation tool, not a font source repository.
+- **m4rc1e/mavenproFont**: Created April 4, 2018 — this is the **successor** repository used for the graduated Maven Pro variable font. It has `sources/config.yaml` and is referenced in the main Maven Pro METADATA.pb.
+
+### Relationship Between Repositories
+
+1. `m4rc1e/Maven-Pro` — Original source repo used for the VF Beta (2016-2017)
+2. `m4rc1e/gfvf` — Build tooling repo used to batch-generate VF betas (2017)
+3. `m4rc1e/mavenproFont` — Successor repo for the properly released Maven Pro variable font (2018+)
+
+## Onboarding History
+
+### Initial Onboarding (March 29, 2017)
+
+- **Commit**: `50153d0f379c50b09b469288234a8bde8778a15f`
+- **Author**: Marc Foley (m.foley.88@gmail.com)
+- **PR**: #724 — "mavenprovfbeta: added to early access."
+- **Merged**: March 28, 2017
+- **Context**: This was one of the first variable font betas added to Google Fonts Early Access. In the PR body, Marc Foley explained he was using the Amstelvar branch as a reference and planned to add more VF beta families once the process was validated.
+
+The source commit in `m4rc1e/Maven-Pro` was most likely `8fbb17d8` (March 13, 2017 — "v2.002 update: fixed Turkish i"), the latest commit at the time of onboarding.
+
+### Update (October 23, 2017)
+
+- **Commit**: `3507365d317354387395cbfdbebe757a86130c5d`
+- **Author**: Marc Foley
+- **Message**: "Variable beta font update. Uploading variable fonts which can be generated from M Foley's machine. Built using https://github.com/m4rc1e/gfvf"
+- **Context**: This was a batch update to multiple VF beta families (Archivo, Asap, Cabin, Faustina, Maven Pro, Podkova). The font binary was regenerated using the gfvf build tool.
+
+The source commit in `m4rc1e/Maven-Pro` for this update was most likely `51ae64ef` (July 4, 2017 — "Merge pull request #3 from m4rc1e/mm-collisions"), which was the latest commit at the time of the October 2017 update.
+
+## Build Configuration
+
+- **No config.yaml** exists in the `m4rc1e/Maven-Pro` repository.
+- The VF Beta was built using the `m4rc1e/gfvf` build tool, which used `fontmake` directly via command line (`fontmake -g <source> -o variable`), not gftools-builder.
+- The source file was `sources/MavenPro.glyphs` in the Maven-Pro repository.
+- The gfvf script renamed the family from "Maven Pro" to "Maven Pro VF Beta" before building.
+
+## Findings
+
+1. **Deprecated family**: Maven Pro VF Beta was an experimental early access variable font from 2017. The main Maven Pro family (`ofl/mavenpro/`) has since been properly released as a variable font with a full METADATA.pb and source block pointing to `m4rc1e/mavenproFont`. The VF Beta is effectively superseded and obsolete.
+
+2. **No METADATA.pb**: This early access family never had a METADATA.pb file, only an `EARLY_ACCESS.category` file.
+
+3. **Unconventional build process**: The VF Beta was generated using a custom Python script (`m4rc1e/gfvf`) that batch-processed `.glyphs` sources with `fontmake`, not using the standard gftools-builder pipeline. This means no `config.yaml` was ever applicable for this family.
+
+4. **Source repository mismatch**: The actual font design source was in `m4rc1e/Maven-Pro`, but the build tooling was in `m4rc1e/gfvf`. Neither repository was set up for standard gftools-builder workflows.
+
+5. **Two relevant source commits**:
+ - First onboarding: `8fbb17d8` from `m4rc1e/Maven-Pro` (March 13, 2017)
+ - Final update: `51ae64ef` from `m4rc1e/Maven-Pro` (July 4, 2017)
+
+6. **OFL copyright**: References `http://www.vissol.co.uk/mavenpro/` (Joe Prince's website), not a GitHub repository.
+
+## Recommended Source Block
+
+Given that this is a deprecated early access family with no METADATA.pb and no standard build configuration, adding a source block is of very low priority. If one were to be added, it would look like:
+
+```
+source {
+ repository_url: "https://github.com/m4rc1e/Maven-Pro"
+ commit: "51ae64ef0eb6ef250f10f71b28b0d4ad2c24b8c7"
+}
+```
+
+However, the recommended action is to **not prioritize this family** for source metadata enrichment because:
+- It is an early access VF beta that has been superseded by the graduated Maven Pro variable font
+- It has no METADATA.pb and no standard build pipeline
+- The main Maven Pro family (`ofl/mavenpro/`) already has complete source metadata pointing to the successor repository `m4rc1e/mavenproFont`
+- Creating a METADATA.pb for this family would require broader decisions about the status of early access VF beta families in general
--- /dev/null
+# McLaren — Source Investigation
+
+**Model**: Claude Opus 4.6
+**Date**: 2026-03-03
+**Status**: incomplete (VFB-only sources, no gftools-builder compatibility)
+
+## METADATA.pb Source Block (current)
+
+No source block exists in METADATA.pb. The current file only contains basic metadata:
+
+```
+name: "McLaren"
+designer: "Astigmatic"
+license: "OFL"
+category: "DISPLAY"
+date_added: "2012-08-13"
+fonts {
+ name: "McLaren"
+ style: "normal"
+ weight: 400
+ filename: "McLaren-Regular.ttf"
+ post_script_name: "McLaren-Regular"
+ full_name: "McLaren"
+ copyright: "Copyright (c) 2012 by Brian J. Bonislawsky DBA Astigmatic (AOETI) (astigma@astigmatic.com), with Reserved Font Name \"McLaren\""
+}
+subsets: "menu"
+subsets: "latin"
+subsets: "latin-ext"
+stroke: "SANS_SERIF"
+classifications: "DISPLAY"
+```
+
+## Repository Analysis
+
+**Repository**: [librefonts/mclaren](https://github.com/librefonts/mclaren)
+**Default branch**: master
+**Created**: 2014-07-16
+**Last pushed**: 2014-10-17
+**Archived**: No
+
+The repository contains a single commit:
+- `7031b7b` (2014-10-17): "update .travis.yml"
+
+### Repository structure:
+
+```
+├── DESCRIPTION.en_us.html
+├── FONTLOG.txt
+├── METADATA.json
+├── OFL.txt
+├── .travis.yml
+├── McLaren-Regular.ttf.*.ttx (TTX table dumps of the TTF)
+└── src/
+ ├── McLaren-Regular.vfb (original source)
+ ├── McLaren-Regular-OTF.vfb (merged contours for OTF)
+ ├── McLaren-Regular-TTF.vfb (TrueType outlines with hinting)
+ ├── McLaren-Regular.otf.*.ttx (TTX table dumps of the OTF)
+ ├── METADATA_comments.txt (subsetting/processing commands)
+ └── VERSIONS.txt (version info: v1.000)
+```
+
+### Source files
+
+The only source files are three `.vfb` files (FontLab Studio format). These are proprietary binary files that cannot be processed by gftools-builder or fontc. No `.glyphs`, `.ufo`, `.designspace`, or `.sfd` files were found.
+
+The repository also contained TTX dumps (XML representations of compiled font tables) for both the TTF and OTF versions, but these are not buildable sources — they are decompiled representations of the binary fonts.
+
+The `.travis.yml` was configured to use `fontbakery-build.py`, an older build system, not gftools-builder.
+
+## Onboarding History
+
+McLaren was added to Google Fonts on 2012-08-13 according to the `date_added` field. The font file appeared in the google/fonts repository's initial commit (`90abd17b4`, dated 2015-03-07), which was a mass import of the entire Google Fonts library.
+
+The font binary (`McLaren-Regular.ttf`) has never been updated since the initial commit — no subsequent commits in google/fonts modified the font file.
+
+The librefonts/mclaren repository was created on 2014-07-16, after the font was already in Google Fonts. This is a common pattern for the "librefonts" organization, which hosted TTX-decompiled sources for Google Fonts families. These repositories were not the original upstream source but rather a decomposed archive of the shipped fonts.
+
+## Build Configuration
+
+**Config status**: None (no config.yaml exists)
+**Build compatibility**: Not gftools-builder compatible
+
+The source files are exclusively in VFB format (FontLab Studio proprietary format). There is no way to create a config.yaml for gftools-builder without first converting the sources to an open format (.glyphs, .ufo, or .designspace).
+
+An override config.yaml cannot be created because there are no source files in a format that gftools-builder can process.
+
+## Findings
+
+1. **VFB-only sources**: The upstream repository only contains `.vfb` files (FontLab Studio format), which are not compatible with gftools-builder or fontc. The sources would need to be converted to an open format before a build pipeline could be established.
+
+2. **Single commit repository**: The librefonts/mclaren repo has exactly one commit (`7031b7b`), which is simply a Travis CI configuration update. The repo was likely auto-generated from the Google Fonts library rather than being a true upstream source.
+
+3. **No designer GitHub presence**: Brian J. Bonislawsky (Astigmatic) has a GitHub account (`astigmatic`) but it has only 2 generic repositories, neither of which contains font sources. The original design sources likely remain with the designer in FontLab format.
+
+4. **Font never updated**: The binary font file has not been modified since the initial google/fonts commit. The font remains at version 1.001 (per the copyright string) or 1.000 (per VERSIONS.txt).
+
+5. **Source block can be added but status remains incomplete**: A source block pointing to librefonts/mclaren with the single commit hash can be added, but no config_yaml can be provided due to the VFB-only source format.
+
+## Recommended Source Block
+
+```
+source {
+ repository_url: "https://github.com/librefonts/mclaren"
+ commit: "7031b7bdfd833221535738903fe1ea50f1772436"
+ branch: "master"
+}
+```
+
+Note: The `config_yaml` field is intentionally omitted because the repository contains only VFB (FontLab) source files, which are not compatible with gftools-builder. No override config.yaml can be created for the same reason. The source block documents the repository and commit for reference purposes, but a functional build pipeline cannot be established without source format conversion.
--- /dev/null
+# Mea Culpa — Source Investigation
+
+**Model**: Claude Opus 4.6
+**Date**: 2026-03-03
+**Status**: complete
+
+## METADATA.pb Source Block (current)
+
+```
+source {
+ repository_url: "https://github.com/googlefonts/mea-culpa"
+ commit: "13dd5b66076ddc6706d85a30dfed8d007e2f8350"
+ files {
+ source_file: "OFL.txt"
+ dest_file: "OFL.txt"
+ }
+ files {
+ source_file: "DESCRIPTION.en_us.html"
+ dest_file: "DESCRIPTION.en_us.html"
+ }
+ files {
+ source_file: "fonts/ttf/MeaCulpa-Regular.ttf"
+ dest_file: "MeaCulpa-Regular.ttf"
+ }
+ branch: "master"
+ config_yaml: "sources/config.yml"
+}
+```
+
+The source block is fully populated with repository URL, commit hash, file mappings, branch, and config_yaml path.
+
+## Repository Analysis
+
+- **Repository**: https://github.com/googlefonts/mea-culpa
+- **Branch**: master (only branch)
+- **Total commits**: 1 (the initial and only commit)
+- **Remote status**: Clean, up to date with origin
+
+The upstream repository contains a single commit (`13dd5b6`) dated 2021-11-26. This commit created the entire repository with the following structure:
+
+- `sources/MeaCulpaPro.glyphs` — Glyphs source file
+- `sources/config.yml` — gftools-builder configuration
+- `fonts/ttf/MeaCulpa-Regular.ttf` — Pre-built TTF binary
+- `fonts/otf/MeaCulpa-Regular.otf` — Pre-built OTF binary
+- `fonts/webfonts/MeaCulpa-Regular.woff2` — Pre-built WOFF2 binary
+- `.github/workflows/CI-static-ttf.yml` — CI workflow
+- Standard project files: `OFL.txt`, `README.md`, `AUTHORS.txt`, `CONTRIBUTORS.txt`, `DESCRIPTION.en_us.html`, `requirements.txt`
+
+The designer is Robert Leuschke, as documented in METADATA.pb.
+
+## Onboarding History
+
+The font was onboarded to Google Fonts via PR #4136:
+
+- **PR title**: "Mea Culpa: Version 1.010; ttfautohint (v1.8.3) added"
+- **Author**: Viviana Monsalve (@vv-monsalve)
+- **Merged by**: Rosalie Wagner (@RosaWagner)
+- **Merged at**: 2021-12-08
+- **Tool used**: gftools-packager
+
+The PR body explicitly states the font was taken from `https://github.com/googlefonts/mea-culpa` at commit `13dd5b66076ddc6706d85a30dfed8d007e2f8350`, which matches the current METADATA.pb entry.
+
+The onboarding commit in google/fonts (`73ac3ca7`) added:
+- `ofl/meaculpa/DESCRIPTION.en_us.html`
+- `ofl/meaculpa/METADATA.pb`
+- `ofl/meaculpa/MeaCulpa-Regular.ttf`
+- `ofl/meaculpa/OFL.txt`
+- `ofl/meaculpa/upstream.yaml`
+
+The original `upstream.yaml` was later merged into METADATA.pb (commit `66f91f10`).
+
+### Source Block History
+
+The source block was partially present at onboarding (repository_url, branch, files) via the upstream.yaml. The commit hash and config_yaml fields were added later in commit `4ad8ac68` ("[Batch 2/4] port info from fontc_crater targets list") on 2025-03-31.
+
+## Build Configuration
+
+The upstream repository has a `sources/config.yml` file at the referenced commit:
+
+```yaml
+sources:
+ - MeaCulpaPro.glyphs
+familyName: "Mea Culpa"
+buildVariable: false
+# autohintTTF: false
+```
+
+This is a valid gftools-builder configuration that builds from the `MeaCulpaPro.glyphs` source as a static (non-variable) font. The `config_yaml` field in METADATA.pb correctly references `sources/config.yml`.
+
+No override config.yaml exists in the google/fonts family directory, as one is not needed — the upstream repo has its own config file.
+
+## Findings
+
+1. **Binary verification**: The TTF file in google/fonts (`MeaCulpa-Regular.ttf`, 162,232 bytes) has an identical SHA-256 hash (`c5a29315...`) to the file in the upstream repo at the referenced commit. This confirms the commit hash is correct.
+
+2. **Commit hash verified**: The commit `13dd5b66076ddc6706d85a30dfed8d007e2f8350` is the only commit in the repository and was explicitly referenced in the gftools-packager onboarding PR #4136. Since the repo has only one commit, there is no ambiguity about the correct hash.
+
+3. **Source block completeness**: All fields are correctly populated:
+ - `repository_url`: Valid, points to the correct repo
+ - `commit`: Verified correct via binary comparison and PR cross-reference
+ - `branch`: Correctly set to `master`
+ - `config_yaml`: Correctly points to `sources/config.yml` (note the `.yml` extension, matching the actual file)
+ - `files`: File mappings are correct
+
+4. **No issues found**: The source block is complete and accurate. No corrections needed.
+
+## Recommended Source Block
+
+The current source block is correct and complete. No changes needed:
+
+```
+source {
+ repository_url: "https://github.com/googlefonts/mea-culpa"
+ commit: "13dd5b66076ddc6706d85a30dfed8d007e2f8350"
+ files {
+ source_file: "OFL.txt"
+ dest_file: "OFL.txt"
+ }
+ files {
+ source_file: "DESCRIPTION.en_us.html"
+ dest_file: "DESCRIPTION.en_us.html"
+ }
+ files {
+ source_file: "fonts/ttf/MeaCulpa-Regular.ttf"
+ dest_file: "MeaCulpa-Regular.ttf"
+ }
+ branch: "master"
+ config_yaml: "sources/config.yml"
+}
+```
--- /dev/null
+# Meddon — Source Investigation
+
+**Model**: Claude Opus 4.6
+**Date**: 2026-03-03
+**Status**: incomplete
+
+## METADATA.pb Source Block (current)
+
+No source block exists. The current METADATA.pb contains only basic metadata:
+
+```
+name: "Meddon"
+designer: "Vernon Adams"
+license: "OFL"
+category: "HANDWRITING"
+date_added: "2011-02-02"
+```
+
+No `source { }` block is present.
+
+## Repository Analysis
+
+### librefonts/meddon (primary candidate)
+
+- **URL**: https://github.com/librefonts/meddon
+- **Status**: Active (not archived, not a fork)
+- **Default branch**: master
+- **Last push**: 2014-10-17
+- **Single commit**: `0317f7b` (2014-10-17, by hash3g) — "update .travis.yml"
+
+The repository contains:
+- `src/Meddon.sfd` — FontForge source file (SFD format), Version 1.000
+- TTX decomposition files (`.ttx`) — XML dump of the font binary tables
+- `DESCRIPTION.en_us.html`, `METADATA.json`, `OFL.txt`
+- `.travis.yml` — legacy CI configuration using fontbakery-build.py
+
+This repository was part of the `librefonts` organization's batch setup of Google Fonts upstream repos, created with TTX decompositions and FontForge sources. It was set up by hash3g as a standardized mirror.
+
+### vernnobile/MeddonFont (original designer repo)
+
+- **URL**: https://github.com/vernnobile/MeddonFont
+- **Description**: "Repository for Meddon webfont"
+- **Default branch**: master
+- **Last push**: 2012-02-01
+- **3 commits**: earliest from 2012-01-21 ("README"), latest from 2012-02-01 ("in progress")
+
+The repository contains two directories:
+- `Old/` — Meddon.sfd (458,060 bytes), Meddon.ttf (old version), OFL.txt
+- `New/` — Meddon.sfd (458,295 bytes), Meddon.sfd~ (backup), Meddon.ttf (128,632 bytes), OFL.txt
+
+The `vernnobile` GitHub account belongs to Vernon Adams (the font's designer), confirmed via GitHub profile (name: "vernon adams", blog: code.newtypography.co.uk).
+
+The TTF in `New/` (128,632 bytes) matched the initial google/fonts binary size before the nbsp fix was applied.
+
+## Onboarding History
+
+The font was added to Google Fonts on **2011-02-02** according to `date_added` in METADATA.pb, predating the current google/fonts repository structure.
+
+In the current google/fonts repository:
+
+1. **`90abd17b`** (2015-03-07, Dave Crossland) — "Initial commit" — Bulk migration of all Google Fonts into the current repository. The Meddon.ttf was 128,632 bytes at this point.
+
+2. **`d78eefe5`** (2015-03-19, Dave Crossland) — "Update Meddon to fix nbsp" — Updated the binary from 128,632 to 128,264 bytes. This was a targeted fix for the non-breaking space character.
+
+3. **`bacec365`** (2015-08-05, Dave Crossland) — "Fix fsType for 54 font files" — Modified the binary (same size 128,264 bytes) to fix the fsType embedding bits.
+
+No further binary modifications were made after 2015-08-05. Later commits only modified METADATA.pb (classifications, language support, etc.) and a promotional PR #8355 (2024-10-24, "Update families.csv with Meddon for Halloween") that did not touch the font binary.
+
+## Build Configuration
+
+**No config.yaml exists** in either upstream repository.
+
+The font sources are exclusively in **SFD (FontForge) format**. There are no `.glyphs`, `.ufo`, or `.designspace` files in either repository. The SFD format is not compatible with gftools-builder, which requires one of those modern source formats.
+
+The librefonts repo had a legacy `.travis.yml` CI setup using the old `fontbakery-build.py` tool, but this is not equivalent to a modern gftools-builder configuration.
+
+## Findings
+
+1. **No source block in METADATA.pb** — Needs to be added.
+
+2. **SFD-only sources** — Both upstream repos contain only FontForge (.sfd) sources. These are not compatible with gftools-builder. An override config.yaml cannot be created because gftools-builder does not support SFD files.
+
+3. **Two candidate repositories**: The `librefonts/meddon` repo is the more structured of the two (with TTX decomposition and CI), while `vernnobile/MeddonFont` is the original designer's repo. The librefonts repo is the conventional upstream for this family.
+
+4. **Commit hash**: The librefonts repo has only one commit (`0317f7b`), which predates the google/fonts repo. The binary in google/fonts was not built from this repo — it was compiled separately (likely from the SFD using FontForge) and the librefonts repo was set up afterward as a mirror. The commit hash is therefore a reference point for the repo state, not a build provenance marker.
+
+5. **Binary modifications in google/fonts**: The font binary was modified twice after the initial migration (nbsp fix and fsType fix), meaning the current binary in google/fonts does not match any binary in either upstream repo.
+
+6. **Designer**: Vernon Adams (deceased, 2014). The font will not receive upstream updates from the original designer.
+
+## Recommended Source Block
+
+```
+source {
+ repository_url: "https://github.com/librefonts/meddon"
+ commit: "0317f7b9df068bfbcdb958aa49887232c62d3541"
+}
+```
+
+Notes on the recommended block:
+- **repository_url** points to `librefonts/meddon` as the conventional upstream (structured with sources and CI)
+- **commit** is the only commit in the repo (`0317f7b`), serving as a reference point
+- **config_yaml is omitted** because the sources are SFD-only and no config.yaml can be created for gftools-builder
+- **No override config.yaml** is possible because gftools-builder does not support SFD sources
+- The status remains "incomplete" because the SFD-only nature of the sources means the font cannot be rebuilt with modern tooling without first converting the sources to a supported format
--- /dev/null
+# MedievalSharp — Source Investigation
+
+**Model**: Claude Opus 4.6
+**Date**: 2026-03-03
+**Status**: incomplete
+
+## METADATA.pb Source Block (current)
+
+No source block exists. The current METADATA.pb contains only basic font metadata (name, designer, license, category, fonts, subsets, classifications) with no `source { }` block.
+
+## Repository Analysis
+
+### librefonts/medievalsharp (primary upstream candidate)
+
+- **URL**: https://github.com/librefonts/medievalsharp
+- **Default branch**: master
+- **Single commit**: `0bf7f34` (2014-10-17) by hash3g — "update .travis.yml"
+- **Organization**: librefonts (created 2013-10-20), a GitHub organization that hosts TTX-decomposed archives of Google Fonts families
+- **Contents**: TTX decomposition of the binary font, plus source files in `src/` directory
+- **Source files**:
+ - `src/MedievalSharp.sfd` — FontForge source (793 KB)
+ - `src/MedievalSharp-TTF.vfb` — FontLab Studio source (222 KB)
+ - `src/MedievalSharp.png` — demo image
+- **Build system**: Old fontbakery-build pipeline via `.travis.yml` (pre-gftools era)
+- **No config.yaml**: No gftools-builder configuration exists
+- **No gftools-compatible sources**: No `.glyphs`, `.ufo`, or `.designspace` files
+
+### wmk69/Medieval-Sharp (designer's repo)
+
+- **URL**: https://github.com/wmk69/Medieval-Sharp
+- **Default branch**: main
+- **Created**: 2022-03-13 (much later than Google Fonts onboarding)
+- **Single commit**: `ee7510b` (2022-03-13) — "Add files via upload"
+- **Contents**: An expanded 4-style family (Book, BookOblique, Bold, BoldOblique) with SFD sources and TTF binaries
+- **Not the onboarding source**: This repo was created 7+ years after the font was added to Google Fonts and contains a different (expanded) version of the family
+
+### Source Format
+
+Both repositories contain only FontForge SFD sources. The gftools-builder toolchain does not support SFD as an input format — it requires `.glyphs`, `.ufo`, or `.designspace` files. Therefore, no config.yaml can be meaningfully created for this font without a source format conversion.
+
+## Onboarding History
+
+- **Added to Google Fonts**: 2011-03-02 (per `date_added` in METADATA.pb)
+- **Initial commit in google/fonts repo**: `90abd17b4` (2015-03-07) by Dave Crossland — "Initial commit" (this was the bulk import of the entire google/fonts repository; the font predated this commit)
+- **Font binary has not been updated** since the initial commit — the only subsequent commits touched METADATA files (METADATA.json, METADATA.pb), not the font binary
+- **Font metadata from binary**: Created with FontForge on 2011-02-27, Version 1.0, copyright by wmk69 (Wojciech Kalinowski)
+- **Original source**: The font was originally published on Open Font Library (http://openfontlibrary.org) per the FONTLOG.txt
+
+The librefonts/medievalsharp repository was created in 2014 as a TTX-decomposed archive of the font, predating the google/fonts initial commit (2015). The single commit (`0bf7f34`) represents the state of the sources at that time.
+
+## Build Configuration
+
+**No config.yaml exists or can be created.** The font sources are exclusively in FontForge SFD format, which is not supported by gftools-builder. Building from these sources would require:
+
+1. Converting the SFD to a gftools-compatible format (UFO or .glyphs)
+2. Creating a config.yaml referencing the converted sources
+3. Verifying the build output matches the existing binary
+
+This is outside the scope of metadata enrichment and would constitute a font engineering task.
+
+## Findings
+
+1. **No source block in METADATA.pb** — needs to be added
+2. **librefonts/medievalsharp is the appropriate upstream repo** — it contains the SFD source and VFB source files for the single-style font that matches what is in Google Fonts
+3. **The only commit is `0bf7f34`** — this is the sole commit in the repository and represents the archived state of the sources
+4. **SFD-only sources** — gftools-builder cannot build from SFD files, so no config.yaml can be provided
+5. **wmk69/Medieval-Sharp is NOT the onboarding repo** — it was created in 2022, contains an expanded 4-style family, and represents newer work by the designer
+6. **The font has not been updated since initial onboarding** — the binary in google/fonts dates to 2011 and has never been rebuilt
+
+## Recommended Source Block
+
+```
+source {
+ repository_url: "https://github.com/librefonts/medievalsharp"
+ commit: "0bf7f34428dfca63c645b586572e85af77095d08"
+ branch: "master"
+}
+```
+
+**Notes**:
+- No `config_yaml` field is included because the sources are SFD-only and no gftools-builder configuration exists or can be created without source format conversion
+- The commit hash `0bf7f34428dfca63c645b586572e85af77095d08` is the only commit in the repository
+- Status is "incomplete" because while the repository URL and commit are known, there is no gftools-builder compatible build configuration
--- /dev/null
+# Medula One — Source Investigation
+
+**Model**: Claude Opus 4.6
+**Date**: 2026-03-03
+**Status**: incomplete (SFD/VFB-only sources, no gftools-builder config possible)
+
+## METADATA.pb Source Block (current)
+
+No source block exists. The current METADATA.pb contains only basic metadata:
+
+```
+name: "Medula One"
+designer: "LatinoType"
+license: "OFL"
+category: "DISPLAY"
+date_added: "2011-12-19"
+fonts {
+ name: "Medula One"
+ style: "normal"
+ weight: 400
+ filename: "MedulaOne-Regular.ttf"
+ post_script_name: "MedulaOne-Regular"
+ full_name: "Medula One"
+ copyright: "Copyright (c) 2011 by LatinoType Limitada (luciano@latinotype.com), with Reserved Font Names \"Medula\""
+}
+subsets: "menu"
+subsets: "latin"
+subsets: "latin-ext"
+```
+
+## Repository Analysis
+
+**Upstream repository**: https://github.com/librefonts/medulaone
+
+The repository belongs to the `librefonts` GitHub organization, which was used as a mirror/archive for Google Fonts library source files. It was created on 2014-07-16 by Mikhail Kashkin (@xen), whose initial commit message was "Move medulaone font files to separate repository" — indicating this was a reorganization of files from a larger collection into individual per-family repositories.
+
+The repo is not a fork and has no description. It is not archived.
+
+### Repository Contents (at HEAD, commit `9559bbd`)
+
+The repository contains:
+- **Decomposed TTX files** of the compiled TTF font (split into per-table `.ttx` files)
+- **Source files** in `src/`:
+ - `MedulaOne-Regular-TTF.sfd` — FontForge Spline Font Database (269 KB)
+ - `MedulaOne-Regular-OTF.vfb` — FontLab VFB binary (102 KB)
+ - Decomposed TTX files of the OTF version
+ - `METADATA_comments.txt` — subsetting commands used during original onboarding
+ - `VERSIONS.txt` — indicates "Version 1.002"
+- `.travis.yml` — Travis CI configuration using fontbakery-build.py (legacy)
+- `METADATA.json`, `DESCRIPTION.en_us.html`, `OFL.txt`
+
+### Commit History (12 commits total, all from 2014)
+
+| Hash | Date | Author | Message |
+|------|------|--------|---------|
+| `71bda1c` | 2014-07-16 | Mikhail Kashkin (@xen) | Move medulaone font files to separate repository |
+| `895207b` | 2014-08-19 | hash3g | Added .travis.yml |
+| `e4fa02a` | 2014-08-21 | hash3g | Travis.yml update |
+| `9a7c880` | 2014-08-22 | hash3g | Travis.yml update |
+| `ace72d0` | 2014-08-22 | hash3g | Travis.yml update |
+| `03e838b` | 2014-09-11 | hash3g | update .travis.yml |
+| `5a516c2` | 2014-09-12 | hash3g | Added raw=True to VDMX and FFTM |
+| `2067801` | 2014-09-14 | hash3g | Installing ttfautohint from ppa |
+| `5a468a8` | 2014-09-15 | hash3g | Update .travis.yml |
+| `7a2807a` | 2014-09-19 | hash3g | Update .travis.yml |
+| `31c582f` | 2014-10-06 | hash3g | Rename fontbakery |
+| `9559bbd` | 2014-10-17 | hash3g | update .travis.yml |
+
+All commits after the initial one were Travis CI configuration updates by hash3g. The source files (SFD, VFB) were never modified after the initial commit.
+
+### Contributors
+- **Mikhail Kashkin** (@xen) — created the repo by extracting files from a larger collection
+- **hash3g** — contributed all Travis CI configuration updates
+
+### No config.yaml
+
+The repository has no `config.yaml` file. The Travis CI configuration used the legacy `fontbakery-build.py` tool, which is not compatible with modern gftools-builder.
+
+## Onboarding History
+
+Medula One was added to Google Fonts on **2011-12-19** (per `date_added` in METADATA.pb). The font file was included in the google/fonts repository in the **initial commit** (`90abd17b4`, dated 2015-03-07), which was the bulk import of all existing Google Fonts families into the current repository structure.
+
+The font binary (`MedulaOne-Regular.ttf`) was **never modified** after the initial commit — no updates or rebuilds were ever applied.
+
+The `librefonts/medulaone` repository was created on **2014-07-16**, approximately 2.5 years after the font was added to Google Fonts. This confirms the librefonts repo is a post-hoc archive of the source files, not the original development repository.
+
+## Build Configuration
+
+**No gftools-builder configuration is possible.**
+
+The only source files available are:
+1. **`MedulaOne-Regular-TTF.sfd`** — FontForge SFD format
+2. **`MedulaOne-Regular-OTF.vfb`** — FontLab VFB binary format
+
+Neither format is supported by gftools-builder, which requires `.glyphs`, `.ufo`, or `.designspace` sources. No override `config.yaml` can be created because there are no compatible source files to reference.
+
+The original font was designed by **LatinoType** (Luciano Vergara, luciano@latinotype.com) and was likely compiled using FontForge or FontLab directly. The copyright notice dates to 2011.
+
+## Findings
+
+1. **No source block in METADATA.pb** — needs to be added with repository_url and commit hash.
+2. **Repository is a post-hoc archive** — the librefonts/medulaone repo was created in 2014, while the font was added to Google Fonts in 2011. The repo was created by Mikhail Kashkin as part of the librefonts organization's effort to create per-family repositories from the earlier googlefontdirectory collection.
+3. **SFD/VFB-only sources** — the upstream repo only has FontForge (.sfd) and FontLab (.vfb) source files. These are not compatible with gftools-builder and cannot be used with a config.yaml.
+4. **Single commit for source files** — the initial commit `71bda1c` (2014-07-16) contains all source files. Subsequent commits only modified the Travis CI configuration.
+5. **Font binary unchanged since initial import** — the TTF file in google/fonts was never updated after the bulk initial commit.
+6. **Shallow clone in cache** — the local clone is shallow (depth=1), containing only the latest commit `9559bbd`. The full history was obtained via the GitHub API.
+7. **The appropriate commit for the source block is `9559bbd`** (HEAD of master), since the source files are unchanged across all commits and this is the latest state of the repository.
+
+## Recommended Source Block
+
+```
+source {
+ repository_url: "https://github.com/librefonts/medulaone"
+ commit: "9559bbd73be136d236851c03e0050708315aef2e"
+}
+```
+
+**Notes on the recommendation:**
+- The `config_yaml` field is omitted because there are no gftools-builder compatible sources (SFD/VFB only).
+- The commit `9559bbd` is used as it is HEAD of master and the source files are identical to the initial commit.
+- No override config.yaml is possible since the source formats are incompatible with gftools-builder.
+- Status: `missing_config` — this family has SFD-only sources that cannot be used with gftools-builder.
--- /dev/null
+# Meera Inimai — Source Investigation
+
+**Model**: Claude Opus 4.6
+**Date**: 2026-03-03
+**Status**: incomplete
+
+## METADATA.pb Source Block (current)
+
+No source block exists in the METADATA.pb file.
+
+## Repository Analysis
+
+The upstream repository is `https://github.com/santhoshtr/meera-tamil`, maintained by Santhosh Thottingal (one of the copyright holders listed in the font). The repository contains:
+
+- `MeeraTamil-Regular.sfd` — FontForge SFD source (the only editable source)
+- `features/` — OpenType feature files
+- `Makefile` — Custom build using FontForge scripting
+- `ttf/` — Pre-compiled TTF binaries
+- `tools/` — Build helper scripts
+
+The repo was renamed from "MeeraTamil" to "meera-tamil" at some point. It has 23 commits, with the latest being `75261af` (2016-03-26, "Rename MeeraTamil.sfd -> MeeraTamil-Regular.sfd").
+
+Note: The font name in Google Fonts is "Meera Inimai" but the upstream project is called "Meera Tamil". These appear to be the same font — the copyright strings match.
+
+## Onboarding History
+
+The font was added to google/fonts via PR #1000 ("hotfix-meerainimai: v2.001 added"), merged as commit `30dc4b94a`. It was later restructured in the deploy commit `76adaf1d2`. The font has never been updated since.
+
+## Build Configuration
+
+The upstream repo uses a custom `Makefile` with FontForge scripting (`tools/generate.py`) to build the font. The sources are exclusively in SFD format, which is not compatible with gftools-builder. No `config.yaml` exists and none can be created without first converting the SFD to a modern format (.ufo, .glyphs, or .designspace).
+
+## Findings
+
+1. The font has no source block in METADATA.pb
+2. The upstream repository (`santhoshtr/meera-tamil`) was identified by searching GitHub for the font name and matching copyright holders
+3. Sources are SFD-only — no gftools-builder compatible formats exist
+4. No override `config.yaml` can be created
+5. The font name differs between Google Fonts ("Meera Inimai") and the upstream repo ("Meera Tamil")
+
+## Recommended Source Block
+
+```
+source {
+ repository_url: "https://github.com/santhoshtr/meera-tamil"
+ commit: "75261af9389afed926f31e44043864ae50fd76f4"
+ branch: "master"
+}
+```
+
+No `config_yaml` field is possible due to SFD-only sources.
+
+**Confidence**: MEDIUM — the copyright strings match but the font names differ slightly between Google Fonts and the upstream repo.
--- /dev/null
+# Megrim — Source Investigation
+
+**Model**: Claude Opus 4.6
+**Date**: 2026-03-03
+**Status**: incomplete (SFD-only sources, no gftools-builder config possible)
+
+## METADATA.pb Source Block (current)
+
+No source block exists on the current `main` branch of google/fonts. A source block was prepared on a local branch (`sources_info_2026-02-25`) but has not been merged:
+
+```
+source {
+ repository_url: "https://github.com/librefonts/megrim"
+ commit: "274ef534110a60534a520038400a8db0b3abd976"
+}
+```
+
+## Repository Analysis
+
+**Repository**: https://github.com/librefonts/megrim
+**Status**: Accessible (HTTP 200), not archived, not a fork
+**Created**: 2014-07-16
+**Last pushed**: 2014-10-17
+**Organization**: librefonts (a third-party archive organization that mirrors Google Fonts sources)
+
+The repository contains a single commit (`274ef53`) by `hash3g` dated 2014-10-17, with the message "update .travis.yml". This is not the original author's repository — it is an archive created by the librefonts organization.
+
+### Repository Structure
+
+```
+/
+├── DESCRIPTION.en_us.html
+├── FONTLOG.txt
+├── METADATA.json
+├── Megrim.ttf.*.ttx (TTX-decomposed tables of the TrueType binary)
+├── OFL.txt
+├── .travis.yml (FontBakery CI config, outdated)
+└── src/
+ ├── Megrim-TTF.sfd (FontForge source, 405 KB)
+ ├── Megrim.vfb (FontLab source, 110 KB)
+ ├── Megrim.otf.*.ttx (TTX-decomposed tables of the OTF binary)
+ ├── METADATA_comments.txt
+ └── VERSIONS.txt
+```
+
+### Source Files
+
+- **Megrim-TTF.sfd**: FontForge SFD source file, created 2010-05-05, last modified 2011-04-28. This is the primary editable source.
+- **Megrim.vfb**: FontLab VFB binary source file (110 KB). Secondary source format.
+- **TTX files**: Decomposed TTX tables of the compiled font. These are not editable design sources.
+
+No `.glyphs`, `.ufo`, or `.designspace` files exist. The sources are exclusively in legacy formats (SFD/VFB) that are not compatible with gftools-builder.
+
+### Contributors to librefonts/megrim
+
+- `vitalyvolkov`
+- `xen`
+
+Neither is the original font designer (Daniel Johnson).
+
+## Onboarding History
+
+**Designer**: Daniel Johnson (il.basso.buffo@gmail.com)
+**Date added to Google Fonts**: 2011-05-04
+**Font version**: 20110427
+
+The font was part of the initial bulk import into the google/fonts repository (commit `90abd17b4`, 2015-03-07, by Dave Crossland). The font binary has never been updated since the initial import — there is only one commit that added the `.ttf` file.
+
+The FONTLOG changelog shows:
+- 2010-05-11: Initial release
+- 2010-07-02: Improved lowercase Icelandic glyphs; added more glyphs with diacritics
+- 2010-08-31: Added stylistic alternate set (ss01); added Turkish glyphs
+
+The SFD file's modification timestamp (2011-04-28) aligns with the font binary version string (20110427).
+
+There were no PRs associated with the onboarding of this font. It was part of the original Google Fonts catalog that predated the current github-based workflow.
+
+A deploy commit (`76adaf1d2`, 2021-11-01, by m4rc1e) appeared to delete the megrim directory, but this commit exists on an orphaned branch and was never merged into main.
+
+### Original Author's Repository
+
+Daniel Johnson's personal page was listed as `http://io.debian.net/~danielj/` in the FONTLOG. No personal GitHub repository was found for Daniel Johnson under this font name. The librefonts/megrim archive appears to be the only GitHub repository containing the source files for this font.
+
+## Build Configuration
+
+**Config.yaml**: None, and none possible.
+
+The upstream repository contains only SFD (FontForge) and VFB (FontLab) source files. These legacy formats are not supported by gftools-builder, which requires `.glyphs`, `.ufo`, or `.designspace` sources. Therefore, no `config.yaml` can be created for this font without first converting the sources to a modern format.
+
+The repository's `.travis.yml` used the old `fontbakery-build.py` pipeline (circa 2014), which is no longer in use.
+
+## Findings
+
+1. **No original upstream repository exists** — The librefonts/megrim repo is a third-party archive, not the original author's repository. Daniel Johnson does not appear to have a GitHub presence for this font.
+
+2. **SFD-only sources** — The only editable design source is a FontForge `.sfd` file. This format is not compatible with gftools-builder, so no `config.yaml` can be provided.
+
+3. **Single commit in upstream** — The archive repository has only one commit (`274ef53`), which is the only possible reference commit.
+
+4. **Font has not been updated since onboarding** — The font binary in google/fonts is the original from the 2015 initial import, matching the 2011-era sources.
+
+5. **Source block was already prepared** — A source block with `repository_url` and `commit` was prepared on a local branch but has not been pushed to google/fonts main.
+
+## Recommended Source Block
+
+```
+source {
+ repository_url: "https://github.com/librefonts/megrim"
+ commit: "274ef534110a60534a520038400a8db0b3abd976"
+}
+```
+
+No `config_yaml` field is included because the sources are in SFD format (FontForge), which is not compatible with gftools-builder. An override config.yaml is also not possible without source format conversion.
+
+**Confidence**: HIGH — The librefonts/megrim repo is the only known GitHub repository for this font, and it contains the correct SFD source matching the compiled binary. The single commit (`274ef53`) is the only possible reference.
projects / thirdparty / google / fonts.git / commitdiff
