--- /dev/null
+# Investigation Report: Cousine
+
+## Summary
+
+Cousine is a monospace sans-serif font designed by Steve Matteson at Monotype Imaging, part of the Chrome OS core fonts family (alongside Arimo and Tinos). It is metrically compatible with Courier New. The current binaries in google/fonts are Version 1.21, last updated via PR #769 in August 2017. There is a development repository at `googlefonts/cousine` (created July 2020 by Marek Jeziorek) containing .glyphs sources and a variable font build, but the currently-serving static binaries predate this repo. There is also a `librefonts/cousine` mirror containing TTX dumps and no buildable sources. No config.yaml exists in either repo.
+
+## Key Findings
+
+| Field | Value |
+|--------------------|-------|
+| Family Name | Cousine |
+| Designer | Steve Matteson |
+| License | Apache 2.0 |
+| Category | MONOSPACE |
+| Date Added | 2010-11-18 |
+| Repository URL | https://github.com/googlefonts/cousine |
+| Commit Hash | Not determinable for current v1.21 binaries |
+| Config YAML | None (no config.yaml in repo) |
+| Source Types | .glyphs (in googlefonts/cousine, for future VF build) |
+| Font Version | 1.21 |
+| Status | missing_config |
+| Confidence | MEDIUM |
+
+## Investigation Details
+
+### Current State in google/fonts
+
+- **Directory**: `apache/cousine/`
+- **Files**: Cousine-Regular.ttf, Cousine-Italic.ttf, Cousine-Bold.ttf, Cousine-BoldItalic.ttf, DESCRIPTION.en_us.html, LICENSE.txt, METADATA.pb
+- **No source block** in METADATA.pb
+- **Font version**: Version 1.21 (from name table: "1.21;MONO;Cousine-Regular")
+- **Copyright**: "Digitized data copyright (c) 2010-2012 Google Corporation."
+- **Vendor**: Monotype Imaging Inc.
+
+### Git History in google/fonts
+
+| Commit | Date | Author | Description |
+|--------|------|--------|-------------|
+| b8df781 | 2017-08-07 | Marc Foley | hotfix-cousine: v1.211 added (#769) |
+| 49fbebd | 2017 | (batch) | chmod -x on all font files |
+| 90abd17 | 2015-03-07 | Dave Crossland | Initial commit |
+
+The last substantive font update was PR #769, merged 2017-08-07 by Marc Foley. The PR body was empty, providing no upstream reference or commit hash.
+
+### Upstream Repository: googlefonts/cousine
+
+- **URL**: https://github.com/googlefonts/cousine
+- **Created**: 2020-07-05 by Marek Jeziorek (marekj@google.com)
+- **Default branch**: main
+- **Description**: "Cousine sources, tests and development fonts"
+- **Source files**: .glyphs format (sources/Cousine-Regular/Cousine-Regular.glyphs, etc.)
+- **Built fonts**: Variable font only (fonts/ttf/hinted/variable_ttf/Cousine-VF.ttf)
+- **No config.yaml** present in the repo
+- **10 commits total**, last updated 2021-02-28
+
+This repository was created in 2020 as a development repo for a variable font version of Cousine, using .glyphs sources. The variable font build has NOT been pushed to google/fonts yet -- the catalog still serves the older static v1.21 TTFs.
+
+### Cached Mirror: librefonts/cousine
+
+- **Path**: upstream_repos/fontc_crater_cache/librefonts/cousine
+- **URL**: https://github.com/librefonts/cousine
+- **Content**: TTX dumps of the binary fonts, plus FontForge subset scripts in src/
+- **Source type**: TTX (decompiled binary, not original design sources)
+- **Single commit** by hash3g (2014-10-17): "update .travis.yml"
+- **Versions file**: Lists Version 1.21 for all four styles
+
+This is a librefonts automated mirror containing decompiled TTX files. It is not a proper upstream source repository and should not be used as the repository_url in METADATA.pb.
+
+### Origin of Current Binaries
+
+The current v1.21 binaries were produced by Monotype Imaging (as indicated by the font name table). Cousine is one of the Chrome OS core fonts originally developed by Ascender Corporation (later acquired by Monotype). The fonts were delivered to Google as compiled binaries. The googlefonts/cousine repo was created later (2020) as a development workspace for a future variable font version.
+
+The font version string says "Version 1.21" but the PR #769 title says "v1.211" -- this appears to be a minor discrepancy in the commit message (the actual name table says 1.21).
+
+### Config.yaml Assessment
+
+Neither the googlefonts/cousine repo nor the librefonts mirror has a config.yaml file. The googlefonts/cousine repo has .glyphs sources that could potentially be built with gftools-builder, but:
+1. The current binaries were not built from these sources
+2. There are four separate .glyphs files (one per style), not a single source
+3. No build configuration exists
+
+## Conclusion
+
+The repository URL should be set to `https://github.com/googlefonts/cousine` as this is the official Google Fonts development repository. However, the current binaries predate this repo and were produced by Monotype. A specific onboarding commit hash cannot be determined for the v1.21 binaries. No config.yaml is available.
+
+### Recommended METADATA.pb Source Block
+
+```
+source {
+ repository_url: "https://github.com/googlefonts/cousine"
+}
+```
+
+**Note**: No commit hash or config_yaml can be specified because:
+- The current v1.21 binaries were produced by Monotype before the GitHub repo existed
+- The googlefonts/cousine repo contains newer development work (variable font) that has not been published to google/fonts yet
+- No config.yaml exists in the repo
+
+### Status: missing_config
+### Confidence: MEDIUM
+
+The repository URL is correct (official googlefonts org), but the relationship between the repo contents and the currently-serving binaries is indirect -- the repo represents future development, not the source of the current fonts.
--- /dev/null
+# Investigation Report: Crafty Girls
+
+## Summary
+
+Crafty Girls is a handwriting font designed by Crystal Kluge for Font Diner, Inc (DBA Tart Workshop). It was added to Google Fonts on 2011-01-06 and last updated via PR #770 in August 2017. There is no dedicated upstream repository beyond the `librefonts/craftygirls` automated mirror, which contains only TTX dumps and decompiled source files. No original design sources (.glyphs, .ufo, .designspace) or config.yaml exist. The font was produced by Font Diner and delivered as a compiled binary.
+
+## Key Findings
+
+| Field | Value |
+|--------------------|-------|
+| Family Name | Crafty Girls |
+| Designer | Tart Workshop (Crystal Kluge) |
+| License | Apache 2.0 |
+| Category | HANDWRITING |
+| Date Added | 2011-01-06 |
+| Repository URL | None (no proper upstream repo) |
+| Commit Hash | N/A |
+| Config YAML | None |
+| Source Types | TTX only (librefonts mirror) |
+| Font Version | 1.001 |
+| Status | no_upstream_repo |
+| Confidence | HIGH |
+
+## Investigation Details
+
+### Current State in google/fonts
+
+- **Directory**: `apache/craftygirls/`
+- **Files**: CraftyGirls-Regular.ttf, DESCRIPTION.en_us.html, LICENSE.txt, METADATA.pb
+- **No source block** in METADATA.pb
+- **Font version**: Version 1.001 (from name table: "1.001;DINR;CraftyGirls-Regular")
+- **Copyright**: "Copyright (c) 2010 by Font Diner, Inc DBA Tart Workshop. All rights reserved."
+- **Vendor**: Font Diner, Inc DBA Tart Workshop
+- **Designer credit**: Crystal Kluge
+
+### Git History in google/fonts
+
+| Commit | Date | Author | Description |
+|--------|------|--------|-------------|
+| 98e7670 | 2017-08-07 | Marc Foley | hotfix-craftygirls: v1.001 added (#770) |
+| 64d3e3a | earlier | (batch) | Remove duplicate files |
+| 90abd17 | 2015-03-07 | Dave Crossland | Initial commit |
+
+PR #770 (merged 2017-08-07 by Marc Foley) renamed the font file from CraftyGirls.ttf to CraftyGirls-Regular.ttf and updated metadata. The PR body was empty.
+
+### Cached Mirror: librefonts/craftygirls
+
+- **Path**: upstream_repos/fontc_crater_cache/librefonts/craftygirls
+- **URL**: https://github.com/librefonts/craftygirls
+- **Content**: TTX dumps of the binary font, plus src/ directory with more TTX files and metadata
+- **Source type**: TTX only (decompiled from binary, not original design sources)
+- **Single commit** by hash3g (undated): "update .travis.yml"
+- **Versions file**: Lists Version 1.000
+
+The librefonts mirror is an automated TTX dump. The src/ directory contains CraftyGirls-TTX.ttf.*.ttx files (decompiled table dumps). These are NOT original design sources and cannot be used to rebuild the font with gftools-builder.
+
+### Search for Upstream Repository
+
+- **No googlefonts/craftygirls** or **googlefonts/crafty-girls** repository exists
+- **fontdiner/fonts** exists on GitHub but is empty (only LICENSE and README.md)
+- **No other upstream repository** was found for this font
+- Font Diner / Tart Workshop is a commercial foundry; the font was contributed under Apache 2.0 but the original design sources (.vfb or similar) were likely never published
+
+### Config.yaml Assessment
+
+No config.yaml exists anywhere. The only available source format is TTX (decompiled binary tables), which is not compatible with gftools-builder. The original design sources (likely FontLab .vfb format given the era and foundry) were never published.
+
+## Conclusion
+
+Crafty Girls has no proper upstream repository. The librefonts/craftygirls mirror contains only TTX dumps and should not be used as a repository_url. The font was produced by Font Diner and delivered as a compiled binary to Google Fonts. No original design sources or build configuration exist.
+
+### Recommended METADATA.pb Source Block
+
+No source block can be added. There is no upstream repository containing original design sources.
+
+### Status: no_upstream_repo
+### Confidence: HIGH
+
+There is no proper upstream repository for this font. The font was created by Font Diner (a commercial foundry) and the original design files were never published to a public repository.
--- /dev/null
+# Investigation Report: Creepster Caps
+
+## Summary
+
+Creepster Caps is a display font designed by Font Diner, Inc (DBA Sideshow), featuring a horror/Halloween-themed aesthetic. It was added to Google Fonts on 2011-10-24 via the initial commit and has never been updated since. The only cached repository is the `librefonts/creepstercaps` mirror, which contains TTX dumps and a FontForge SFD source file. No dedicated upstream repository with gftools-builder compatible sources exists. There is a related but distinct font "Creepster" (without "Caps") in the OFL directory, which has its own librefonts mirror.
+
+## Key Findings
+
+| Field | Value |
+|--------------------|-------|
+| Family Name | Creepster Caps |
+| Designer | Sideshow (Font Diner, Inc) |
+| License | Apache 2.0 |
+| Category | DISPLAY |
+| Date Added | 2011-10-24 |
+| Repository URL | None (no proper upstream repo) |
+| Commit Hash | N/A |
+| Config YAML | None |
+| Source Types | SFD (FontForge format, in librefonts mirror) |
+| Font Version | 1.000 |
+| Status | no_upstream_repo |
+| Confidence | HIGH |
+
+## Investigation Details
+
+### Current State in google/fonts
+
+- **Directory**: `apache/creepstercaps/`
+- **Files**: CreepsterCaps-Regular.ttf, DESCRIPTION.en_us.html, LICENSE.txt, METADATA.pb
+- **No source block** in METADATA.pb
+- **Font version**: Version 1.000 (from name table)
+- **Copyright**: "Copyright (c) 2011 by Font Diner, Inc. All rights reserved."
+- **Vendor**: Font Diner, Inc
+- **Note**: The copyright says 2011, and the font was added with the initial commit in March 2015
+
+### Git History in google/fonts
+
+| Commit | Date | Author | Description |
+|--------|------|--------|-------------|
+| 90abd17 | 2015-03-07 | Dave Crossland | Initial commit |
+
+Creepster Caps has never been updated since the initial commit. All subsequent commits touching this directory were metadata-only changes (METADATA.pb language data, etc.).
+
+### Relationship to "Creepster" (OFL)
+
+There is a separate font called "Creepster" (without "Caps") in `ofl/creepster/`. That font is also by Font Diner/Sideshow and has a similar horror theme. The OFL version has its own librefonts mirror at `librefonts/creepster` with SFD sources. These are two distinct fonts:
+- **Creepster Caps** (Apache 2.0, in `apache/creepstercaps/`) - this investigation
+- **Creepster** (OFL, in `ofl/creepster/`) - separate font, already investigated
+
+### Cached Mirror: librefonts/creepstercaps
+
+- **Path**: upstream_repos/fontc_crater_cache/librefonts/creepstercaps
+- **URL**: https://github.com/librefonts/creepstercaps
+- **Content**: TTX dumps of the binary font, plus SFD source in src/
+- **Source files**:
+ - `src/CreepsterCaps-Regular-TTF.sfd` - FontForge SFD format
+ - TTX table dumps at root level
+- **Single commit** by hash3g: "update .travis.yml"
+- **Versions file**: Lists Version 1.000
+
+The SFD file header confirms:
+- FontName: CreepsterCaps-Regular
+- Version: 1.001 (slightly newer than the binary's 1.000)
+- Copyright: "Copyright (c) 2011 by Font Diner, Inc. All rights reserved."
+- CreationTime: 1319137200 (approx Oct 20, 2011)
+- ModificationTime: 1319464871 (approx Oct 24, 2011)
+
+### Search for Upstream Repository
+
+- **No googlefonts/creepstercaps** or similar repository exists
+- **No googlefonts/creepster-caps** repository exists
+- **fontdiner/fonts** exists but is empty (LICENSE and README.md only)
+- The librefonts mirror is the only repository, and it is an automated dump, not a proper upstream
+
+### Config.yaml Assessment
+
+No config.yaml exists. The only source format available is SFD (FontForge), which is not compatible with gftools-builder. The SFD file contains the "-TTF" suffix in its filename, suggesting it was reverse-engineered from the TTF binary rather than being the original design source.
+
+The original design sources were likely in a proprietary format (FontLab .vfb or similar) used by Font Diner and never published.
+
+## Conclusion
+
+Creepster Caps has no proper upstream repository. The librefonts/creepstercaps mirror contains TTX dumps and a FontForge SFD file (likely reverse-engineered), but these are not suitable as a proper upstream. The font was produced by Font Diner and delivered as a compiled binary. No gftools-builder compatible sources or build configuration exist.
+
+### Recommended METADATA.pb Source Block
+
+No source block can be added. There is no upstream repository containing original design sources.
+
+### Status: no_upstream_repo
+### Confidence: HIGH
+
+There is no proper upstream repository for this font. The font was created by Font Diner (a commercial foundry) and the original design files were never published to a public repository. The librefonts mirror contains only decompiled/reverse-engineered files.
--- /dev/null
+# Cossette Texte - Investigation Report
+
+## Source Data
+
+| Field | Value |
+|---|---|
+| Family Name | Cossette Texte |
+| Repository URL | https://github.com/googlefonts/cossette-fonts |
+| Commit Hash | ee99cea3c23039e31865c3c37bd7d716278e546b |
+| Branch | main |
+| Config YAML | sources/config-texte.yaml |
+| Designer | Cossette |
+| License | OFL |
+| Date Added | 2025-07-29 |
+
+## How URL Found
+
+The repository URL `https://github.com/googlefonts/cossette-fonts` is documented directly in the METADATA.pb `source {}` block added when the font was onboarded. The copyright strings in the font entries also reference this repository URL.
+
+## How Commit Determined
+
+The commit hash `ee99cea3c23039e31865c3c37bd7d716278e546b` is explicitly stated in the google/fonts commit message (ca5e6235b, authored by Marc Foley on 2025-09-30):
+
+> "Taken from the upstream repo https://github.com/googlefonts/cossette-fonts at commit https://github.com/googlefonts/cossette-fonts/commit/ee99cea3c23039e31865c3c37bd7d716278e546b."
+
+This commit is also the only commit (HEAD) of the upstream repository ("Merge pull request #2 from googlefonts/url"). The upstream repo has only a single commit.
+
+## Config YAML Status
+
+The config file `sources/config-texte.yaml` exists in the upstream repository at the referenced commit. It contains:
+
+```yaml
+familyName: Cossette Texte
+sources:
+ - CossetteTexte-Regular.ufo
+ - CossetteTexte-Bold.ufo
+buildVariable: false
+includeSourceFixes: true
+```
+
+This is a valid gftools-builder configuration pointing to UFO sources.
+
+## Verification
+
+- **Repository accessible**: Yes - cloned at `upstream_repos/fontc_crater_cache/googlefonts/cossette-fonts/`
+- **Commit exists**: Yes - `ee99cea` is HEAD (and only commit) of the repo
+- **Config exists at commit**: Yes - `sources/config-texte.yaml` is present
+- **Source files present**: Yes - UFO sources for Regular and Bold weights
+- **Font files match**: Binary .ttf files are mapped via `files {}` entries in METADATA.pb
+
+## Confidence Level
+
+**HIGH** - All data is fully documented in the METADATA.pb source block and confirmed by the google/fonts commit message. The upstream repo has only one commit, making verification trivial.
+
+## Open Questions
+
+None.
--- /dev/null
+# Cossette Titre - Investigation Report
+
+## Source Data
+
+| Field | Value |
+|---|---|
+| Family Name | Cossette Titre |
+| Repository URL | https://github.com/googlefonts/cossette-fonts |
+| Commit Hash | ee99cea3c23039e31865c3c37bd7d716278e546b |
+| Branch | main |
+| Config YAML | sources/config-titre.yaml |
+| Designer | Cossette |
+| License | OFL |
+| Date Added | 2025-07-29 |
+
+## How URL Found
+
+The repository URL `https://github.com/googlefonts/cossette-fonts` is documented in the METADATA.pb `source {}` block. This is a shared repository that contains both Cossette Texte and Cossette Titre font families. The copyright strings in the font entries also reference this repository.
+
+## How Commit Determined
+
+The commit hash `ee99cea3c23039e31865c3c37bd7d716278e546b` is explicitly stated in the google/fonts commit message (98a7dc08b, authored by Marc Foley on 2025-09-30):
+
+> "Taken from the upstream repo https://github.com/googlefonts/cossette-fonts at commit https://github.com/googlefonts/cossette-fonts/commit/ee99cea3c23039e31865c3c37bd7d716278e546b."
+
+This is the same commit used for Cossette Texte, which makes sense as both families share the same repository. The commit is HEAD (and the only commit) of the upstream repository.
+
+## Config YAML Status
+
+The config file `sources/config-titre.yaml` exists in the upstream repository at the referenced commit. It contains:
+
+```yaml
+familyName: Cossette Titre
+sources:
+ - CossetteTitre-Regular.ufo
+ - CossetteTitre-Bold.ufo
+buildVariable: false
+includeSourceFixes: true
+```
+
+This is a valid gftools-builder configuration pointing to UFO sources.
+
+## Verification
+
+- **Repository accessible**: Yes - cloned at `upstream_repos/fontc_crater_cache/googlefonts/cossette-fonts/`
+- **Commit exists**: Yes - `ee99cea` is HEAD (and only commit) of the repo
+- **Config exists at commit**: Yes - `sources/config-titre.yaml` is present
+- **Source files present**: Yes - UFO sources for Regular and Bold weights
+- **Font files match**: Binary .ttf files are mapped via `files {}` entries in METADATA.pb
+
+## Confidence Level
+
+**HIGH** - All data is fully documented in the METADATA.pb source block and confirmed by the google/fonts commit message. The upstream repo has only one commit, making verification trivial.
+
+## Open Questions
+
+None.
--- /dev/null
+# Crimson Pro - Investigation Report
+
+## Source Data
+
+| Field | Value |
+|---|---|
+| Family Name | Crimson Pro |
+| Designer | Jacques Le Bailly |
+| Repository URL | https://github.com/Fonthausen/CrimsonPro |
+| Commit | `24e8f7bf59ec45d77c67879ad80d97e5f94c787b` |
+| Config YAML | `sources/config.yaml` (in upstream repo) |
+| Status | complete |
+
+## How URL Found
+
+The repository URL `https://github.com/Fonthausen/CrimsonPro` is referenced in:
+- The font copyright string: "Copyright 2018 The Crimson Pro Project Authors (https://github.com/Fonthausen/CrimsonPro)"
+- The DESCRIPTION.en_us.html file
+- PR #3632 by Aaron Bell mentions his fork at `https://github.com/aaronbell/CrimsonPro` but the canonical upstream is Fonthausen/CrimsonPro
+
+The URL was first added to METADATA.pb source block in commit `cd5db6b6e` by Simon Cozens on 2023-12-14 ("Update upstreams").
+
+## How Commit Determined
+
+The commit hash `24e8f7bf59ec45d77c67879ad80d97e5f94c787b` was added in commit `19cdcec59` ("[Batch 1/4] port info from fontc_crater targets list") by Felipe Sanches, ported from the fontc_crater targets.json file.
+
+This commit is the HEAD of the Fonthausen/CrimsonPro repository, which is a merge commit from 2022-08-30: "Merge pull request #5 from rschiang/normalize-build". It introduces zero changes relative to the previous commit `f21e0a4` (Aaron Bell's merge from 2021-09-01), so the font sources at this commit are identical to those used for the last google/fonts update.
+
+### Font update history in google/fonts:
+1. `cd20fc29b` - crimsonpro: v1.000 added (#1779) - initial addition
+2. `01204e1f0` - crimsonpro: v1.002 added
+3. `5c70a7919` - CrimsonPro v1.003 (stat fix) (#3632) - by Aaron Bell, converted to UFR and rebuilt
+4. `76adaf1d2` - deploy commit (re-added files, no content change)
+
+The last meaningful font update was PR #3632 by Aaron Bell, who rebuilt the fonts after converting to UFR format. His work was merged into the upstream repo as commit `f21e0a4`, and the subsequent commit `24e8f7b` (normalize-build) introduced no source changes.
+
+## Config YAML Status
+
+The `sources/config.yaml` file exists in the upstream repo at the referenced commit. It is a valid gftools-builder configuration specifying:
+- Sources: `CrimsonPro.glyphs`, `CrimsonPro-Italic.glyphs`
+- Axis order: wght, ital
+- Family name: "Crimson Pro"
+- STAT table configuration
+
+No override config.yaml exists in the google/fonts family directory.
+
+## Verification
+
+- **Repository URL**: Verified accessible, correct upstream for this font
+- **Commit hash**: Exists in repo, is HEAD. Sources unchanged since the actual font build commit
+- **Config YAML**: Present at `sources/config.yaml`, valid gftools-builder format
+- **Upstream cache**: Present at `upstream_repos/fontc_crater_cache/Fonthausen/CrimsonPro/`
+
+## Confidence Level
+
+**HIGH** - All data verified. The commit hash points to HEAD which has identical source files to the commit used for the last font update.
+
+## Open Questions
+
+None.
--- /dev/null
+# Crimson Text - Investigation Report
+
+## Source Data
+
+| Field | Value |
+|---|---|
+| Family Name | Crimson Text |
+| Repository URL | https://github.com/googlefonts/Crimson |
+| Commit Hash | 4f1458ae64c6c0d9c5fdfbf5095c7fabe0fa063f |
+| Branch | master |
+| Config YAML | sources/config.yaml |
+| Designer | Sebastian Kosch |
+| License | OFL |
+| Date Added | 2011-01-26 |
+
+## How URL Found
+
+The repository URL `https://github.com/googlefonts/Crimson` is documented in the METADATA.pb `source {}` block. The original Crimson Text project was at `skosch/Crimson`, but was transferred to the googlefonts organization. The copyright strings in the METADATA.pb font entries reference this googlefonts URL.
+
+## How Commit Determined
+
+The commit hash `4f1458ae64c6c0d9c5fdfbf5095c7fabe0fa063f` was set in the METADATA.pb source block when the fonts were last updated in PR #4416 (commit 1ac62d533, authored by Emma Marichal on 2022-03-30).
+
+**Important nuance**: The PR #4416 body text initially referenced an earlier commit `f8b7d63dd515b63aa232857f76af3f9da048f239` ("Merge pull request #3 from emmamarichal/master", 2022-03-24). However, the METADATA.pb source block in the same PR already had commit `4f1458a` ("Merge pull request #4 from emmamarichal/master", 2022-03-25). This indicates the PR was updated after additional work was done upstream (PR #4 added "Some glyphs: ordinals, idotaccent, caron.alt"). The METADATA.pb is the authoritative record, and `4f1458a` is HEAD of the upstream repo, confirming this is the final commit used.
+
+Chronology:
+- 2022-03-24: Upstream commit `f8b7d63` (PR #3 merged - version number change)
+- 2022-03-25: Upstream commit `4f1458a` (PR #4 merged - additional glyphs added) -- **this is the recorded commit**
+- 2022-03-30: google/fonts commit 1ac62d533 (PR #4416 merged)
+
+## Config YAML Status
+
+The config file `sources/config.yaml` exists in the upstream repository at the referenced commit. It contains:
+
+```yaml
+sources:
+ - CrimsonText.glyphs
+ - CrimsonText-Italic.glyphs
+familyName: "Crimson Text"
+buildVariable: false
+autohintTTF: false
+```
+
+This is a valid gftools-builder configuration pointing to Glyphs sources. The `config_yaml` field was added to METADATA.pb in commit 19cdcec59 ("[Batch 1/4] port info from fontc_crater targets list", 2025-03-31).
+
+## Verification
+
+- **Repository accessible**: Yes - cloned at `upstream_repos/fontc_crater_cache/googlefonts/Crimson/`
+- **Commit exists**: Yes - `4f1458a` is HEAD of the upstream repo
+- **Config exists at commit**: Yes - `sources/config.yaml` is present at the referenced commit
+- **Source files present**: Yes - `.glyphs` files for Roman and Italic
+- **Font files match**: Binary .ttf files are mapped via `files {}` entries in METADATA.pb (6 styles: Regular, Italic, SemiBold, SemiBoldItalic, Bold, BoldItalic)
+- **Commit hash is HEAD**: Yes, `4f1458a` is the latest commit in the repo
+
+## Confidence Level
+
+**HIGH** - The commit hash in METADATA.pb was set during the original font update PR (#4416). While the PR body text referenced an earlier commit, the METADATA.pb source block had the final commit from the beginning. The upstream repo confirms this is HEAD, config.yaml exists, and all source data is consistent.
+
+## Open Questions
+
+None.
--- /dev/null
+# Cuprum
+
+**Date investigated**: 2026-02-26
+**Status**: complete
+**Designer**: Jovanny Lemonad
+**METADATA.pb path**: `ofl/cuprum/METADATA.pb`
+
+## Source Data
+
+| Field | Value |
+|-------|-------|
+| Repository URL | https://github.com/alexeiva/cuprum |
+| Commit | `98adc59dc00ca00dbde9eb42a23ace5f924b4f90` |
+| Config YAML | Override in google/fonts (`ofl/cuprum/config.yaml`) |
+| Branch | `master` |
+
+## How the Repository URL Was Found
+
+The repository URL `https://github.com/alexeiva/cuprum` is documented in the METADATA.pb `source { repository_url }` field. It matches the copyright string in the font files ("Copyright 2020 The Cuprum Project Authors (https://github.com/alexeiva/cuprum)"). The gftools-packager commit `df19ee8f7` in google/fonts (PR #2692) also explicitly references this URL: "Cuprum Version 3.000 taken from the upstream repo https://github.com/alexeiva/cuprum".
+
+## How the Commit Hash Was Identified
+
+The commit hash `98adc59dc00ca00dbde9eb42a23ace5f924b4f90` is recorded in METADATA.pb and is directly confirmed by the gftools-packager commit `df19ee8f7` (PR #2692, authored by Marc Foley): "Cuprum Version 3.000 taken from the upstream repo https://github.com/alexeiva/cuprum at commit https://github.com/alexeiva/cuprum/commit/98adc59dc00ca00dbde9eb42a23ace5f924b4f90."
+
+This commit is the HEAD of the `master` branch in the upstream repository. It is a merge commit: "Merge pull request #5 from TypeNetwork/master". While there are more recent commits on other branches (dependabot bumps), the master branch has not moved past this commit.
+
+## How Config YAML Was Resolved
+
+The upstream repository does **not** contain a `config.yaml` or `builder.yaml` file. Instead, an override `config.yaml` exists in the google/fonts family directory at `ofl/cuprum/config.yaml`. This override file references two designspace sources: `sources/Cuprum.designspace` and `sources/Cuprum-Italic.designspace`, with `buildVariable: true`.
+
+Since the override exists in google/fonts, the `config_yaml` field is correctly omitted from the METADATA.pb `source { }` block, as google-fonts-sources will detect the local override automatically.
+
+## Verification
+
+- Commit exists in upstream repo: Yes
+- Commit is HEAD of master: Yes
+- Commit message: "Merge pull request #5 from TypeNetwork/master"
+- Source files at commit: `sources/Cuprum.designspace`, `sources/Cuprum-Italic.designspace`, plus 4 UFO sources
+- Override config.yaml in google/fonts: Yes (`ofl/cuprum/config.yaml`)
+- METADATA.pb files mapping matches repo structure (fonts in `fonts/variable/` and `fonts/ttf/`)
+
+## Confidence
+
+**High**: The repository URL and commit hash are both confirmed by the gftools-packager commit message (PR #2692). The commit exists in the upstream repo and is the HEAD of the master branch. The override config.yaml in google/fonts correctly references the designspace sources present in the repo.
+
+## Open Questions
+
+None. All data is consistent and well-documented.
--- /dev/null
+# Cute Font
+
+**Date investigated**: 2026-02-26
+**Status**: no_upstream_repo
+**Designer**: TypoDesign Lab. Inc
+**METADATA.pb path**: `ofl/cutefont/METADATA.pb`
+
+## Source Data
+
+| Field | Value |
+|-------|-------|
+| Repository URL | None |
+| Commit | None |
+| Config YAML | None |
+| Branch | None |
+
+## How the Repository URL Was Found
+
+No repository URL exists in METADATA.pb. There is no `source { }` block at all. The font was added to Google Fonts as part of a batch of Korean fonts in PR #1459 ("korean families r01: added"), authored by Marc Foley (m4rc1e) on 2018-03-13. The PR body states: "Korean Font binaries have been mastered by Aaron Bell, https://www.sajatypeworks.com".
+
+No upstream GitHub repository has been found for this font. Searches on GitHub for "CuteFont" and "TypoDesign Lab" did not reveal a source repository. The font appears to have been delivered as pre-compiled binary files by TypoDesign Lab. Inc, a Korean foundry, and mastered by Aaron Bell.
+
+The copyright string in the font reads: "COPYRIGHT 2004-2017 by TypoDesign Lab. Inc. All rights reserved. Font designed by TypoDesign Lab. Inc." This does not reference any repository URL.
+
+## How the Commit Hash Was Identified
+
+No commit hash exists because there is no known upstream repository. The binary font file was directly submitted in PR #1459 without reference to a source repository.
+
+## How Config YAML Was Resolved
+
+Not applicable. Without an upstream repository, there is no config.yaml. No override config.yaml exists in the google/fonts family directory (`ofl/cutefont/`).
+
+## Verification
+
+- The font directory contains only: `CuteFont-Regular.ttf`, `DESCRIPTION.en_us.html`, `METADATA.pb`, `OFL.txt`
+- No source block in METADATA.pb
+- Font was added 2018-02-23 (date_added in METADATA.pb)
+- PR #1459 was a batch PR adding multiple Korean fonts (Black And White Picture, Black Han Sans, Cute Font, Do Hyeon, Dokdo, East Sea Dokdo, Gaegu, Gamja Flower, and others)
+- All Korean fonts in this batch were mastered by Aaron Bell from pre-existing font files
+
+## Confidence
+
+**High**: The font clearly has no known upstream repository. The onboarding was done from pre-compiled binaries provided by TypoDesign Lab. Inc, mastered by Aaron Bell. The `no_upstream_repo` status is correct.
+
+## Open Questions
+
+1. Does TypoDesign Lab. Inc maintain source files anywhere (even privately) that could be made available as an open-source upstream repo? This would require contacting the foundry.
--- /dev/null
+# Cutive
+
+**Date investigated**: 2026-02-26
+**Status**: complete
+**Designer**: Vernon Adams
+**METADATA.pb path**: `ofl/cutive/METADATA.pb`
+
+## Source Data
+
+| Field | Value |
+|-------|-------|
+| Repository URL | https://github.com/googlefonts/CutiveFont |
+| Commit | `d97e7cb29296a2c091568d01e3394ae87111bd39` |
+| Config YAML | `sources/config.yaml` |
+| Branch | `master` |
+
+## How the Repository URL Was Found
+
+The repository URL was already present in the METADATA.pb `source { repository_url }` field, set to `https://github.com/googlefonts/CutiveFont`. This matches the copyright string in the font file ("Copyright 2012 The Cutive Project Authors (https://github.com/googlefonts/CutiveFont), with Reserved Font Names \"Cutive\""). The google/fonts commit `46bc8761f` (2024-08-01) by Emma Marichal explicitly states: "Taken from the upstream repo https://github.com/googlefonts/CutiveFont".
+
+## How the Commit Hash Was Identified
+
+The commit `d97e7cb29296a2c091568d01e3394ae87111bd39` is referenced directly in the google/fonts commit `46bc8761f` (2024-08-01, "Cutive: Version 1.110; ttfautohint (v1.8.4.7-5d5b) added"), which states: "Taken from the upstream repo https://github.com/googlefonts/CutiveFont at commit https://github.com/googlefonts/CutiveFont/commit/d97e7cb29296a2c091568d01e3394ae87111bd39."
+
+This is the most recent font binary update for Cutive. A previous update at commit `0f79e19d9` (2024-06-07, "Version 1.100") referenced a different upstream commit (`2d3d48d9f1b915c840abbd1be6a97324f1f16974`), but the v1.110 update supersedes it.
+
+The upstream repository is a single-commit repo: `d97e7cb` ("bumped version") is both the only commit and HEAD.
+
+## How Config YAML Was Resolved
+
+The file `sources/config.yaml` exists in the upstream repository at the recorded commit. It contains:
+
+```yaml
+sources:
+ - Cutive.glyphs
+familyName: Cutive
+buildVariable: false
+```
+
+This was added to METADATA.pb via the batch commit `19cdcec59` ("[Batch 1/4] port info from fontc_crater targets list", 2025-03-31), porting data from fontc_crater's target.json. No override config.yaml exists in the google/fonts family directory (`ofl/cutive/`).
+
+## Verification
+
+- Commit exists in upstream repo: Yes (it is the only commit / HEAD)
+- Commit message: "bumped version"
+- Source files at commit: `sources/Cutive.glyphs`, `sources/config.yaml`
+- Font binary in METADATA.pb files block: `fonts/ttf/Cutive-Regular.ttf` maps to `Cutive-Regular.ttf`
+
+## Confidence
+
+**High**: The commit hash is explicitly referenced in the google/fonts commit message for the most recent font update. The upstream repo has only one commit, which matches. The config.yaml exists and is valid. All data is fully consistent.
+
+## Open Questions
+
+None.
--- /dev/null
+# Cutive Mono
+
+**Date investigated**: 2026-02-26
+**Status**: complete
+**Designer**: Vernon Adams
+**METADATA.pb path**: `ofl/cutivemono/METADATA.pb`
+
+## Source Data
+
+| Field | Value |
+|-------|-------|
+| Repository URL | https://github.com/googlefonts/cutivemono |
+| Commit | `4422d783b81be0fcec82ef3610eac94784d989c1` |
+| Config YAML | `sources/config.yaml` |
+| Branch | `main` |
+
+## How the Repository URL Was Found
+
+The repository URL was already present in the METADATA.pb `source { repository_url }` field, set to `https://github.com/googlefonts/cutivemono`. This matches the copyright string in the font file ("Copyright 2012 The Cutive Project Authors (https://github.com/googlefonts/cutivemono)"). The google/fonts commit `7c38f10e1` (2024-05-08) by Emma Marichal explicitly states: "Taken from the upstream repo https://github.com/googlefonts/cutivemono". The URL was initially added to METADATA.pb by Simon Cozens in commit `c8f729cbd` ("Add more upstreams (c,d)", 2024-01-14).
+
+## How the Commit Hash Was Identified
+
+The commit `4422d783b81be0fcec82ef3610eac94784d989c1` is referenced directly in the google/fonts commit `7c38f10e1` (2024-05-08, "Cutive Mono: Version 1.110; ttfautohint (v1.8.4.7-5d5b) added"), which states: "Taken from the upstream repo https://github.com/googlefonts/cutivemono at commit https://github.com/googlefonts/cutivemono/commit/4422d783b81be0fcec82ef3610eac94784d989c1."
+
+This is the most recent font binary update for Cutive Mono. The upstream repository has only this single commit (`4422d78`, "fix ldot"), which is HEAD.
+
+## How Config YAML Was Resolved
+
+The file `sources/config.yaml` exists in the upstream repository at the recorded commit. It contains:
+
+```yaml
+sources:
+ - CutiveMono.glyphs
+familyName: Cutive Mono
+buildVariable: false
+```
+
+This was added to METADATA.pb via the batch commit `19cdcec59` ("[Batch 1/4] port info from fontc_crater targets list", 2025-03-31), porting data from fontc_crater's target.json. No override config.yaml exists in the google/fonts family directory (`ofl/cutivemono/`).
+
+## Verification
+
+- Commit exists in upstream repo: Yes (it is the only commit / HEAD)
+- Commit message: "fix ldot"
+- Source files at commit: `sources/CutiveMono.glyphs`, `sources/config.yaml`
+- Font binary in METADATA.pb files block: `fonts/ttf/CutiveMono-Regular.ttf` maps to `CutiveMono-Regular.ttf`
+
+## Confidence
+
+**High**: The commit hash is explicitly referenced in the google/fonts commit message for the most recent font update. The upstream repo has only one commit, which matches. The config.yaml exists and is valid. All data is fully consistent.
+
+## Open Questions
+
+None.
--- /dev/null
+# Damion
+
+**Date investigated**: 2026-02-26
+**Status**: complete
+**Designer**: Vernon Adams
+**METADATA.pb path**: `ofl/damion/METADATA.pb`
+
+## Source Data
+
+| Field | Value |
+|-------|-------|
+| Repository URL | https://github.com/googlefonts/damionFont |
+| Commit | `6408c983f707a0bd5129eecf74a834146fec2983` |
+| Config YAML | `sources/config.yaml` |
+| Branch | `master` |
+
+## How the Repository URL Was Found
+
+The repository URL was already present in the METADATA.pb `source { repository_url }` field, set to `https://github.com/googlefonts/damionFont`. This matches the copyright string in the font file ("Copyright 2014 The Damion Project Authors (https://github.com/googlefonts/damionFont)"). The google/fonts commit `8b3003069` (2024-04-19) by Emma Marichal explicitly states: "Taken from the upstream repo https://github.com/googlefonts/damionFont".
+
+## How the Commit Hash Was Identified
+
+The commit `6408c983f707a0bd5129eecf74a834146fec2983` is referenced directly in the google/fonts commit `8b3003069` (2024-04-19, "Damion: Version 1.100; ttfautohint (v1.8.4.7-5d5b) added"), which states: "Taken from the upstream repo https://github.com/googlefonts/damionFont at commit https://github.com/googlefonts/damionFont/commit/6408c983f707a0bd5129eecf74a834146fec2983."
+
+This is the most recent font binary update for Damion. The upstream repository has only this single commit (`6408c98`, "last fixes in the sources"), which is HEAD.
+
+## How Config YAML Was Resolved
+
+The file `sources/config.yaml` exists in the upstream repository at the recorded commit. It contains:
+
+```yaml
+sources:
+ - Damion.glyphs
+familyName: Damion
+buildVariable: false
+```
+
+This was added to METADATA.pb via the batch commit `19cdcec59` ("[Batch 1/4] port info from fontc_crater targets list", 2025-03-31), porting data from fontc_crater's target.json. No override config.yaml exists in the google/fonts family directory (`ofl/damion/`).
+
+## Verification
+
+- Commit exists in upstream repo: Yes (it is the only commit / HEAD)
+- Commit message: "last fixes in the sources"
+- Source files at commit: `sources/Damion.glyphs`, `sources/config.yaml`
+- Font binary in METADATA.pb files block: `fonts/ttf/Damion-Regular.ttf` maps to `Damion-Regular.ttf`
+
+## Confidence
+
+**High**: The commit hash is explicitly referenced in the google/fonts commit message for the most recent font update. The upstream repo has only one commit, which matches. The config.yaml exists and is valid. All data is fully consistent.
+
+## Open Questions
+
+None.
--- /dev/null
+# Dancing Script
+
+**Date investigated**: 2026-02-26
+**Status**: complete
+**Designer**: Impallari Type
+**METADATA.pb path**: `ofl/dancingscript/METADATA.pb`
+
+## Source Data
+
+| Field | Value |
+|-------|-------|
+| Repository URL | https://github.com/googlefonts/DancingScript |
+| Commit | `291f87c05206179b6bfd53735a5638b5cc84e3b3` |
+| Config YAML | `sources/config.yaml` |
+| Branch | `master` |
+
+## How the Repository URL Was Found
+
+The repository URL was already present in the METADATA.pb `source { repository_url }` field, set to `https://github.com/googlefonts/DancingScript`. The copyright string references this URL. The font was originally maintained at `https://github.com/aaronbell/DancingScript` and later transferred/forked to the googlefonts organization. The URL was added to METADATA.pb by commit `f7455d788` ("Populate source.repository_url") in google/fonts.
+
+## How the Commit Hash Was Identified
+
+The commit `291f87c05206179b6bfd53735a5638b5cc84e3b3` was added via the batch commit `19cdcec59` ("[Batch 1/4] port info from fontc_crater targets list", 2025-03-31), porting data from fontc_crater's target.json.
+
+**Background on the font update history**: The most recent font binary update was PR #3788 (commit `f8dc91f6f`, 2021-09-30, "Dancing Script: Version 2.001 added") by Aaron Bell. The PR body states the font was "taken from the upstream repo https://github.com/aaronbell/DancingScript at commit https://github.com/aaronbell/DancingScript/commit/d1b9b8b369e284006d1d0e03464693e6c895fba2."
+
+The `googlefonts/DancingScript` repository has a single merge commit (`291f87c`, "Merge pull request #9 from aaronbell/master") which is HEAD. This merge commit incorporates the aaronbell fork content. Since the METADATA.pb points to the googlefonts repo (not the aaronbell fork), using `291f87c` as the commit is appropriate -- it represents the canonical state of the font in the googlefonts organization's repository.
+
+The upstream repo is a shallow clone with only this single commit visible. The original aaronbell commit `d1b9b8b3` is not present in the local clone (it was in the aaronbell fork history).
+
+## How Config YAML Was Resolved
+
+The file `sources/config.yaml` exists in the upstream repository at the recorded commit. It contains gftools-builder configuration referencing `DancingScript.designspace` with a weight axis and STAT table definitions. This was added to METADATA.pb via the same batch commit `19cdcec59`. No override config.yaml exists in the google/fonts family directory (`ofl/dancingscript/`).
+
+## Verification
+
+- Commit exists in upstream repo: Yes (it is the only commit / HEAD)
+- Commit message: "Merge pull request #9 from aaronbell/master"
+- Source files at commit: `sources/DancingScript.designspace`, `sources/config.yaml`, legacy sources in `legacy/`
+- Font binary: Variable font `DancingScript[wght].ttf` with weight axis (400-700)
+- Variable font confirmed: `DancingScript[wght].ttf` in both upstream and google/fonts
+
+## Confidence
+
+**High**: The repository URL and commit hash are consistent. The googlefonts/DancingScript repo is the canonical home for this font. The commit `291f87c` is the only commit in the repo and encompasses all the work from aaronbell's fork. The config.yaml is present and valid. The font was originally onboarded from aaronbell's fork but the canonical repo has been moved to googlefonts.
+
+## Open Questions
+
+1. The local clone of googlefonts/DancingScript appears to be shallow (single commit). A full clone might reveal additional history, but since `291f87c` is HEAD and the only commit on master, this is not a concern for verification purposes.
--- /dev/null
+# Danfo
+
+**Date investigated**: 2026-02-26
+**Status**: complete
+**Designer**: Afrotype, Seyi Olusanya, Eyiyemi Adegbite, David Udoh, Mirko Velimirovic
+**METADATA.pb path**: `ofl/danfo/METADATA.pb`
+
+## Source Data
+
+| Field | Value |
+|-------|-------|
+| Repository URL | https://github.com/Afrotype/danfo |
+| Commit | `a66fc9ded8f42ad2d39b91c9cd8a1960737ad02a` |
+| Config YAML | `sources/config.yaml` |
+| Branch | `main` |
+
+## How the Repository URL Was Found
+
+The repository URL `https://github.com/Afrotype/danfo` is documented in the METADATA.pb `source { repository_url }` field. It matches the copyright string in the font ("Copyright 2024 The Tac Project Authors (https://github.com/Afrotype/Danfo)"). The gftools-packager commit `d2b934888` in google/fonts confirms this: "Danfo Version 1.000 taken from the upstream repo https://github.com/Afrotype/danfo".
+
+Note: the copyright references the repo URL with capital "D" (Danfo) but the actual METADATA.pb uses lowercase (danfo). Both work on GitHub as repository names are case-insensitive.
+
+## How the Commit Hash Was Identified
+
+The commit hash `a66fc9ded8f42ad2d39b91c9cd8a1960737ad02a` is recorded in METADATA.pb and confirmed by the gftools-packager commit `d2b934888`: "Danfo Version 1.000 taken from the upstream repo https://github.com/Afrotype/danfo at commit https://github.com/Afrotype/danfo/commit/a66fc9ded8f42ad2d39b91c9cd8a1960737ad02a."
+
+This commit is the HEAD of the `main` branch in the upstream repository (commit message: "language fixes"). No additional commits have been made to the repo since onboarding.
+
+## How Config YAML Was Resolved
+
+The upstream repository contains `sources/config.yaml` at the recorded commit. The config file references `Danfo.glyphs` as the source, with axis order `ELSH` (Element Shape), `familyName: Danfo`, and `buildVariable: True`. This path is correctly recorded in the METADATA.pb `config_yaml` field. No override config.yaml exists in the google/fonts family directory.
+
+## Verification
+
+- Commit exists in upstream repo: Yes
+- Commit is HEAD of main: Yes
+- Commit message: "language fixes"
+- Source files at commit: `sources/Danfo.glyphs`, `sources/config.yaml`
+- Config YAML at commit: `sources/config.yaml` (valid gftools-builder config)
+- METADATA.pb files mapping: `fonts/variable/Danfo[ELSH].ttf` -> `Danfo[ELSH].ttf`
+- Minisite URL: https://www.afrotype.com/danfo
+
+## Confidence
+
+**High**: All data is confirmed by the gftools-packager commit message. The commit exists and is the HEAD of the main branch. The config.yaml is present in the upstream repo at the correct path. The font was recently added (2024-03-15).
+
+## Open Questions
+
+None. All data is consistent and well-documented.
--- /dev/null
+# Dangrek
+
+**Date investigated**: 2026-02-26
+**Status**: complete
+**Designer**: Danh Hong
+**METADATA.pb path**: `ofl/dangrek/METADATA.pb`
+
+## Source Data
+
+| Field | Value |
+|-------|-------|
+| Repository URL | https://github.com/danhhong/Dangrek |
+| Commit | `a8da8cf02ec7e96f45716b0052a027007bb042c2` |
+| Config YAML | `Source/builder.yaml` |
+| Branch | `master` |
+
+## How the Repository URL Was Found
+
+The repository URL `https://github.com/danhhong/Dangrek` is documented in the METADATA.pb `source { repository_url }` field. It matches the copyright string in the font ("Copyright 2020 The Dangrek Project Authors (https://github.com/danhhong/Dangrek)"). The gftools-packager commit `f587dcbf8` in google/fonts (PR #3507) also references this URL: "Dangrek Version 8.000; ttfautohint (v1.8.3) taken from the upstream repo https://github.com/danhhong/Dangrek.git".
+
+## How the Commit Hash Was Identified
+
+The commit hash `a8da8cf02ec7e96f45716b0052a027007bb042c2` is recorded in METADATA.pb and confirmed by the gftools-packager commit `f587dcbf8` (PR #3507, authored by Yanone): "Dangrek Version 8.000; ttfautohint (v1.8.3) taken from the upstream repo https://github.com/danhhong/Dangrek.git at commit https://github.com/danhhong/Dangrek/commit/a8da8cf02ec7e96f45716b0052a027007bb042c2."
+
+This commit is the HEAD of the `master` branch in the upstream repository. It is a merge commit: "Merge pull request #1 from yanone/master". No additional commits have been made since.
+
+Note: After the initial onboarding (PR #3507), there was a subsequent batch update in commit `4f5dbdb58` ("Bumped to 8.002 (urgent glyph definition issues)" PR #4152) that modified `Dangrek-Regular.ttf`. This was a batch fix for Khmer fonts addressing "urgent glyph definition issues" and did not come from a new upstream commit -- the binary was likely rebuilt from the same source.
+
+## How Config YAML Was Resolved
+
+The upstream repository contains `Source/builder.yaml` at the recorded commit. The builder config references `Dangrek.glyphs` as the source with `outputDir: "../Release"`, `buildStatic: true`, `buildVariable: false`. This path is correctly recorded in the METADATA.pb `config_yaml` field as `Source/builder.yaml`. No override config.yaml exists in the google/fonts family directory.
+
+## Verification
+
+- Commit exists in upstream repo: Yes
+- Commit is HEAD of master: Yes
+- Commit message: "Merge pull request #1 from yanone/master"
+- Source files at commit: `Source/Dangrek.glyphs`, `Source/builder.yaml`
+- Config YAML at commit: `Source/builder.yaml` (valid gftools-builder config)
+- METADATA.pb files mapping: `Release/ttf/Dangrek-Regular.ttf` -> `Dangrek-Regular.ttf`
+- Font was originally added in early google/fonts history (2011-03-02), then updated to V8 via PR #3507
+
+## Confidence
+
+**High**: The repository URL and commit hash are both confirmed by the gftools-packager commit message (PR #3507). The commit exists and is the HEAD of the master branch. The builder.yaml is present at the correct path in the upstream repo.
+
+## Open Questions
+
+None. All data is consistent and well-documented.
--- /dev/null
+# Darker Grotesque
+
+**Date investigated**: 2026-02-26
+**Status**: complete
+**Designer**: Gabriel Lam, ViệtAnh Nguyễn
+**METADATA.pb path**: `ofl/darkergrotesque/METADATA.pb`
+
+## Source Data
+
+| Field | Value |
+|-------|-------|
+| Repository URL | https://github.com/bettergui/DarkerGrotesque |
+| Commit | `a5c3584b44ab3a7d272565662139ee07bb72e8e8` |
+| Config YAML | `sources/config.yaml` |
+| Branch | `master` |
+
+## How the Repository URL Was Found
+
+The repository URL `https://github.com/bettergui/DarkerGrotesque` is documented in the METADATA.pb `source { repository_url }` field. It matches the copyright string in the font ("Copyright 2019 The Darker Grotesque Project Authors (https://github.com/bettergui/DarkerGrotesque)"). Multiple onboarding commits in google/fonts reference this URL.
+
+## How the Commit Hash Was Identified
+
+The commit hash `a5c3584b44ab3a7d272565662139ee07bb72e8e8` is recorded in METADATA.pb and confirmed by the gftools-packager commit `661c8bdc6` (authored by Emma Marichal, 2023-04-27): "Darker Grotesque Version 1.000;gftools[0.9.28] taken from the upstream repo https://github.com/bettergui/DarkerGrotesque at commit https://github.com/bettergui/DarkerGrotesque/commit/a5c3584b44ab3a7d272565662139ee07bb72e8e8."
+
+**Important history**: Darker Grotesque was originally added to Google Fonts with static fonts from a different commit:
+- **Original onboarding** (commits `b77c4d9b6` and `c4ab99f33`, 2019): "Taken from the upstream repo https://github.com/bettergui/DarkerGrotesque at commit https://github.com/bettergui/DarkerGrotesque/commit/f9478bb90aeecf97cd4bc4138a12586d835f7593" -- this was the static font version.
+- **Variable font re-packaging** (commit `661c8bdc6`, 2023): Emma Marichal re-packaged the font as a variable font from commit `a5c3584b`, which replaced the 7 static TTF files with a single variable `DarkerGrotesque[wght].ttf`.
+
+The current commit `a5c3584b` is the HEAD of the `master` branch (commit message: "Merge pull request #8 from emmamarichal/master"). This is the correct and most recent onboarding commit.
+
+## How Config YAML Was Resolved
+
+The upstream repository contains `sources/config.yaml` at the recorded commit. The config file references `DarkerGrotesque.glyphs` as the source, with axis order `wght` and `familyName: "Darker Grotesque"`. This path is correctly recorded in the METADATA.pb `config_yaml` field. No override config.yaml exists in the google/fonts family directory.
+
+## Verification
+
+- Commit exists in upstream repo: Yes
+- Commit is HEAD of master: Yes (and only commit in repo, as it's a single-commit repo)
+- Commit message: "Merge pull request #8 from emmamarichal/master"
+- Source files at commit: `sources/DarkerGrotesque.glyphs`, `sources/config.yaml`
+- Config YAML at commit: `sources/config.yaml` (valid gftools-builder config with STAT table)
+- METADATA.pb files mapping: `fonts/variable/DarkerGrotesque[wght].ttf` -> `DarkerGrotesque[wght].ttf`
+- Weight range: 300-900
+
+## Confidence
+
+**High**: The repository URL and commit hash are confirmed by the gftools-packager commit message from the variable font re-packaging (2023). The commit exists and is the HEAD of the master branch. The config.yaml is present in the upstream repo at the correct path. The transition from static to variable fonts is well-documented.
+
+## Open Questions
+
+None. All data is consistent and well-documented.
--- /dev/null
+# Darumadrop One - Investigation Report
+
+## Source Data
+
+| Field | Value |
+|-------|-------|
+| Family Name | Darumadrop One |
+| Designer | Maniackers Design |
+| Repository URL | https://github.com/ManiackersDesign/darumadrop |
+| Commit Hash | `ddbe82834bdab1ecc24adad09cc122d6e8678a81` |
+| Branch | master |
+| Config YAML | Override in google/fonts (no config_yaml field needed) |
+| Status | complete |
+| Date Added | 2020-12-14 |
+
+## How URL Found
+
+The repository URL `https://github.com/ManiackersDesign/darumadrop` is documented in the copyright field of METADATA.pb and was present from the original onboarding PR #2864. The commit message in google/fonts explicitly states: "Daruma Drop One Version 1.000 taken from the upstream repo https://github.com/ManiackersDesign/darumadrop.git".
+
+## How Commit Determined
+
+The font has a complex onboarding history with multiple commit references:
+
+1. **PR #2864 body** references commit `35ecca7fc3a038ea3f910e556a294edb0ddbcf61` (Aaron Bell's "Create OFL.txt" commit)
+2. **Merged commit message** (140a3943d) references commit `9d5188a76086b0f011830dc191ee712c15a29d40` (Aaron Bell's "Updating copyright string" commit)
+3. **Current METADATA.pb** uses commit `ddbe82834bdab1ecc24adad09cc122d6e8678a81` (the HEAD merge commit)
+
+The discrepancy is explained by the renaming. The original font was "Daruma Drop One" (with spaces), onboarded at commit `9d5188a` or `35ecca7`. Later, PR #4177 renamed it to "Darumadrop One" (no space). This renaming was done by Yanone (Jan Gerner) both in the upstream repo and in google/fonts. The upstream rename was merged as commit `ddbe828` (Merge pull request #4 from yanone/master - "Darumadrop One ready for Google Fonts").
+
+The current METADATA.pb correctly points to `ddbe828` because the renamed font binary (`DarumadropOne-Regular.ttf`) was taken from that commit via the `files` mapping: `source_file: "fonts/ttf/DarumadropOne-Regular.ttf"`.
+
+## Config YAML Status
+
+- **No config.yaml in upstream repo**: The upstream does not have a config.yaml file
+- **Override config.yaml exists in google/fonts**: `/ofl/darumadropone/config.yaml` with content:
+ ```yaml
+ buildVariable: false
+ sources:
+ - source/DarumadropOne.glyphs
+ ```
+- The source file `source/DarumadropOne.glyphs` exists at commit `ddbe828`
+- Since an override config exists, the `config_yaml` field is correctly omitted from the METADATA.pb source block
+
+## Verification
+
+- Repository URL is valid and accessible: https://github.com/ManiackersDesign/darumadrop
+- Commit `ddbe828` exists in the upstream repo and is HEAD (master)
+- The METADATA.pb `files` mapping correctly maps `fonts/ttf/DarumadropOne-Regular.ttf` to `DarumadropOne-Regular.ttf`
+- The upstream repo is cached at `upstream_repos/fontc_crater_cache/ManiackersDesign/darumadrop/`
+
+## Confidence Level
+
+**HIGH** - All data is well-documented. The commit hash is correct for the renamed version. The override config.yaml correctly points to the .glyphs source.
+
+## Open Questions
+
+None. The investigation is complete.
--- /dev/null
+# Investigation Report: Datatype
+
+## Summary
+
+Datatype is a variable font (with `wdth` and `wght` axes) designed by Frank Tisellano that turns text into charts. It was very recently added to Google Fonts on 2026-02-25 via PR #10267, authored by Emma Marichal. The upstream repository at `franktisellano/datatype` already has a complete source block in METADATA.pb with commit hash and repository URL. However, the font uses a custom Python-based build system rather than gftools-builder, so there is no config.yaml and none can be created.
+
+## Key Findings
+
+| Field | Value |
+|---------------------|----------------------------------------------------------|
+| Family Name | Datatype |
+| Designer | Frank Tisellano |
+| License | OFL |
+| Date Added | 2026-02-25 |
+| Repository URL | https://github.com/franktisellano/datatype |
+| Commit Hash | 1a17d767ba7fecd54d47ec11b2f7ed644a31513d |
+| Branch | main |
+| Config YAML | None (custom Python build system, not gftools-builder) |
+| Source Types | Custom Python (sources/build.py, sources/font_builder.py)|
+| Status | no_config_possible |
+| Confidence | HIGH |
+
+## Investigation Details
+
+### METADATA.pb Analysis
+
+The METADATA.pb at `ofl/datatype/METADATA.pb` already has a **complete source block**:
+
+```
+source {
+ repository_url: "https://github.com/franktisellano/datatype"
+ commit: "1a17d767ba7fecd54d47ec11b2f7ed644a31513d"
+ files {
+ source_file: "OFL.txt"
+ dest_file: "OFL.txt"
+ }
+ files {
+ source_file: "fonts/variable/Datatype[wdth,wght].ttf"
+ dest_file: "Datatype[wdth,wght].ttf"
+ }
+ branch: "main"
+}
+```
+
+The font file is a variable font: `Datatype[wdth,wght].ttf` with width axis (50-150) and weight axis (100-900).
+
+### Git History in google/fonts
+
+Four commits touch this family:
+1. `2a727e489` (2026-02-25, Emma Marichal): "Datatype: Version 1.202 added" -- initial onboarding
+2. `2ed24956d`: "Remove IBM Plex copyright notice from OFL.txt"
+3. `956f0091b`: "Add font information and contribution details to ARTICLE.en_us.html"
+4. `91bf91951`: "Add sample_text section to METADATA.pb"
+
+These were all merged via PR #10267 on 2026-02-26.
+
+### Upstream Repository Verification
+
+The repository `https://github.com/franktisellano/datatype` was created on 2026-02-15. The referenced commit `1a17d767ba7fecd54d47ec11b2f7ed644a31513d` was authored on 2026-02-23 with the message "gives well-deserved thanks to Emma and Dave for their guidance and support". This commit predates the PR merge on 2026-02-26, which is consistent.
+
+The commit message in google/fonts explicitly states: "Taken from the upstream repo https://github.com/franktisellano/datatype at commit https://github.com/franktisellano/datatype/commit/1a17d767ba7fecd54d47ec11b2f7ed644a31513d."
+
+### Source Files and Build System
+
+The upstream repo does **not** use gftools-builder. Instead, it has a custom Python-based build system:
+
+- `sources/build.py` -- Main build script that orchestrates font generation
+- `sources/font_builder.py` -- Font building utilities
+- `sources/config.py` -- Configuration for family name, axes, masters, instances
+- `sources/glyphs/` -- Python modules that programmatically draw glyphs (bar charts, sparklines, pie charts)
+- `sources/glyphs/base_imported.py` -- Imports base glyphs from IBM Plex Mono
+- `Makefile` -- Runs `python sources/build.py`
+
+The font is built programmatically rather than designed in a traditional font editor. There are no `.glyphs`, `.ufo`, or `.designspace` files. The build is invoked via `make build` which runs `python sources/build.py`.
+
+No `config.yaml` exists in the upstream repo, and an override config.yaml cannot be created because there are no gftools-builder compatible source files.
+
+The repo is **not cached locally** at `fontc_crater_cache/`. Due to disk space constraints (98%), no clone was performed.
+
+### Onboarding Commit Verification
+
+The commit hash `1a17d767ba7fecd54d47ec11b2f7ed644a31513d` is verified:
+- It exists in the upstream repo on the `main` branch
+- It was authored on 2026-02-23, three days before the PR merge on 2026-02-26
+- The PR commit message explicitly references this exact commit
+- The files entry references `fonts/variable/Datatype[wdth,wght].ttf` which is present at that commit
+
+## Conclusion
+
+**Status: no_config_possible**
+
+The source block in METADATA.pb is already complete and correct. The font uses a custom Python build system (not gftools-builder), so no config.yaml is applicable. No changes are needed for this family.
+
+### Current METADATA.pb source block (already correct)
+
+```
+source {
+ repository_url: "https://github.com/franktisellano/datatype"
+ commit: "1a17d767ba7fecd54d47ec11b2f7ed644a31513d"
+ files {
+ source_file: "OFL.txt"
+ dest_file: "OFL.txt"
+ }
+ files {
+ source_file: "fonts/variable/Datatype[wdth,wght].ttf"
+ dest_file: "Datatype[wdth,wght].ttf"
+ }
+ branch: "main"
+}
+```
--- /dev/null
+# David Libre - Investigation Report
+
+## Source Data
+
+| Field | Value |
+|-------|-------|
+| Family Name | David Libre |
+| Designer | Monotype Imaging Inc., SIL International, Meir Sadan |
+| Repository URL | https://github.com/meirsadan/david-libre |
+| Commit Hash | `15496c1be77e35f3fa3d0df14a2c2c6f9adfd297` |
+| Branch | master |
+| Config YAML | `sources/config.yaml` (in upstream) |
+| Status | complete |
+| Date Added | 2021-07-23 |
+
+## How URL Found
+
+The repository URL `https://github.com/meirsadan/david-libre` is documented in the copyright field of the font files and in the METADATA.pb. It was present from the original onboarding PR #3595 (authored by Rosalie Wagner) and confirmed by the gftools-packager update commit `0841b9aa8`.
+
+## How Commit Determined
+
+The gftools-packager commit `0841b9aa8` (Marc Foley, Feb 21 2024) explicitly states: "David Libre Version 1.100; ttfautohint (v1.8.4.7-5d5b) taken from the upstream repo https://github.com/meirsadan/david-libre at commit https://github.com/meirsadan/david-libre/commit/15496c1be77e35f3fa3d0df14a2c2c6f9adfd297."
+
+This commit (`15496c1`) is the HEAD of the upstream repository (a merge of PR #25 from emmamarichal/master titled "Small fixes"). The font was rebuilt from source by the packager using this commit.
+
+### Onboarding History
+
+1. **PR #3595 (Jul 2021)** - Rosalie Wagner added David Libre from the Google Fonts API ZIP file (not from a specific upstream commit)
+2. **Commit 0841b9aa8 (Feb 2024)** - Marc Foley rebuilt the font from upstream using gftools-packager at commit `15496c1`
+
+The current font binaries in google/fonts are from the Feb 2024 packager rebuild.
+
+## Config YAML Status
+
+- **config.yaml exists in upstream**: `sources/config.yaml` with content:
+ ```yaml
+ sources:
+ - DavidLibre.glyphs
+ familyName: David Libre
+ buildVariable: False
+ buildOTF: False
+ checkCompatibility: False
+ ```
+- The `config_yaml` field in METADATA.pb is correctly set to `sources/config.yaml`
+- No override config.yaml in google/fonts
+
+## Verification
+
+- Repository URL is valid and accessible: https://github.com/meirsadan/david-libre
+- Commit `15496c1` exists in the upstream repo and is HEAD (master)
+- The METADATA.pb `files` mapping correctly maps font files from `fonts/ttf/` to the family directory
+- The upstream repo is cached at `upstream_repos/fontc_crater_cache/meirsadan/david-libre/`
+- The `sources/config.yaml` file exists in the upstream repo at commit `15496c1`
+
+## Confidence Level
+
+**HIGH** - The gftools-packager commit explicitly documents the upstream commit used for the most recent build. All fields are verified.
+
+## Open Questions
+
+None. The investigation is complete.
--- /dev/null
+# Investigation: Decovar Alpha
+
+## Summary
+
+| Field | Value |
+|-------|-------|
+| Family Name | Decovar Alpha |
+| Slug | decovar-alpha |
+| License Dir | ofl |
+| Repository URL | https://github.com/TypeNetwork/fb-Decovar |
+| Commit Hash | unknown |
+| Config YAML | unknown |
+| Status | missing_commit |
+| Confidence | MEDIUM |
+
+## Source Data (METADATA.pb)
+
+```
+No source block
+```
+
+(No METADATA.pb exists for this family. It is an Early Access font.)
+
+## Investigation
+
+The family directory is at `ofl/decovaralpha/` and contains:
+- `DecovarAlpha-VF.ttf`
+- `DESCRIPTION.en_us.html`
+- `EARLY_ACCESS.category` (value: "Sans Serif")
+- `OFL.txt`
+
+**No METADATA.pb exists.** This is an Early Access font that predates the modern METADATA.pb onboarding process.
+
+### Git History
+
+```
+bc4d03ae3 2017-08-30 decovaralpha/Decovar-VF.ttf -> DecovarAlpha-VF.ttf
+3231ca2f6 2017-08-30 decovar -> decovaralpha + update to latest version (#1183)
+fda8d1f9c 2017-08-14 Add Decovar to Early Access (#656)
+```
+
+- **PR #656** (commit `fda8d1f9c`, 2017-08-14, Dave Crossland): Initial onboarding as "decovar" — added `Decovar-VF.ttf`, `DESCRIPTION.en_us.html`, `EARLY_ACCESS.category`, and `OFL.txt` to `ofl/decovar/`.
+- **PR #1183** (commit `3231ca2f6`, 2017-08-30, Dave Crossland): Renamed directory from `ofl/decovar/` to `ofl/decovaralpha/` and updated the TTF to a newer version (295,396 bytes → 295,460 bytes). The PR title is "decovar -> decovaralpha + update to latest version".
+- **commit `bc4d03ae3`** (2017-08-30, Dave Crossland): Renamed the font file from `Decovar-VF.ttf` to `DecovarAlpha-VF.ttf`.
+
+### Upstream Repository
+
+The `DESCRIPTION.en_us.html` links directly to the upstream repository:
+> "To learn more about this project, visit [github.com/TypeNetwork/fb-Decovar](https://github.com/TypeNetwork/fb-Decovar)"
+
+The `OFL.txt` copyright line reads:
+> "Copyright 2016 The Decovar Project Authors (info@fontbureau.com)"
+
+The upstream is **https://github.com/TypeNetwork/fb-Decovar** (originally a Font Bureau project by David Berlow, now maintained under TypeNetwork).
+
+### Upstream Repo Not in Cache
+
+The repository `TypeNetwork/fb-Decovar` is **not** cloned in `upstream_repos/fontc_crater_cache/TypeNetwork/` (only `Arimo` and `Assistant` are cached there).
+
+### No config.yaml Known
+
+Without access to the upstream repo, the config.yaml status cannot be confirmed. Given the early nature of this project (2017) and that it is a variable font with likely `.glyphs` or `.designspace` sources, a config.yaml may or may not exist.
+
+### Exact Commit Unknown
+
+The PR #1183 commit message does not include an upstream commit hash. The exact commit in `TypeNetwork/fb-Decovar` that corresponds to the August 2017 update is unknown without inspecting the upstream repository.
+
+## Conclusion
+
+This Early Access font has a clearly identified upstream repository at `https://github.com/TypeNetwork/fb-Decovar`. A METADATA.pb with a source block needs to be created, referencing this upstream. The exact commit hash used for the August 2017 update needs to be determined by inspecting the upstream repository history around that date. Once the upstream repo is cloned and the correct commit identified, a config.yaml path (or override) can be determined.
+
+**Action needed**: Clone `TypeNetwork/fb-Decovar` to the fontc_crater_cache (when disk space allows), identify the commit from around 2017-08-30, check for config.yaml, and create a METADATA.pb with source block.
--- /dev/null
+# Dekko - Investigation Report
+
+## Source Data
+
+| Field | Value |
+|-------|-------|
+| Family Name | Dekko |
+| Designer | Sorkin Type |
+| Repository URL | https://github.com/EbenSorkin/Dekko |
+| Commit Hash | `4887c14997f1158a2a122d4351343e8745a8d504` |
+| Branch | (not specified in METADATA.pb) |
+| Config YAML | `sources/config.yaml` (in upstream) |
+| Status | complete |
+| Date Added | 2015-01-28 |
+
+## How URL Found
+
+The repository URL `https://github.com/EbenSorkin/Dekko` was added in commit `c8f729cbd` by Simon Cozens (Jan 14 2024, "Add more upstreams (c,d)"). This is the canonical upstream repository maintained by Eben Sorkin / Sorkin Type.
+
+## How Commit Determined
+
+The commit `4887c14997f1158a2a122d4351343e8745a8d504` was set in commit `19cdcec59` ("Batch 1/4 port info from fontc_crater targets list" by Felipe Sanches, Mar 31 2025). This commit is the HEAD of the upstream repository, representing a merge of PR #12 from SorkinType/dependabot (Bump fonttools from 4.33.3 to 4.43.0).
+
+### Font Binary History
+
+The font binary in google/fonts was last modified in commit `b0235e00e` by Dave Crossland (May 11 2015, "Updating Dekko"). The current font in google/fonts was NOT rebuilt from the current upstream source using gftools-builder. The METADATA.pb source block references HEAD (`4887c14`) with the `config_yaml` pointing to `sources/config.yaml`, which is set up for future rebuilds.
+
+Note: The font binary in google/fonts predates the current upstream repo structure. The upstream was later restructured to have a proper `sources/` directory with `config.yaml` and `.glyphs` source.
+
+## Config YAML Status
+
+- **config.yaml exists in upstream**: `sources/config.yaml` with content:
+ ```yaml
+ sources:
+ - Dekko.glyphs
+ familyName: Dekko
+ buildVariable: False
+ ```
+- The `config_yaml` field in METADATA.pb is correctly set to `sources/config.yaml`
+- No override config.yaml in google/fonts
+- Source file `sources/Dekko.glyphs` exists in the upstream repo
+
+## Verification
+
+- Repository URL is valid and accessible: https://github.com/EbenSorkin/Dekko
+- Commit `4887c14` exists in the upstream repo and is HEAD
+- The upstream repo is a shallow clone, cached at `upstream_repos/fontc_crater_cache/EbenSorkin/Dekko/`
+- The `sources/config.yaml` file exists in the upstream repo at commit `4887c14`
+- The source block in METADATA.pb does NOT have `files` mappings or `branch` field, indicating it references the upstream for future rebuilds rather than documenting the original binary source
+
+## Confidence Level
+
+**HIGH** for URL and config_yaml. The upstream is the correct canonical repository with proper gftools-builder configuration.
+
+**MEDIUM** for commit hash. The commit `4887c14` is HEAD and was set for fontc_crater targets. The actual font binary in google/fonts was built from an earlier state of the upstream. However, for the purpose of gftools-builder compatibility, referencing HEAD is appropriate since the font would be rebuilt from the latest sources.
+
+## Open Questions
+
+- The font in google/fonts (last updated 2015) has not been rebuilt from the current upstream sources. A rebuild would update the font to the latest version with potential improvements.
--- /dev/null
+# Delicious Handrawn - Investigation Report
+
+## Source Data
+
+| Field | Value |
+|---|---|
+| Family Name | Delicious Handrawn |
+| Designer | Agung Rohmat |
+| License | OFL |
+| Repository URL | https://github.com/alphArtype/Delicious-Handrawn |
+| Commit Hash (in METADATA.pb) | 454896185708d68530577800804c032756040370 |
+| Correct Onboarding Commit | 0a9b42f98d6f2ee40563a406b1cdd9bb5a58fe57 |
+| Branch | main |
+| Config YAML | sources/config.yaml |
+| Status | complete (but commit hash is incorrect) |
+| Date Added | 2023-01-06 |
+
+## How URL Found
+
+The repository URL `https://github.com/alphArtype/Delicious-Handrawn` is documented in the METADATA.pb source block, the copyright string, and all three gftools-packager PRs.
+
+## How Commit Determined
+
+### Onboarding History
+
+Three versions were onboarded via gftools-packager:
+
+1. **v1.000** - Initial add (commit 8c3135f0b, 2023-01-06)
+ - Upstream commit: `b4bc06828c04da4ef07518386cc77bbdfdba1e20`
+
+2. **v1.001** - Update (commit 46f8f535f, 2023-02-15)
+ - Upstream commit: `d32722cd629ea4d6f48c63d5f4387a9441db3c6c`
+
+3. **v1.002** - Latest update, PR #6068 by emmamarichal (commit 0f70b3d62, 2023-03-23)
+ - Upstream commit: `0a9b42f98d6f2ee40563a406b1cdd9bb5a58fe57`
+ - This is the commit from which the current fonts in google/fonts were built
+
+### Commit Hash Discrepancy
+
+The METADATA.pb currently contains commit `454896185708d68530577800804c032756040370`, which is the HEAD of the upstream repo (a merge commit "Merge pull request #5 from sursly/main" from 2024-04-21). This is **newer** than the actual onboarding commit.
+
+This incorrect commit was introduced in commit `19cdcec59` ("Batch 1/4: port info from fontc_crater targets list", 2025-03-31), which replaced the correct commit `0a9b42f` with `4548961` based on fontc_crater's target.json data. The fontc_crater target list appears to track the latest upstream state rather than the exact onboarding commit.
+
+The correct onboarding commit should be `0a9b42f98d6f2ee40563a406b1cdd9bb5a58fe57` as documented in PR #6068.
+
+## Config YAML Status
+
+- `sources/config.yaml` exists in the upstream repository:
+ ```yaml
+ sources:
+ - Delicious-Handrawn.glyphs
+ familyName: Delicious Handrawn
+ buildVariable: false
+ ```
+- The `config_yaml` field in METADATA.pb correctly points to `sources/config.yaml`
+- No override config.yaml in google/fonts (not needed)
+
+## Verification
+
+- Repository URL is valid and accessible
+- Upstream repo cloned at `upstream_repos/fontc_crater_cache/alphArtype/Delicious-Handrawn/` (shallow clone)
+- Current HEAD (`4548961`) is newer than the onboarding commit (`0a9b42f`)
+- The config.yaml exists at `sources/config.yaml` in the upstream repo
+- Source file `Delicious-Handrawn.glyphs` referenced in config exists in `sources/` directory
+
+## Confidence Level
+
+**High** for repository URL and config_yaml. **High** that the correct onboarding commit should be `0a9b42f` (clearly documented in PR #6068), and that `4548961` in METADATA.pb is incorrect (introduced by batch fontc_crater port).
+
+## Open Questions
+
+- The commit hash in METADATA.pb should be corrected from `454896185708d68530577800804c032756040370` to `0a9b42f98d6f2ee40563a406b1cdd9bb5a58fe57` to reflect the actual onboarding commit used in PR #6068.
+- The newer commit `4548961` (2024-04-21) may contain source changes that haven't been reviewed for Google Fonts yet.
--- /dev/null
+# Della Respira
+
+## Summary
+
+Della Respira is a serif display typeface designed by Nathan Willis, a revival of the Della Robbia typeface by American Type Founders (ATF). The original source was hosted on Launchpad using Bazaar version control, not GitHub. A librefonts mirror exists on GitHub but contains only TTX-decomposed files, not real font sources.
+
+## Key Findings
+
+- **Designer**: Nathan Willis
+- **Date added to Google Fonts**: 2012-04-04
+- **Original source**: Launchpad (https://launchpad.net/revivalism-fonts/) using Bazaar VCS
+- **GitHub mirror**: https://github.com/librefonts/dellarespira (TTX-only, not buildable)
+- **Source formats available**: TTX decomposed files only (in librefonts mirror)
+- **config.yaml**: None (not applicable - no gftools-buildable sources)
+- **Override config.yaml**: None in google/fonts
+
+## Repository Analysis
+
+The librefonts/dellarespira GitHub repo was created by Mikhail Kashkin on 2014-07-16 as a mirror of the font data. It contains only TTX-decomposed font table files (the binary .ttf decompiled into XML), not actual editable font sources (.glyphs, .ufo, .sfd, etc.). The repo has 11 commits, all related to CI/Travis setup and TTX file organization.
+
+The actual font source was maintained on Launchpad at `lp:revivalism-fonts` using Bazaar (bzr) version control. The Launchpad project page is still accessible.
+
+## google/fonts History
+
+The font binary has not been updated since the initial commit (90abd17b4) of the google/fonts repository. No gftools-packager updates or font refreshes have occurred.
+
+## Status
+
+- **repository_url**: The librefonts mirror exists but has no buildable sources. The actual source was on Launchpad.
+- **commit**: N/A (no useful commit to reference in the TTX-only mirror)
+- **config_yaml**: N/A (no gftools-buildable sources exist)
+- **Overall**: no_upstream_repo - The only GitHub repo is a TTX mirror with no real font sources. The original Launchpad/Bazaar source is the true upstream but is not a GitHub repository.
+
+## Recommendation
+
+Status should remain `no_upstream_repo`. The librefonts mirror contains only TTX decomposed files and is not suitable as a build source. The original source on Launchpad uses Bazaar VCS which is not compatible with the Google Fonts toolchain.
--- /dev/null
+# Diphylleia
+
+## Summary
+
+| Field | Value |
+|---|---|
+| **Family name** | Diphylleia |
+| **Designer** | Minha Hyung, JAMO |
+| **License** | OFL |
+| **Date added** | 2023-05-18 |
+| **Repository URL** | https://github.com/JAMO-TYPEFACE/Diphylleia |
+| **Commit** | `6a20531aa22286238d89f3bc1d8c29694acaec53` |
+| **Branch** | main |
+| **Config YAML** | `Sources/config.yaml` |
+| **Status** | complete |
+
+## Upstream Repository
+
+The upstream repo at `JAMO-TYPEFACE/Diphylleia` contains:
+- `Sources/Diphylleia.glyphs` - Glyphs source file
+- `Sources/config.yaml` - gftools-builder configuration
+- `Fonts/ttf/Diphylleia-Regular.ttf` - Pre-built TTF
+- Standard Google Fonts project structure (AUTHORS.txt, CONTRIBUTORS.txt, etc.)
+
+The repo has a single commit (`6a20531`), indicating the repo was likely reset/force-pushed at some point.
+
+## Commit Verification
+
+The original onboarding used commit `d481ed1f2dc17d2457f9788351a1d4e886cdc221`, as recorded in the gftools-packager commit `c39470536` in google/fonts (by Aaron Bell, 2023-05-18). That commit message states: "taken from the upstream repo https://github.com/JAMO-TYPEFACE/Diphylleia at commit d481ed1f2dc17d2457f9788351a1d4e886cdc221".
+
+However, the upstream repo was subsequently reset to a single commit (`6a20531`, "Delete Diphylleia-Regular.otf", 2024-12-27). The original commit `d481ed1` no longer exists in the repo history.
+
+The METADATA.pb was updated from `d481ed1` to `6a20531` in commit `19cdcec59` ("[Batch 1/4] port info from fontc_crater targets list", 2025-03-31), which ported data from fontc_crater's targets.json file.
+
+A subsequent update to the TTF was made in google/fonts commit `469bc2664` ("Update Diphylleia-Regular.ttf - Adding missing glyph from GF Kernal", by Aaron Bell, 2023-05-24), without a corresponding upstream commit.
+
+## Config YAML
+
+The config.yaml at `Sources/config.yaml` contains:
+```yaml
+sources:
+ - Diphylleia.glyphs
+familyName: "Diphylleia"
+buildOTF: false
+```
+
+Note the capital "S" in `Sources/` - this was corrected in commit `7190093b1` in google/fonts.
+
+## Conclusion
+
+- Repository URL: Verified correct
+- Commit hash: `6a20531` is the only commit in the repo (original `d481ed1` was lost to repo reset)
+- Config YAML: Verified at `Sources/config.yaml`
+- Status: `complete` - all fields populated and verified
+- Note: The original onboarding commit is no longer in the repo history due to a force-push
--- /dev/null
+# Diplomata
+
+## Summary
+
+| Field | Value |
+|---|---|
+| **Family name** | Diplomata |
+| **Designer** | Eduardo Tunni |
+| **License** | OFL |
+| **Date added** | 2012-01-25 |
+| **Repository URL** | https://github.com/etunni/diplomata |
+| **Commit** | `32dc35e6b420631acc10808e1f92f74e3048e81d` |
+| **Branch** | master |
+| **Config YAML** | `sources/diplomata.yaml` |
+| **Status** | complete |
+
+## Upstream Repository
+
+The upstream repo at `etunni/diplomata` is shared between Diplomata and Diplomata SC. It contains:
+- `sources/Diplomata.glyphs` - Glyphs source for Diplomata
+- `sources/DiplomataSC.glyphs` - Glyphs source for Diplomata SC
+- `sources/diplomata.yaml` - gftools-builder config for Diplomata
+- `sources/diplomatasc.yaml` - gftools-builder config for Diplomata SC
+- `fonts/diplomata/ttf/Diplomata-Regular.ttf` - Pre-built TTF
+- `fonts/diplomatasc/ttf/DiplomataSC-Regular.ttf` - Pre-built TTF
+
+The repo has a single commit (`32dc35e`), which is a merge commit for PR #1 from emmamarichal/master.
+
+## Commit Verification
+
+The commit `32dc35e` ("Merge pull request #1 from emmamarichal/master - Diplomata and DiplomataSC update") was authored by Eduardo Rodriguez Tunni on 2023-02-16. This matches the gftools-packager commit `4ceb8d23f` in google/fonts (by Emma Marichal, same date), which states: "taken from the upstream repo https://github.com/etunni/diplomata at commit https://github.com/etunni/diplomata/commit/32dc35e6b420631acc10808e1f92f74e3048e81d".
+
+This is the only commit in the repo, and is confirmed as the correct onboarding commit.
+
+## Config YAML
+
+The config at `sources/diplomata.yaml` contains:
+```yaml
+sources:
+ - Diplomata.glyphs
+outputDir: "../fonts/diplomata"
+```
+
+## Source Block Status
+
+The METADATA.pb has a complete source block with:
+- repository_url, commit, branch, config_yaml, and files entries
+- All data was populated in commits `53995c52a` and `66f91f10f`
+
+## Conclusion
+
+- Repository URL: Verified correct
+- Commit hash: Verified correct (`32dc35e` is the sole commit, confirmed by gftools-packager)
+- Config YAML: Verified at `sources/diplomata.yaml`
+- Status: `complete` - all fields populated and verified
--- /dev/null
+# Diplomata SC
+
+## Summary
+
+| Field | Value |
+|---|---|
+| **Family name** | Diplomata SC |
+| **Designer** | Eduardo Tunni |
+| **License** | OFL |
+| **Date added** | 2012-01-25 |
+| **Repository URL** | https://github.com/etunni/diplomata |
+| **Commit** | `32dc35e6b420631acc10808e1f92f74e3048e81d` |
+| **Branch** | master |
+| **Config YAML** | `sources/diplomatasc.yaml` |
+| **Status** | complete |
+
+## Upstream Repository
+
+The upstream repo at `etunni/diplomata` is shared with the Diplomata family. It contains:
+- `sources/DiplomataSC.glyphs` - Glyphs source for Diplomata SC
+- `sources/diplomatasc.yaml` - gftools-builder config for Diplomata SC
+- `fonts/diplomatasc/ttf/DiplomataSC-Regular.ttf` - Pre-built TTF
+
+See the [Diplomata investigation](diplomata.md) for full repo details.
+
+## Commit Verification
+
+The commit `32dc35e` is the same as used for Diplomata (both families share the same upstream repo and commit). This was confirmed by the gftools-packager commit `6a8620423` in google/fonts (by Emma Marichal, 2023-02-16), which states: "taken from the upstream repo https://github.com/etunni/diplomata at commit https://github.com/etunni/diplomata/commit/32dc35e6b420631acc10808e1f92f74e3048e81d".
+
+## Config YAML
+
+The config at `sources/diplomatasc.yaml` contains:
+```yaml
+sources:
+ - DiplomataSC.glyphs
+outputDir: "../fonts/diplomatasc"
+```
+
+## Source Block Status
+
+The METADATA.pb has a complete source block with:
+- repository_url, commit, branch, config_yaml, and files entries
+- All data was populated in the same commits as Diplomata
+
+## Conclusion
+
+- Repository URL: Verified correct (shared repo with Diplomata)
+- Commit hash: Verified correct (`32dc35e` is the sole commit, confirmed by gftools-packager)
+- Config YAML: Verified at `sources/diplomatasc.yaml`
+- Status: `complete` - all fields populated and verified
--- /dev/null
+# DM Sans
+
+**Date investigated**: 2026-02-26
+**Status**: complete
+**Designer**: Colophon Foundry
+**METADATA.pb path**: `ofl/dmsans/METADATA.pb`
+
+## Source Data
+
+| Field | Value |
+|-------|-------|
+| Repository URL | https://github.com/googlefonts/dm-fonts |
+| Commit | `d0520ba03bd780f5dccb3024854463d44f699b78` |
+| Config YAML | `Sans/Source/config.yaml` |
+| Branch | `main` |
+
+## How the Repository URL Was Found
+
+The repository URL was already present in the METADATA.pb `source { repository_url }` field, set to `https://github.com/googlefonts/dm-fonts`. This is confirmed by multiple gftools-packager commit messages in google/fonts. The copyright string in the font files also references this URL ("Copyright 2014 The DM Sans Project Authors (https://github.com/googlefonts/dm-fonts)").
+
+## How the Commit Hash Was Identified
+
+The commit hash `d0520ba03bd780f5dccb3024854463d44f699b78` was identified from the most recent gftools-packager commit in google/fonts. Commit `db50662ac` (2023-06-14, by Emma Marichal) states: "DM Sans Version 4.004;gftools[0.9.30] taken from the upstream repo https://github.com/googlefonts/dm-fonts at commit https://github.com/googlefonts/dm-fonts/commit/d0520ba03bd780f5dccb3024854463d44f699b78."
+
+This commit (`d0520ba0`) in upstream has the message "STAT table updated" and is the third most recent commit in the dm-fonts repo. The two newer commits (`da9bd90` "Added tabular numbers" and `4412393` "Tabular update - Fonts exported") were made after the v4.004 onboarding.
+
+The METADATA.pb already contained this commit hash, having been set by the gftools-packager process.
+
+## Build Configuration
+
+The `config.yaml` at `Sans/Source/config.yaml` in the upstream dm-fonts repository is a valid gftools-builder configuration. It specifies:
+- Sources: `DMSans.glyphs` and `DMSans-Italic.glyphs`
+- Axis order: `opsz`, `wght`, `ital`
+- Family name: "DM Sans"
+- STAT table configuration for optical size, weight, and italic axes
+
+The METADATA.pb also includes explicit `files {}` entries mapping source files to destination files.
+
+## Relationship to Other DM Families
+
+DM Sans shares the `googlefonts/dm-fonts` repository with DM Serif Display and DM Serif Text. The Sans sources live under `Sans/Source/` while the Serif sources live under `Serif/Source/`. DM Mono has its own separate repo (`googlefonts/dm-mono`).
+
+## Timeline
+
+- **2019-06-12**: DM Sans v1.100 initially added to google/fonts by Marc Foley (commit `03cd45cdb`) as static fonts
+- **2019-10-16**: Updated via Font Bakery Dashboard (PR #2203) from dm-fonts commit `027cea4`
+- **2023-06-08**: Variable font version 4.003 added by Emma Marichal (commit `c26e50af6`) from upstream commit `7c79670d`
+- **2023-06-14**: Version 4.004 added by Emma Marichal (commit `db50662ac`) from upstream commit `d0520ba0` (current)
+
+## Issues Found
+
+None. The tracking data is accurate and complete. The METADATA.pb on main already has the correct commit hash, config_yaml, and branch.
--- /dev/null
+# Dokdo
+
+## Summary
+
+Dokdo is a Korean and Latin display font designed by FONTRIX. No upstream source repository has been identified on GitHub or elsewhere.
+
+## Key Findings
+
+| Field | Value |
+|-------|-------|
+| **Family Name** | Dokdo |
+| **Designer** | FONTRIX |
+| **License** | OFL |
+| **Date Added** | 2018-02-23 |
+| **Repository URL** | None found |
+| **Commit Hash** | N/A |
+| **Config YAML** | N/A |
+| **Status** | no_upstream_repo |
+
+## Investigation Details
+
+### Onboarding History
+
+Dokdo was added to Google Fonts in PR #1459 ("korean families r01: added") by Marc Foley on 2018-03-13 (commit `16680f868`). The PR body states: "Korean Font binaries have been mastered by Aaron Bell, https://www.sajatypeworks.com". This was a batch addition of Korean fonts.
+
+The font binary has not been updated since onboarding.
+
+### Upstream Repository Search
+
+- No GitHub repository found for "Dokdo font" or "FONTRIX"
+- FONTRIX appears to be a Korean foundry that contributed the font under OFL
+- The copyright states "Copyright (c) 2005-2017 FONTRIX. All Rights Reserved."
+- No upstream repo is cached in fontc_crater_cache
+- Dokdo is the only family in the Google Fonts catalog attributed to FONTRIX
+
+### Source Availability
+
+No source files (`.glyphs`, `.ufo`, `.designspace`, `.sfd`) are publicly available. Only the compiled TTF binary exists in google/fonts.
+
+## Conclusion
+
+Dokdo has no known upstream repository. The font was provided as a compiled binary by FONTRIX for the Korean fonts batch addition. Without an upstream repo, no config.yaml can be set up and the font cannot be rebuilt from sources via gftools-builder.
--- /dev/null
+# Domine
+
+## Summary
+
+Domine is a variable serif font by Impallari Type. It has complete source documentation in METADATA.pb with repository URL, commit hash, and config.yaml path.
+
+## Key Findings
+
+| Field | Value |
+|-------|-------|
+| **Family Name** | Domine |
+| **Designer** | Impallari Type |
+| **License** | OFL |
+| **Date Added** | 2012-11-30 |
+| **Repository URL** | https://github.com/googlefonts/Domine |
+| **Commit Hash** | `2974ac627aad3a34190288c07fd0a0040d38550f` |
+| **Config YAML** | `sources/config.yaml` |
+| **Status** | complete |
+
+## Investigation Details
+
+### Onboarding History
+
+Domine was originally added to Google Fonts in the initial commit (`90abd17b4`) as a static font. It was updated to v2.000 (variable font) in PR #2492 (commit `2194d6669`) by Marc Foley on 2020-06-10. The PR commit message states: "Taken from the upstream repo https://github.com/TypeNetwork/Domine at commit https://github.com/TypeNetwork/Domine/commit/a1676d0478fa24f63f45474091258008698bdf5f".
+
+The source block was later populated in the batch port from fontc_crater targets list (commit `19cdcec59`).
+
+### Upstream Repository
+
+The upstream repo at https://github.com/googlefonts/Domine contains:
+- `sources/Domine.designspace` - the designspace source
+- `sources/Domine-Regular.ufo` and `sources/Domine-Bold.ufo` - UFO sources
+- `sources/config.yaml` - gftools-builder configuration
+- `fonts/` - compiled font files
+
+The repo appears to be a fork/mirror maintained by googlefonts. The original v2 sources were at TypeNetwork/Domine.
+
+### Commit Verification
+
+The commit `2974ac6` in METADATA.pb is the HEAD (and only commit visible in the shallow clone) of the googlefonts/Domine repo. It adds the `sources/config.yaml` file. This is the commit used in fontc_crater targets.
+
+### Config YAML
+
+The `sources/config.yaml` contains:
+```yaml
+sources:
+ - Domine.designspace
+```
+
+No override config.yaml exists in the google/fonts family directory.
+
+## Conclusion
+
+Domine is fully documented with all required metadata. The source block is complete with repository URL, commit hash, and config.yaml path pointing to a valid gftools-builder configuration in the upstream repo.
--- /dev/null
+# Dongle
+
+## Summary
+
+Dongle is a Korean sans-serif font by Yanghee Ryu available in Light, Regular, and Bold weights. It has complete source documentation with a repository URL, commit hash, and an override config.yaml in the google/fonts directory.
+
+## Key Findings
+
+| Field | Value |
+|-------|-------|
+| **Family Name** | Dongle |
+| **Designer** | Yanghee Ryu |
+| **License** | OFL |
+| **Date Added** | 2021-06-14 |
+| **Repository URL** | https://github.com/yangheeryu/Dongle |
+| **Commit Hash** | `f7127c4d2450e1cad20254ec692591347e2fc260` |
+| **Config YAML** | Override in google/fonts (`ofl/dongle/config.yaml`) |
+| **Status** | complete |
+
+## Investigation Details
+
+### Onboarding History
+
+Dongle v2.000 was added to Google Fonts via PR #3530 (commit `388be86af`) by Aaron Bell on 2021-06-22. The PR commit message states: "Dongle Version 2.000 taken from the upstream repo https://github.com/yangheeryu/Dongle.git at commit https://github.com/yangheeryu/Dongle/commit/71cc5162a79d65b3b9b5ad70398473152ce59ab9."
+
+The source block and override config.yaml were later added in commit `5f31230ff` ("sources info for Dongle: Version 2.000 (PR #3530)").
+
+### Upstream Repository
+
+The upstream repo at https://github.com/yangheeryu/Dongle contains:
+- `sources/Dongle.zip` - source files in a zip archive
+- `fonts/ttf/` - compiled TTF files (Dongle-Light.ttf, Dongle-Regular.ttf, Dongle-Bold.ttf)
+- No config.yaml in the upstream repo
+
+The HEAD commit is `f7127c4` ("Update README.md"), which matches the METADATA.pb. The original onboarding was at commit `71cc516`, but the 3 commits between then and HEAD are only README/DESCRIPTION updates - no source or font changes.
+
+### Commit Hash Analysis
+
+The source files (`sources/Dongle.zip`) were last modified at commit `dbd7f34` ("Updated font metrics to match original"), which is earlier than both the onboarding commit (`71cc516`) and the recorded commit (`f7127c4`). Using HEAD is acceptable since no source changes occurred after onboarding.
+
+### Config YAML
+
+The METADATA.pb uses a `files` block to copy pre-compiled TTFs directly from the upstream repo (not rebuilding from sources). An override config.yaml exists in `ofl/dongle/config.yaml`:
+```yaml
+buildVariable: false
+sources:
+ - sources/Dongle.zip
+```
+
+Since the override config.yaml exists in the google/fonts directory, the `config_yaml` field is correctly omitted from the METADATA.pb source block.
+
+## Conclusion
+
+Dongle is fully documented. The source block has the correct repository URL and commit hash. The override config.yaml in the google/fonts directory provides the build configuration. No further action needed.
--- /dev/null
+# Dosis
+
+**Date investigated**: 2026-02-27
+**Status**: complete
+**Designer**: Impallari Type
+**METADATA.pb path**: `ofl/dosis/METADATA.pb`
+
+## Source Data
+
+| Field | Value |
+|-------|-------|
+| Repository URL | https://github.com/googlefonts/dosis-vf |
+| Commit | `3407d52f1d1b1c36c14e756ad0b36561d8d44a3b` |
+| Config YAML | `sources/config.yaml` |
+| Branch | `master` |
+
+## How the Repository URL Was Found
+
+The repository URL was already present in the METADATA.pb `source { repository_url }` field, set to `https://github.com/googlefonts/dosis-vf`. This URL is confirmed by the gftools-packager commit message in google/fonts PR #3821, which explicitly states the font was "taken from the upstream repo https://github.com/googlefonts/dosis-vf". The copyright string in the font files also references this URL ("Copyright 2011 The Dosis Project Authors (https://github.com/googlefonts/dosis-vf)").
+
+The `dosis-vf` repo is a variable font rework of the original Dosis project by Pablo Impallari. The repo is under the `googlefonts` GitHub organization.
+
+## How the Commit Hash Was Identified
+
+The commit hash `3407d52f1d1b1c36c14e756ad0b36561d8d44a3b` was identified from the gftools-packager commit in google/fonts. The commit `59f86d8fc` (2021-09-10, PR #3821 by Aaron Bell) explicitly states: "Dosis Version 3.002 taken from the upstream repo https://github.com/googlefonts/dosis-vf at commit https://github.com/googlefonts/dosis-vf/commit/3407d52f1d1b1c36c14e756ad0b36561d8d44a3b."
+
+This commit is the only commit in the upstream repository (which is a shallow clone in the local cache, but it is also the HEAD of the `master` branch). It is a merge commit by Marc Foley merging PR #18 from aaronbell/master ("Updated copyright string and fonts rebuilt"), dated 2021-09-09.
+
+**Binary verification**: The SHA256 hash of `fonts/variable/Dosis[wght].ttf` at this upstream commit matches exactly with the file in `ofl/dosis/Dosis[wght].ttf` in google/fonts (`b2238eef0b3464904fed097ef274c704bc63d21407369b7d7a5be7b0821a0e82`). This confirms the font binary was taken directly from this commit.
+
+## Build Configuration
+
+The upstream repository has a valid gftools-builder `config.yaml` at `sources/config.yaml`:
+
+```yaml
+sources:
+ - Dosis.glyphs
+axisOrder:
+ - wght
+familyName: "Dosis"
+```
+
+The source file is `sources/Dosis.glyphs` (Glyphs format). No override config.yaml exists in the google/fonts family directory. The METADATA.pb correctly references this config file via `config_yaml: "sources/config.yaml"`.
+
+## Timeline
+
+- **2015-03-07**: Dosis initially added to google/fonts (initial commit) as static fonts (7 weights)
+- **2018-10-23**: Variable font version 3.000 added by Eli Heuer (commit `fb60908eb`), replacing static fonts with `Dosis[wght].ttf`
+- **2019-07-26**: Version 3.001 update by Marc Foley (commit `e08d7ee8b`)
+- **2021-09-10**: Version 3.002 added by Aaron Bell (commit `59f86d8fc`, PR #3821) from upstream commit `3407d52` (current)
+
+## Issues Found
+
+None. The METADATA.pb source block is complete and accurate:
+- Repository URL correctly points to `https://github.com/googlefonts/dosis-vf`
+- Commit hash `3407d52` is verified via binary hash comparison
+- Config YAML path `sources/config.yaml` exists in the upstream repo at the referenced commit
+- Branch is correctly set to `master`
+- File mappings for `Dosis[wght].ttf` and `OFL.txt` are correctly specified
--- /dev/null
+# Doto
+
+**Date investigated**: 2026-02-27
+**Status**: complete
+**Designer**: Oliver Lalan
+**METADATA.pb path**: `ofl/doto/METADATA.pb`
+
+## Source Data
+
+| Field | Value |
+|-------|-------|
+| Repository URL | https://github.com/oliverlalan/Doto |
+| Commit | `1c587f2eed62cb257055540ac2a15f356070414f` |
+| Config YAML | `sources/config.yaml` (in upstream repo) |
+| Branch | `main` |
+
+## How the Repository URL Was Found
+
+The repository URL was already present in the METADATA.pb `source { repository_url }` field: `https://github.com/oliverlalan/Doto`. This URL is also confirmed by the font copyright string in METADATA.pb: "Copyright 2024-2024 The Doto Project Authors (https://github.com/oliverlalan/Doto)". The onboarding commit `2c982e6bd` in google/fonts explicitly states: "Taken from the upstream repo https://github.com/oliverlalan/Doto at commit https://github.com/oliverlalan/Doto/commit/1c587f2eed62cb257055540ac2a15f356070414f." The remote URL in the cached repo confirms the same address.
+
+## How the Commit Hash Was Identified
+
+The commit hash `1c587f2eed62cb257055540ac2a15f356070414f` was pre-existing in the METADATA.pb `source { commit }` field. It was also explicitly referenced in the onboarding commit message (`2c982e6bd` in google/fonts, authored by Emma Marichal on 2024-10-09).
+
+**Note on PR body discrepancy**: The google/fonts PR #8212 body text references a different commit: `f46a14819db0a833967774625e0f22edd2bf5319`. However, examining the commit object `1c587f2` reveals it is a merge commit with two parents:
+- `f46a148` (first parent, the initial repo state)
+- `b5569f2` (second parent, Emma Marichal's v-metrics update from upstream PR #5)
+
+The upstream PR #5 ("Update v-metrics") was merged on 2024-10-06 to center uppercase letterforms by adjusting typoAscender/typoDescender from 900/-300 to 950/-250. Emma Marichal opened the PR in the upstream repo, the designer merged it, and then Emma used the post-merge commit (`1c587f2`) for the google/fonts onboarding. This explains the discrepancy: the PR #8212 body was written referencing the earlier state (`f46a148`), but the actual METADATA.pb and onboarding commit correctly reference the final merged state (`1c587f2`).
+
+The upstream repo has only this single merge commit as its entire visible history (prior commits appear to have been squashed or the repo was initialized fresh with a merge).
+
+## How Config YAML Was Resolved
+
+The upstream repo contains a `config.yaml` at `sources/config.yaml`. This matches the `config_yaml: "sources/config.yaml"` field in METADATA.pb. Its contents:
+
+```yaml
+sources:
+ - Doto.designspace
+axisOrder:
+ - ROND
+ - wght
+buildOTF: false
+```
+
+The config references `Doto.designspace` in the same `sources/` directory, which defines a 2-axis variable font (ROND: Roundness 0-100, wght: Weight 100-900) using four UFO masters:
+- `Doto-ThinSquare.ufo`
+- `Doto-BlackSquare.ufo`
+- `Doto-ThinRound.ufo`
+- `Doto-BlackRound.ufo`
+
+No override `config.yaml` exists in the google/fonts family directory.
+
+## Verification
+
+- Commit exists in upstream repo: Yes (it is also HEAD of the `main` branch)
+- Commit date: 2024-10-07 04:01:26 +0700
+- Commit message: "Merge pull request #5 from emmamarichal/main - Update v-metrics"
+- Binary file verification: SHA-256 hash of `Doto[ROND,wght].ttf` matches exactly between google/fonts (`ofl/doto/`) and the upstream repo (`fonts/variable/`): `6f4fe7d37853b91df3698daa84cde2dbe1c9695d88c986e6510134910337d426`
+- Source files at commit: `sources/Doto.designspace`, four UFO masters, `sources/config.yaml`
+- Onboarding PR: google/fonts PR #8212, merged 2024-10-15 by Emma Marichal
+
+## Confidence
+
+**High**: All data points are fully consistent. The repository URL is confirmed by METADATA.pb, the font copyright string, and the onboarding commit message. The commit hash is verified present in the upstream repo and matches the binary files exactly (identical SHA-256). The config.yaml path is correct and points to a valid gftools-builder configuration. The discrepancy between the PR body commit reference (`f46a148`) and the METADATA.pb commit (`1c587f2`) is explained by Emma Marichal's v-metrics fix being merged into the upstream repo between PR creation and font onboarding.
+
+## Open Questions
+
+None. This family is fully documented with consistent evidence across METADATA.pb, google/fonts commit history, binary file verification, and the upstream repository.
--- /dev/null
+# Investigation Report: Dotum
+
+## Family Overview
+
+- **Family name**: Dotum
+- **Designer**: HanYang I&C Co.
+- **License**: OFL
+- **Category**: Sans Serif
+- **Primary script**: Korean (Kore)
+- **Date added**: 2024-05-15
+- **Description**: Dotum is a well-known gothic-style Korean font that first shipped with Windows 95, designed with clean, simple strokes for clarity in user interfaces. This version includes proportional Latin characters.
+
+## Source Block (Current)
+
+The METADATA.pb at `ofl/dotum/METADATA.pb` already contains a source block:
+
+```
+source {
+ repository_url: "https://github.com/googlefonts/gulim"
+ commit: "012723a8d5b6a6dc920330f26d165422c3014fd6"
+ files {
+ source_file: "OFL.txt"
+ dest_file: "OFL.txt"
+ }
+ files {
+ source_file: "fonts/ttf/hinted/dotum-Regular.ttf"
+ dest_file: "Dotum-Regular.ttf"
+ }
+ branch: "main"
+}
+```
+
+## Upstream Repository
+
+- **URL**: https://github.com/googlefonts/gulim
+- **Local cache**: `upstream_repos/fontc_crater_cache/googlefonts/gulim`
+- **Remote verified**: Yes (origin points to https://github.com/googlefonts/gulim)
+
+### Repository Structure
+
+The gulim repository hosts four related Korean font families: Gulim, GulimChe, Dotum, and DotumChe. All four originate from HanYang I&C Co. legacy fonts.
+
+```
+sources/
+ ttf/
+ Dotum.ttf (original TTF source)
+ DotumChe.ttf (original TTF source)
+ Gulim.ttf (original TTF source)
+ GulimChe.ttf (original TTF source)
+ ttc/
+ gulim.ttc (TrueType Collection containing all four)
+fonts/
+ ttf/
+ hinted/ (processed outputs with hinting)
+ unhinted/ (processed outputs without hinting)
+ bitmap/ (processed outputs with bitmap tables)
+ ttc/
+ gulim-Regular.ttc
+```
+
+### Source File Format
+
+The sources are **pre-compiled TTF binaries** (TrueType Font data with 19 tables including EBDT bitmap data). There are NO standard editable source files (.glyphs, .ufo, .designspace, .sfd) in the repository.
+
+The build process is a Python script (`process.py`) that:
+1. Reads the source TTFs from `sources/ttf/`
+2. Removes control character glyphs
+3. Updates copyright and license strings
+4. Sets `fontRevision` to 2.210
+5. Applies hinting fixes via `gftools fix-hinting`
+6. Creates subsets: bitmap (with EBLC/EBDT), hinted (without bitmaps), and unhinted (dehinted)
+7. Creates a TTC from the four static TTFs
+
+Dependencies: `fontbakery[googlefonts]>=0.9.2`, `gftools[qa]>=0.9.23`, `dehinter`
+
+### No config.yaml
+
+There is **no `config.yaml`** file anywhere in the upstream repository. The build process uses a custom `process.py` script and `Makefile`, not gftools-builder. This is because the sources are pre-compiled TTFs that undergo post-processing, not standard font source files that gftools-builder would compile.
+
+There is also **no override `config.yaml`** in `ofl/dotum/` in google/fonts.
+
+## Commit Verification
+
+### Referenced Commit
+
+- **Hash**: `012723a8d5b6a6dc920330f26d165422c3014fd6`
+- **Author**: Aaron Bell <aaron@sajatypeworks.com>
+- **Date**: 2024-05-15 21:35:03 -0700
+- **Message**: "updating filenames"
+- **This is the HEAD commit** of the gulim repository (the latest and last commit)
+
+This commit is confirmed to exist in the upstream repository and is the most recent commit.
+
+### Onboarding History in google/fonts
+
+1. **`8e087e4a9`** (2024-05-15) by Aaron Bell: "Dotum: Version 2.21 added" -- Initial onboarding with `dotum-Regular.ttf` (lowercase, 4,575,576 bytes). Commit message explicitly references upstream repo and commit `012723a`.
+
+2. **`300e23027`** (2024-06-04) by Aaron: "Update DESCRIPTION.en_us.html" -- Replaced "N/A" placeholder with actual description text.
+
+3. **`f39f963fa`** (2024-06-24) by Aaron: "Delete dotum-Regular.ttf" -- Removed the lowercase-named file (4,575,576 bytes).
+
+4. **`38ef2d49c`** (2024-06-24) by Aaron: "Updating vertical metrics and metadata" -- Added new `Dotum-Regular.ttf` (capitalized, 4,575,996 bytes) with updated vertical metrics and nbspace alignment. Also modified METADATA.pb and DESCRIPTION.
+
+5. **`0e974a7ea`** (2024-06-28) by Viviana Monsalve: "Dotum Japanese deleted" -- Removed Japanese subset from METADATA.pb.
+
+### PR History
+
+- **PR #7673**: "Dotum: Version 2.21 added" by @aaronbell, merged 2024-06-28 by @emmamarichal.
+ - PR body states: "Taken from the upstream repo https://github.com/googlefonts/gulim at commit https://github.com/googlefonts/gulim/commit/012723a8d5b6a6dc920330f26d165422c3014fd6"
+
+### Binary File Discrepancy
+
+The font binary in google/fonts (`Dotum-Regular.ttf`, 4,575,996 bytes) does NOT exactly match the file at the referenced upstream commit (`fonts/ttf/hinted/dotum-Regular.ttf`, 4,575,576 bytes). The google/fonts version is 420 bytes larger because Aaron updated vertical metrics and nbspace alignment during the PR review process (commit `38ef2d49c`). This modification happened in the google/fonts PR branch, not in the upstream repository.
+
+This means the `source_file` path in the METADATA.pb source block (`fonts/ttf/hinted/dotum-Regular.ttf`) points to the original file at that commit, but the actual binary shipped in google/fonts has been locally modified.
+
+## Assessment
+
+### Status: complete (with caveats)
+
+The source block is correctly populated with the right repository URL and commit hash. The commit hash `012723a` is indeed the commit that was used as the basis for onboarding, as confirmed by both the google/fonts commit message and the PR body.
+
+### Why no config.yaml is appropriate
+
+A gftools-builder `config.yaml` is **not applicable** for this family. The upstream repo does not contain standard editable font sources -- it contains pre-compiled legacy TTF binaries that are post-processed via a custom Python script. gftools-builder cannot be used to build fonts from TTF sources. Creating an override config.yaml would serve no purpose.
+
+### Confidence: HIGH
+
+- Repository URL is correct and verified
+- Commit hash is explicitly documented in both the google/fonts commit message and the PR body
+- The commit is the HEAD of the upstream repository
+- The onboarder (Aaron Bell) is the same person who created the upstream repository
+
+### Remaining Notes
+
+- The binary in google/fonts was locally modified during the PR process (vertical metrics update), so it does not byte-for-byte match the upstream file at the referenced commit
+- The source block uses the `files` mapping pattern (explicit source_file to dest_file), not config_yaml, which is the correct approach for TTF-sourced fonts
+- Four related families (Gulim, GulimChe, Dotum, DotumChe) all share the same upstream repo `googlefonts/gulim` and the same commit hash
--- /dev/null
+# Investigation Report: DotumChe
+
+## Family Overview
+
+- **Family name**: DotumChe
+- **Designer**: HanYang I&C Co.
+- **License**: OFL
+- **Category**: Sans Serif
+- **Primary script**: Korean (Kore)
+- **Date added**: 2024-05-15
+- **Description**: DotumChe is a well-known gothic-style Korean font that first shipped with Windows 95, designed with clean, simple strokes for clarity in user interfaces. This version includes monospace, half-width Latin characters.
+
+## Source Block (Current)
+
+The METADATA.pb at `ofl/dotumche/METADATA.pb` already contains a source block:
+
+```
+source {
+ repository_url: "https://github.com/googlefonts/gulim"
+ commit: "012723a8d5b6a6dc920330f26d165422c3014fd6"
+ files {
+ source_file: "OFL.txt"
+ dest_file: "OFL.txt"
+ }
+ files {
+ source_file: "fonts/ttf/hinted/dotumche-Regular.ttf"
+ dest_file: "DotumChe-Regular.ttf"
+ }
+ branch: "main"
+}
+```
+
+## Upstream Repository
+
+- **URL**: https://github.com/googlefonts/gulim
+- **Local cache**: `upstream_repos/fontc_crater_cache/googlefonts/gulim`
+- **Remote verified**: Yes (origin points to https://github.com/googlefonts/gulim)
+
+### Repository Structure
+
+The gulim repository hosts four related Korean font families: Gulim, GulimChe, Dotum, and DotumChe. All four originate from HanYang I&C Co. legacy fonts.
+
+```
+sources/
+ ttf/
+ Dotum.ttf (original TTF source)
+ DotumChe.ttf (original TTF source)
+ Gulim.ttf (original TTF source)
+ GulimChe.ttf (original TTF source)
+ ttc/
+ gulim.ttc (TrueType Collection containing all four)
+fonts/
+ ttf/
+ hinted/ (processed outputs with hinting)
+ unhinted/ (processed outputs without hinting)
+ bitmap/ (processed outputs with bitmap tables)
+ ttc/
+ gulim-Regular.ttc
+```
+
+### Source File Format
+
+The sources are **pre-compiled TTF binaries** (TrueType Font data with 19 tables including EBDT bitmap data). There are NO standard editable source files (.glyphs, .ufo, .designspace, .sfd) in the repository.
+
+The build process is a Python script (`process.py`) that:
+1. Reads the source TTFs from `sources/ttf/`
+2. Removes control character glyphs
+3. Updates copyright and license strings
+4. Sets `fontRevision` to 2.210
+5. Applies hinting fixes via `gftools fix-hinting`
+6. Creates subsets: bitmap (with EBLC/EBDT), hinted (without bitmaps), and unhinted (dehinted)
+7. Creates a TTC from the four static TTFs
+
+Dependencies: `fontbakery[googlefonts]>=0.9.2`, `gftools[qa]>=0.9.23`, `dehinter`
+
+### No config.yaml
+
+There is **no `config.yaml`** file anywhere in the upstream repository. The build process uses a custom `process.py` script and `Makefile`, not gftools-builder. This is because the sources are pre-compiled TTFs that undergo post-processing, not standard font source files that gftools-builder would compile.
+
+There is also **no override `config.yaml`** in `ofl/dotumche/` in google/fonts.
+
+## Commit Verification
+
+### Referenced Commit
+
+- **Hash**: `012723a8d5b6a6dc920330f26d165422c3014fd6`
+- **Author**: Aaron Bell <aaron@sajatypeworks.com>
+- **Date**: 2024-05-15 21:35:03 -0700
+- **Message**: "updating filenames"
+- **This is the HEAD commit** of the gulim repository (the latest and last commit)
+
+This commit is confirmed to exist in the upstream repository and is the most recent commit.
+
+### Onboarding History in google/fonts
+
+1. **`485993a9e`** (2024-05-15) by Aaron Bell: "Dotumche: Version 2.21 added" -- Initial onboarding with `dotumche-Regular.ttf` (lowercase, 4,568,076 bytes). Commit message explicitly references upstream repo and commit `012723a`.
+
+2. **`aeb0fac6f`** (2024-06-04) by Aaron: "Update DESCRIPTION.en_us.html" -- Replaced placeholder description text.
+
+3. **`c035cf0f1`** (2024-06-24) by Aaron: "Delete dotumche-Regular.ttf" -- Removed the lowercase-named file (4,568,076 bytes).
+
+4. **`685530dc5`** (2024-06-24) by Aaron: "Updating vertical metrics and metadata" -- Added new `DotumChe-Regular.ttf` (capitalized, 4,568,508 bytes) with updated vertical metrics.
+
+5. **`15d222b8e`** (2024-06-28) by Viviana Monsalve: "Dotumche Japanese deleted" -- Removed Japanese subset from METADATA.pb.
+
+### PR History
+
+- **PR #7674**: "Dotumche: Version 2.21 added" by @aaronbell, merged 2024-06-27 by @emmamarichal.
+ - PR body states: "Taken from the upstream repo https://github.com/googlefonts/gulim at commit https://github.com/googlefonts/gulim/commit/012723a8d5b6a6dc920330f26d165422c3014fd6"
+
+### Binary File Discrepancy
+
+The font binary in google/fonts (`DotumChe-Regular.ttf`, 4,568,508 bytes) does NOT exactly match the file at the referenced upstream commit (`fonts/ttf/hinted/dotumche-Regular.ttf`, 4,568,076 bytes). The google/fonts version is 432 bytes larger because Aaron updated vertical metrics during the PR review process (commit `685530dc5`). This modification happened in the google/fonts PR branch, not in the upstream repository.
+
+This means the `source_file` path in the METADATA.pb source block (`fonts/ttf/hinted/dotumche-Regular.ttf`) points to the original file at that commit, but the actual binary shipped in google/fonts has been locally modified.
+
+## Assessment
+
+### Status: complete (with caveats)
+
+The source block is correctly populated with the right repository URL and commit hash. The commit hash `012723a` is indeed the commit that was used as the basis for onboarding, as confirmed by both the google/fonts commit message and the PR body.
+
+### Why no config.yaml is appropriate
+
+A gftools-builder `config.yaml` is **not applicable** for this family. The upstream repo does not contain standard editable font sources -- it contains pre-compiled legacy TTF binaries that are post-processed via a custom Python script. gftools-builder cannot be used to build fonts from TTF sources. Creating an override config.yaml would serve no purpose.
+
+### Confidence: HIGH
+
+- Repository URL is correct and verified
+- Commit hash is explicitly documented in both the google/fonts commit message and the PR body
+- The commit is the HEAD of the upstream repository
+- The onboarder (Aaron Bell) is the same person who created the upstream repository
+
+### Remaining Notes
+
+- The binary in google/fonts was locally modified during the PR process (vertical metrics update), so it does not byte-for-byte match the upstream file at the referenced commit
+- The source block uses the `files` mapping pattern (explicit source_file to dest_file), not config_yaml, which is the correct approach for TTF-sourced fonts
+- Four related families (Gulim, GulimChe, Dotum, DotumChe) all share the same upstream repo `googlefonts/gulim` and the same commit hash
+- DotumChe was merged one day before its sibling Dotum: DotumChe PR #7674 merged 2024-06-27, Dotum PR #7673 merged 2024-06-28
--- /dev/null
+# EB Garamond
+
+**Date investigated**: 2026-02-27
+**Status**: complete
+**Designer**: Georg Duffner, Octavio Pardo
+**METADATA.pb path**: `ofl/ebgaramond/METADATA.pb`
+
+## Source Data
+
+| Field | Value |
+|-------|-------|
+| Repository URL | https://github.com/octaviopardo/EBGaramond12 |
+| Commit | `e608414f52e532b68e2182f96b4ce9db35335593` |
+| Config YAML | `sources/config.yaml` |
+| Branch | `master` |
+
+## How the Repository URL Was Found
+
+The repository URL `https://github.com/octaviopardo/EBGaramond12` was already present in the METADATA.pb `source { repository_url }` field. It was initially added by Simon Cozens in the "Update upstreams" commit (`cd5db6b6e`, 2023-12-14), which added a source block with only the repository_url. The commit hash and config_yaml were later added by Felipe Sanches in the "[Batch 1/4] port info from fontc_crater targets list" commit (`19cdcec59`, 2025-03-31).
+
+The copyright string in the font files also confirms this repository: "Copyright 2017 The EB Garamond Project Authors (https://github.com/octaviopardo/EBGaramond12)".
+
+Note: EB Garamond has a complex history. The original EB Garamond was created by Georg Duffner (hosted at `github.com/georgd/EB-Garamond`). Octavio Pardo created EBGaramond12 as a redesign/successor of the original, and it is EBGaramond12 that is currently served through Google Fonts.
+
+## How the Commit Hash Was Identified
+
+The commit hash `e608414f52e532b68e2182f96b4ce9db35335593` was ported from the fontc_crater targets list. This is the HEAD commit on the `master` branch of the upstream repository -- a merge commit "Merge pull request #40 from aaronbell/master" dated 2021-09-29.
+
+### Verification of the Commit Hash
+
+The font has gone through several updates in google/fonts:
+
+1. **v1.000 static (2017-10-31)**: Marc Foley added static fonts (commit `62e0ebd5d`, PR #1287) from the upstream repo.
+
+2. **v1.000 VF (2019-10-30)**: Marc Foley added variable fonts (commit `8d96f2bad`, PR #1881). The commit message explicitly references upstream commit `cbc4c4e7fa4031cb9c900e67bf5cb7f86e591986` ("VF build chain added", 2019-03-15) from PR #25 on the upstream repo.
+
+3. **v1.001 stat fix (2021-09-24)**: Aaron Bell updated the variable fonts with STAT table fixes (commit `177c41e76`, PR #3633). The PR body states: "Rebuilding of variable fonts and static instances from the UFR structure (https://github.com/aaronbell/EBGaramond12). PR'd to upstream." Aaron did the work on his fork, submitted it to google/fonts, and then it was merged upstream via PR #40 on 2021-09-29.
+
+The timeline is:
+- **2021-06-22 to 2021-07-22**: Aaron Bell made commits on his fork (STAT table, UFR conversion, autohinting rebuild)
+- **2021-09-24**: google/fonts PR #3633 merged (fonts built from Aaron's work)
+- **2021-09-29**: Upstream PR #40 merged by octaviopardo (commit `e608414f`)
+
+Since `e608414f` is the merge of Aaron's work into the upstream master, and it contains identical source files to the pre-merge commit `f1a73968` (no file differences between them), this commit hash is correct for representing the state of sources used to build the fonts currently in google/fonts. The merge happened 5 days after google/fonts merged, but the content is identical.
+
+## Build Configuration
+
+The `config.yaml` at `sources/config.yaml` in the upstream repository is a valid gftools-builder configuration. It specifies:
+- Sources: `EBGaramond.glyphs` and `EBGaramond-Italic.glyphs`
+- Axis order: `wght`, `ital`
+- Family name: "EB Garamond"
+- STAT table configuration for weight and italic axes
+- `autohintTTF: False` (added in the autohinting rebuild commit)
+
+The config.yaml was introduced in the UFR format conversion (commit `78b4eb2a`, 2021-06-23) and slightly updated in the autohinting rebuild (commit `f1a73968`, 2021-07-22, which added `autohintTTF: False`).
+
+No local override config.yaml exists in the google/fonts family directory.
+
+## Source Files
+
+The upstream repository contains Glyphs format sources:
+- `sources/EBGaramond.glyphs` (Roman)
+- `sources/EBGaramond-Italic.glyphs` (Italic)
+
+These produce two variable font files:
+- `EBGaramond[wght].ttf` (weight axis: 400-800)
+- `EBGaramond-Italic[wght].ttf` (weight axis: 400-800)
+
+## Timeline
+
+- **2011-03-23**: EB Garamond added to Google Fonts catalog (date_added in METADATA.pb)
+- **2017-10-31**: Static fonts v1.000 added by Marc Foley (commit `62e0ebd5d`, PR #1287) from octaviopardo/EBGaramond12
+- **2019-10-30**: Variable fonts v1.000 added by Marc Foley (commit `8d96f2bad`, PR #1881) from upstream commit `cbc4c4e7`
+- **2021-09-24**: v1.001 stat fix by Aaron Bell (commit `177c41e76`, PR #3633) -- UFR rebuild with STAT table
+- **2021-09-29**: Aaron's work merged upstream via PR #40 (commit `e608414f` = current METADATA.pb hash)
+- **2023-12-14**: Source block (repository_url only) added by Simon Cozens (commit `cd5db6b6e`)
+- **2024-01-18**: Broken merge of METADATA fixed by Simon Cozens (commit `e0845b367`)
+- **2025-03-31**: Commit hash and config_yaml added from fontc_crater targets by Felipe Sanches (commit `19cdcec59`)
+
+## Issues Found
+
+None. The source block in METADATA.pb is complete and accurate:
+- Repository URL correctly points to `octaviopardo/EBGaramond12`
+- Commit hash `e608414f` is the HEAD of master and correctly represents the state of sources used for the current fonts in google/fonts
+- Config YAML path `sources/config.yaml` exists at the referenced commit and is a valid gftools-builder configuration
+- The upstream repository is clean and up-to-date
--- /dev/null
+# Eczar
+
+**Date investigated**: 2026-02-27
+**Status**: complete
+**Designer**: Rosetta, Vaibhav Singh
+**METADATA.pb path**: `ofl/eczar/METADATA.pb`
+
+## Source Data
+
+| Field | Value |
+|-------|-------|
+| Repository URL | https://github.com/rosettatype/eczar |
+| Commit | `f248ec9c0c5e3a9442d22824cc1cba6c713725d5` |
+| Config YAML | `sources/builder.yaml` |
+| Branch | `master` |
+
+## How the Repository URL Was Found
+
+The repository URL `https://github.com/rosettatype/eczar` was already present in the METADATA.pb `source { repository_url }` field. It is also referenced in the copyright string in the font files ("Copyright 2014 The Eczar Project Authors (https://github.com/rosettatype/eczar)") and in the gftools-packager commit body for google/fonts PR #4321.
+
+## How the Commit Hash Was Identified
+
+The commit `f248ec9c0c5e3a9442d22824cc1cba6c713725d5` is explicitly referenced in the gftools-packager commit `597475e6f` in google/fonts, which states: "Eczar Version 2.000 taken from the upstream repo https://github.com/rosettatype/eczar at commit https://github.com/rosettatype/eczar/commit/f248ec9c0c5e3a9442d22824cc1cba6c713725d5."
+
+This commit is the sole commit in the upstream repository. It is a merge commit (PR #26 from yanone/master) dated 2022-02-17, titled "Merge pull request #26 from yanone/master". The PR body explains: "I was commissioned to prepare Eczar for publication on Google Fonts. I removed all the old UFO and .fea files and moved everything into one variable Glyphs source." The PR was authored by Yanone and merged on 2022-02-17.
+
+The google/fonts PR #4321 was created by Yanone on 2022-02-17 and merged by RosaWagner on 2022-02-18. The timeline is consistent: the upstream PR was merged first, then the google/fonts PR was created referencing that commit.
+
+## How Config YAML Was Resolved
+
+The config file `sources/builder.yaml` exists at the referenced commit in the upstream repository. Its contents:
+
+```yaml
+sources:
+ - Eczar.glyphs
+outputDir: "../release"
+buildStatic: true
+buildVariable: true
+buildTTF: false
+buildOTF: false
+buildWebfont: false
+```
+
+No override `config.yaml` exists in the google/fonts family directory (`ofl/eczar/`). The `config_yaml` field was added to METADATA.pb in commit `35e809c6b` ("sources info for Eczar", 2025-04-02).
+
+## Verification
+
+- Commit exists in upstream repo: Yes (it is the only commit)
+- Commit date: 2022-02-17 15:35:18 +0100
+- Commit message: "Merge pull request #26 from yanone/master"
+- Source files at commit: `sources/Eczar.glyphs`, `sources/builder.yaml`
+- Binary match: The `Eczar[wght].ttf` in google/fonts is byte-identical to `release/variable/Eczar[wght].ttf` in the upstream repo (MD5: `2d26d338d36619e60fc98e285c3624d2`, 407304 bytes)
+- Upstream repo is clean with no local modifications
+
+## History in google/fonts
+
+The font was originally added in the initial commit (`90abd17b4`) with static instances. Notable subsequent updates:
+- `597475e6f` (2022-02-18): Version 2.000 added via gftools-packager (PR #4321) -- replaced 5 static TTFs with a single variable font `Eczar[wght].ttf`
+- `66f91f10f` (2024-04-03): upstream.yaml merged into METADATA.pb, adding files and branch info
+- `35e809c6b` (2025-04-02): `config_yaml` field added to source block
+
+## Confidence
+
+**HIGH**: All metadata is fully verified. The repository URL matches the copyright string and gftools-packager references. The commit hash is the sole commit in the upstream repo and is explicitly cited in the google/fonts onboarding commit body. The binary font file in google/fonts is byte-identical to the one in the upstream repo. The builder.yaml config is present at the referenced commit and correctly referenced in METADATA.pb. No open questions remain.
+
+## Open Questions
+
+None.
--- /dev/null
+# Investigation: Edu AU VIC WA NT Arrows
+
+## Family Overview
+
+- **Family name**: Edu AU VIC WA NT Arrows
+- **Display name**: Edu Australia VIC WA NT Hand Arrows
+- **Designer**: Tina Anderson, Corey Anderson
+- **License**: OFL
+- **Category**: HANDWRITING
+- **Date added**: 2024-08-12
+- **Variable axes**: wght (400-700)
+
+## Source Block Status
+
+**Already has source block**: Yes (complete with repository_url, commit, archive_url, files, branch, config_yaml)
+
+## Upstream Repository
+
+- **Repository URL**: https://github.com/SorkinType/VICWANTSchoolhandAustralia
+- **Cached at**: upstream_repos/fontc_crater_cache/SorkinType/VICWANTSchoolhandAustralia
+- **Repository status**: Clean, up to date with origin
+- **Source files**: `sources/AuVICWANT.glyphs` (single Glyphs source)
+- **Config**: `sources/config.yaml` using `fontprimer` recipe provider
+- **Shared repo**: This upstream repo serves ALL five Edu AU VIC WA NT family variants (Hand, Arrows, Dots, Guides, Pre). A single `.glyphs` source is built into multiple font families using the `variants` system in config.yaml.
+
+## Config.yaml Analysis
+
+The config.yaml uses `recipeProvider: fontprimer` with a `variants` system that produces different font families from a single source (`AuVICWANT.glyphs`). The Arrows variant is defined as:
+
+```yaml
+- name: Outline Arrows
+ alias: Arrows
+ steps:
+ - operation: featureFreeze
+ args: -f ss05
+ - operation: exec
+ args: --output-file=$out --unicodes=A0,20,30-39,61-7A,41-5A --notdef-outline --name-IDs=* --layout-features=* $in
+ exe: hb-subset
+```
+
+The Arrows variant freezes stylistic set 5 (ss05) and subsets to a limited character set.
+
+## Commit Hash Analysis
+
+### Current METADATA.pb commit
+- **Commit**: `6529c525fceb9ec15e51dfa6d87244ef053c2d8a`
+- **Date**: 2024-12-04
+- **Author**: Eben Sorkin
+- **Message**: "corrected positions for lcaron, dcaron, tcaron and Lcaron in the various styles required for cursive and other stylistic varients"
+
+### Important: Repo history was squashed
+The upstream repo currently has only ONE commit (`6529c52`), dated 2024-12-04. All previous history was squashed into this single commit. The old commit hashes still exist as GitHub tags but are no longer reachable from any branch:
+
+- **v1.000** tag -> `abab94d19985f24132e45db4c4822b042eb63302` (initial release, 2024-03-19)
+- **v1.001** tag -> `88099a2e2d47e222cb62441730a2bc1c082754e1` (2024-04-30)
+- **v1.002** tag -> `4d4efe710065410b34b66fa9d588498351642f41` (2024-10-11)
+
+### Onboarding History in google/fonts
+
+The Arrows variant went through several stages:
+
+1. **First onboarding (as "Edu VIC WA NT Arrows")**: Initially onboarded under the directory `ofl/eduvicwantarrows/` with commit `abab94d1` (v1.000 tag). Merged via PR #7447 on 2024-08-15 by Viviana Monsalve.
+
+2. **Rename and update**: Commit `69cc6cf7` (2024-08-13, Simon Cozens) renamed from `ofl/eduvicwantarrows/` to `ofl/eduauvicwantarrows/` and updated the font binary. The old METADATA.pb referenced `VICWANTSchoolHandAustralia` (uppercase H) which was corrected to `VICWANTSchoolhandAustralia`.
+
+3. **Display name fix**: PR #8070, merged 2024-08-20 by Viviana Monsalve, fixed the `display_name` field.
+
+4. **v1.001 update**: PR #8319, merged 2024-11-08 by Viviana Monsalve. Simon Cozens's commit (`22484892c`, 2024-10-11) updated the font binary and changed the commit hash from `abab94d1` (v1.000) to `4d4efe71` (v1.002) and archive_url to the v1.002 release. The commit message explicitly stated: "Taken from the upstream repo https://github.com/SorkinType/VICWANTSchoolhandAustralia at commit https://github.com/SorkinType/VICWANTSchoolhandAustralia/commit/4d4efe710065410b34b66fa9d588498351642f41."
+
+5. **Batch update**: Commit `19cdcec5` (2025-03-31, Felipe Sanches) as part of "[Batch 1/4] port info from fontc_crater targets list" changed the commit hash from `4d4efe71` to `6529c52` and added `config_yaml: "sources/config.yaml"`.
+
+### Commit hash accuracy concern
+
+The current commit `6529c52` in METADATA.pb was set by the batch update on 2025-03-31. This is a post-onboarding squash commit from 2024-12-04 that consolidates all previous history. The original onboarding used commit `4d4efe71` (tag v1.002, from 2024-10-11) as referenced by Simon Cozens's explicit commit message. Since the upstream repo was force-pushed to squash history, the original commit is no longer reachable from any branch (though tags still reference it on GitHub). Using the current HEAD `6529c52` is reasonable since the repo has only one commit now, but the original commit was `4d4efe71`.
+
+## Verification Summary
+
+| Field | Value | Status |
+|-------|-------|--------|
+| repository_url | https://github.com/SorkinType/VICWANTSchoolhandAustralia | Correct |
+| commit | 6529c525fceb9ec15e51dfa6d87244ef053c2d8a | Acceptable (post-squash HEAD; original was 4d4efe71) |
+| config_yaml | sources/config.yaml | Correct (exists in repo) |
+| archive_url | v1.002 release | Correct |
+| branch | main | Correct |
+
+## Status
+
+- **Status**: complete
+- **Confidence**: HIGH
+- **Notes**: Source block is fully populated. The commit hash `6529c52` is the only commit in the (squashed) repo, so it is the most sensible value to reference. The config.yaml uses `fontprimer` recipe provider, which is not the standard `gftools-builder` but is the correct configuration for this font family. No action needed.
--- /dev/null
+# Investigation: Edu AU VIC WA NT Dots
+
+## Family Overview
+
+- **Family name**: Edu AU VIC WA NT Dots
+- **Display name**: Edu Australia VIC WA NT Hand Dots
+- **Designer**: Tina Anderson, Corey Anderson
+- **License**: OFL
+- **Category**: HANDWRITING
+- **Date added**: 2024-08-12
+- **Variable axes**: wght (400-700)
+
+## Source Block Status
+
+**Already has source block**: Yes (complete with repository_url, commit, archive_url, files, branch, config_yaml)
+
+## Upstream Repository
+
+- **Repository URL**: https://github.com/SorkinType/VICWANTSchoolhandAustralia
+- **Cached at**: upstream_repos/fontc_crater_cache/SorkinType/VICWANTSchoolhandAustralia
+- **Repository status**: Clean, up to date with origin
+- **Source files**: `sources/AuVICWANT.glyphs` (single Glyphs source)
+- **Config**: `sources/config.yaml` using `fontprimer` recipe provider
+- **Shared repo**: This upstream repo serves ALL five Edu AU VIC WA NT family variants (Hand, Arrows, Dots, Guides, Pre). A single `.glyphs` source is built into multiple font families using the `variants` system in config.yaml.
+
+## Config.yaml Analysis
+
+The config.yaml uses `recipeProvider: fontprimer` with a `variants` system. The Dots variant is defined as:
+
+```yaml
+- name: Dots
+ steps:
+ - operation: featureFreeze
+ args: -f ss06
+ - operation: exec
+ args: --output-file=$out --unicodes=A0,20,30-39,61-7A,41-5A --notdef-outline --name-IDs=* --layout-features=* $in
+ exe: hb-subset
+```
+
+The Dots variant freezes stylistic set 6 (ss06) and subsets to a limited character set.
+
+## Commit Hash Analysis
+
+### Current METADATA.pb commit
+- **Commit**: `6529c525fceb9ec15e51dfa6d87244ef053c2d8a`
+- **Date**: 2024-12-04
+- **Author**: Eben Sorkin
+- **Message**: "corrected positions for lcaron, dcaron, tcaron and Lcaron in the various styles required for cursive and other stylistic varients"
+
+### Important: Repo history was squashed
+The upstream repo currently has only ONE commit (`6529c52`), dated 2024-12-04. All previous history was squashed into this single commit. The old commit hashes still exist as GitHub tags but are no longer reachable from any branch:
+
+- **v1.000** tag -> `abab94d19985f24132e45db4c4822b042eb63302` (initial release, 2024-03-19)
+- **v1.001** tag -> `88099a2e2d47e222cb62441730a2bc1c082754e1` (2024-04-30)
+- **v1.002** tag -> `4d4efe710065410b34b66fa9d588498351642f41` (2024-10-11)
+
+### Onboarding History in google/fonts
+
+1. **Initial onboarding**: Commit `d287d97d` (2024-08-13, Simon Cozens) "Edu VIC WA NT Dots: Version 1.001 added". This commit added the font with commit hash `abab94d1` (v1.000 tag) and archive_url pointing to the v1.000 release. No explicit upstream commit reference in the commit message body. Merged via PR #8020 on 2024-08-20 by Viviana Monsalve.
+
+2. **Display name update**: Commit `42cbd18e` updated the `display_name` in METADATA.pb.
+
+3. **Custom sample text**: Commit `9184f230` (date unclear) added custom `sample_text` block.
+
+4. **Batch update**: Commit `19cdcec5` (2025-03-31, Felipe Sanches) as part of "[Batch 1/4] port info from fontc_crater targets list" changed the commit hash from `abab94d1` (v1.000) to `6529c52` (current HEAD) and added `config_yaml: "sources/config.yaml"`.
+
+### Archive URL inconsistency
+
+The METADATA.pb currently references commit `6529c52` (which is the squashed HEAD, incorporating all versions including v1.002) but the `archive_url` still points to the v1.000 release. This is a minor inconsistency: the commit hash implies the latest code, but the archive URL points to an older release. However, since the binary font in google/fonts was never updated from the initial v1.000 onboarding, the v1.000 archive is actually the correct one for the binary that was originally served.
+
+### Commit hash accuracy concern
+
+The original onboarding used commit `abab94d1` (tag v1.000). The batch update changed this to `6529c52` (post-squash HEAD). Since the repo was force-pushed to squash history, `6529c52` is the only reachable commit. The font binary in google/fonts was onboarded from the v1.000 release and was never updated.
+
+## Verification Summary
+
+| Field | Value | Status |
+|-------|-------|--------|
+| repository_url | https://github.com/SorkinType/VICWANTSchoolhandAustralia | Correct |
+| commit | 6529c525fceb9ec15e51dfa6d87244ef053c2d8a | Acceptable (post-squash HEAD; original was abab94d1 / v1.000) |
+| config_yaml | sources/config.yaml | Correct (exists in repo) |
+| archive_url | v1.000 release | Correct for the onboarded binary |
+| branch | main | Correct |
+
+## Status
+
+- **Status**: complete
+- **Confidence**: HIGH
+- **Notes**: Source block is fully populated. The commit hash `6529c52` is the only commit in the (squashed) repo. The archive_url points to v1.000 which matches the binary originally onboarded. The config.yaml uses `fontprimer` recipe provider. No action needed.
--- /dev/null
+# Investigation: Edu AU VIC WA NT Guides
+
+## Family Overview
+
+- **Family name**: Edu AU VIC WA NT Guides
+- **Display name**: Edu Australia VIC WA NT Hand Guides
+- **Designer**: Tina Anderson, Corey Anderson
+- **License**: OFL
+- **Category**: HANDWRITING
+- **Date added**: 2024-08-12
+- **Variable axes**: wght (400-700)
+
+## Source Block Status
+
+**Already has source block**: Yes (complete with repository_url, commit, archive_url, files, branch, config_yaml)
+
+## Upstream Repository
+
+- **Repository URL**: https://github.com/SorkinType/VICWANTSchoolhandAustralia
+- **Cached at**: upstream_repos/fontc_crater_cache/SorkinType/VICWANTSchoolhandAustralia
+- **Repository status**: Clean, up to date with origin
+- **Source files**: `sources/AuVICWANT.glyphs` (single Glyphs source)
+- **Config**: `sources/config.yaml` using `fontprimer` recipe provider
+- **Shared repo**: This upstream repo serves ALL five Edu AU VIC WA NT family variants (Hand, Arrows, Dots, Guides, Pre). A single `.glyphs` source is built into multiple font families using the `variants` system in config.yaml.
+
+## Config.yaml Analysis
+
+The config.yaml uses `recipeProvider: fontprimer` with a `variants` system. The Guides variant is not explicitly listed among the named variants in config.yaml. Instead, it is generated by the `doGuidelines: true` flag in config.yaml, which instructs fontprimer to produce an additional "Guides" variant automatically.
+
+## Commit Hash Analysis
+
+### Current METADATA.pb commit
+- **Commit**: `6529c525fceb9ec15e51dfa6d87244ef053c2d8a`
+- **Date**: 2024-12-04
+- **Author**: Eben Sorkin
+- **Message**: "corrected positions for lcaron, dcaron, tcaron and Lcaron in the various styles required for cursive and other stylistic varients"
+
+### Important: Repo history was squashed
+The upstream repo currently has only ONE commit (`6529c52`), dated 2024-12-04. All previous history was squashed into this single commit. The old commit hashes still exist as GitHub tags but are no longer reachable from any branch:
+
+- **v1.000** tag -> `abab94d19985f24132e45db4c4822b042eb63302` (initial release, 2024-03-19)
+- **v1.001** tag -> `88099a2e2d47e222cb62441730a2bc1c082754e1` (2024-04-30)
+- **v1.002** tag -> `4d4efe710065410b34b66fa9d588498351642f41` (2024-10-11)
+
+### Onboarding History in google/fonts
+
+1. **Initial onboarding**: Commit `72283941` (2024-08-13, Simon Cozens) "Edu VIC WA NT Guides: Version 1.001 added". This commit added the font with commit hash `abab94d1` (v1.000 tag) and archive_url pointing to the v1.000 release. No explicit upstream commit reference in the commit message body. Merged via PR #8021 on 2024-08-20 by Viviana Monsalve.
+
+2. **Display name update**: Commit `8715b340` updated the `display_name` in METADATA.pb.
+
+3. **Batch update**: Commit `19cdcec5` (2025-03-31, Felipe Sanches) as part of "[Batch 1/4] port info from fontc_crater targets list" changed the commit hash from `abab94d1` (v1.000) to `6529c52` (current HEAD) and added `config_yaml: "sources/config.yaml"`.
+
+### Archive URL inconsistency
+
+The METADATA.pb currently references commit `6529c52` (post-squash HEAD) but the `archive_url` still points to the v1.000 release. The font binary in google/fonts was onboarded from the v1.000 release and was never updated.
+
+### Commit hash accuracy concern
+
+The original onboarding used commit `abab94d1` (tag v1.000). The batch update changed this to `6529c52` (post-squash HEAD). Since the repo was force-pushed to squash history, `6529c52` is the only reachable commit.
+
+## Verification Summary
+
+| Field | Value | Status |
+|-------|-------|--------|
+| repository_url | https://github.com/SorkinType/VICWANTSchoolhandAustralia | Correct |
+| commit | 6529c525fceb9ec15e51dfa6d87244ef053c2d8a | Acceptable (post-squash HEAD; original was abab94d1 / v1.000) |
+| config_yaml | sources/config.yaml | Correct (exists in repo) |
+| archive_url | v1.000 release | Correct for the onboarded binary |
+| branch | main | Correct |
+
+## Status
+
+- **Status**: complete
+- **Confidence**: HIGH
+- **Notes**: Source block is fully populated. The commit hash `6529c52` is the only commit in the (squashed) repo. The archive_url points to v1.000 which matches the binary originally onboarded. The config.yaml uses `fontprimer` recipe provider. No action needed.
--- /dev/null
+# Investigation: Edu AU VIC WA NT Hand
+
+## Family Overview
+
+- **Family name**: Edu AU VIC WA NT Hand
+- **Display name**: Edu Australia VIC WA NT Hand
+- **Designer**: Tina Anderson, Corey Anderson
+- **License**: OFL
+- **Category**: HANDWRITING
+- **Date added**: 2024-05-02
+- **Variable axes**: wght (400-700)
+
+## Source Block Status
+
+**Already has source block**: Yes (complete with repository_url, commit, archive_url, files, branch, config_yaml)
+
+## Upstream Repository
+
+- **Repository URL**: https://github.com/SorkinType/VICWANTSchoolhandAustralia
+- **Cached at**: upstream_repos/fontc_crater_cache/SorkinType/VICWANTSchoolhandAustralia
+- **Repository status**: Clean, up to date with origin
+- **Source files**: `sources/AuVICWANT.glyphs` (single Glyphs source)
+- **Config**: `sources/config.yaml` using `fontprimer` recipe provider
+- **Shared repo**: This upstream repo serves ALL five Edu AU VIC WA NT family variants (Hand, Arrows, Dots, Guides, Pre). A single `.glyphs` source is built into multiple font families using the `variants` system in config.yaml.
+
+## Config.yaml Analysis
+
+The config.yaml uses `recipeProvider: fontprimer` with `familyName: Edu AU VIC WA NT Hand` and `shortFamilyName: Edu AU VIC WA NT`. The Hand variant is the base/default variant -- all other variants (Pre, Arrows, Dots, Guides) are derived from it through the `variants` list using stylistic set freezing and subsetting operations.
+
+## Commit Hash Analysis
+
+### Current METADATA.pb commit
+- **Commit**: `6529c525fceb9ec15e51dfa6d87244ef053c2d8a`
+- **Date**: 2024-12-04
+- **Author**: Eben Sorkin
+- **Message**: "corrected positions for lcaron, dcaron, tcaron and Lcaron in the various styles required for cursive and other stylistic varients"
+
+### Important: Repo history was squashed
+The upstream repo currently has only ONE commit (`6529c52`), dated 2024-12-04. All previous history was squashed into this single commit. The old commit hashes still exist as GitHub tags but are no longer reachable from any branch:
+
+- **v1.000** tag -> `abab94d19985f24132e45db4c4822b042eb63302` (initial release, 2024-03-19)
+- **v1.001** tag -> `88099a2e2d47e222cb62441730a2bc1c082754e1` (2024-04-30)
+- **v1.002** tag -> `4d4efe710065410b34b66fa9d588498351642f41` (2024-10-11)
+
+### Onboarding History in google/fonts
+
+The Hand variant was the FIRST of the five to be onboarded, and has the most complex history:
+
+1. **Initial onboarding**: Commit `4191cb9e` (2024-05-02, Simon Cozens) "Edu AU VIC WA NT Hand: Version 1.001 added". The commit body explicitly states: "Taken from the upstream repo https://github.com/SorkinType/VICWANTSchoolhandAustralia at commit https://github.com/SorkinType/VICWANTSchoolhandAustralia/commit/88099a2e2d47e222cb62441730a2bc1c082754e1." This matches the v1.001 tag.
+
+2. **Update**: Commit `f391c677` (2024-05-03, Simon Cozens) "Update" -- updated DESCRIPTION, font binary, METADATA.pb, and OFL.txt.
+
+3. **Fixes**: Commit `bf2234b6` (2024-05-09, Simon Cozens) "Fixes" -- font binary update only.
+
+4. **Latest build (x3)**: Commits `a4d81d6c`, `cf4ce712`, `685295e6` (May-June 2024, Simon Cozens) -- incremental font binary updates.
+
+5. **PR merge**: PR #7628, merged 2024-06-06 by Emma Marichal.
+
+6. **Batch update**: Commit `19cdcec5` (2025-03-31, Felipe Sanches) as part of "[Batch 1/4] port info from fontc_crater targets list" changed the commit hash from `88099a2e` (v1.001) to `6529c52` (current HEAD) and added `config_yaml: "sources/config.yaml"`.
+
+### Commit hash accuracy
+
+The original onboarding explicitly referenced commit `88099a2e` (v1.001 tag). The font went through several iterations in the PR before merging. The batch update later changed the hash to `6529c52` (post-squash HEAD). The METADATA.pb `archive_url` correctly points to the v1.001 release, which aligns with the original onboarding commit.
+
+## Verification Summary
+
+| Field | Value | Status |
+|-------|-------|--------|
+| repository_url | https://github.com/SorkinType/VICWANTSchoolhandAustralia | Correct |
+| commit | 6529c525fceb9ec15e51dfa6d87244ef053c2d8a | Acceptable (post-squash HEAD; original was 88099a2e / v1.001) |
+| config_yaml | sources/config.yaml | Correct (exists in repo) |
+| archive_url | v1.001 release | Correct for the original onboarding |
+| branch | main | Correct |
+
+## Status
+
+- **Status**: complete
+- **Confidence**: HIGH
+- **Notes**: Source block is fully populated. This was the first of the five Edu AU VIC WA NT variants to be onboarded (2024-05-02 vs 2024-08-12 for the others). The commit hash `6529c52` is the only commit in the (squashed) repo. The archive_url points to v1.001 which matches the binary from the original onboarding by Simon Cozens. The config.yaml uses `fontprimer` recipe provider. No action needed.
--- /dev/null
+# Investigation: Edu AU VIC WA NT Pre
+
+## Family Overview
+
+- **Family name**: Edu AU VIC WA NT Pre
+- **Display name**: Edu Australia VIC WA NT Hand Precursive
+- **Designer**: Tina Anderson, Corey Anderson
+- **License**: OFL
+- **Category**: HANDWRITING
+- **Date added**: 2024-08-12
+- **Variable axes**: wght (400-700)
+
+## Source Block Status
+
+**Already has source block**: Yes (complete with repository_url, commit, archive_url, files, branch, config_yaml)
+
+## Upstream Repository
+
+- **Repository URL**: https://github.com/SorkinType/VICWANTSchoolhandAustralia
+- **Cached at**: upstream_repos/fontc_crater_cache/SorkinType/VICWANTSchoolhandAustralia
+- **Repository status**: Clean, up to date with origin
+- **Source files**: `sources/AuVICWANT.glyphs` (single Glyphs source)
+- **Config**: `sources/config.yaml` using `fontprimer` recipe provider
+- **Shared repo**: This upstream repo serves ALL five Edu AU VIC WA NT family variants (Hand, Arrows, Dots, Guides, Pre). A single `.glyphs` source is built into multiple font families using the `variants` system in config.yaml.
+
+## Config.yaml Analysis
+
+The config.yaml uses `recipeProvider: fontprimer` with a `variants` system. The Pre (Precursive) variant is defined as:
+
+```yaml
+- name: Precursive
+ alias: Pre
+ steps:
+ - operation: remapLayout
+ args: "'ss01=>ccmp'"
+```
+
+The Precursive variant remaps stylistic set 1 (ss01) to the `ccmp` (Glyph Composition/Decomposition) feature, effectively making the precursive letterforms the default.
+
+## Commit Hash Analysis
+
+### Current METADATA.pb commit
+- **Commit**: `6529c525fceb9ec15e51dfa6d87244ef053c2d8a`
+- **Date**: 2024-12-04
+- **Author**: Eben Sorkin
+- **Message**: "corrected positions for lcaron, dcaron, tcaron and Lcaron in the various styles required for cursive and other stylistic varients"
+
+### Important: Repo history was squashed
+The upstream repo currently has only ONE commit (`6529c52`), dated 2024-12-04. All previous history was squashed into this single commit. The old commit hashes still exist as GitHub tags but are no longer reachable from any branch:
+
+- **v1.000** tag -> `abab94d19985f24132e45db4c4822b042eb63302` (initial release, 2024-03-19)
+- **v1.001** tag -> `88099a2e2d47e222cb62441730a2bc1c082754e1` (2024-04-30)
+- **v1.002** tag -> `4d4efe710065410b34b66fa9d588498351642f41` (2024-10-11)
+
+### Onboarding History in google/fonts
+
+The Pre variant had the most revisions in its PR before merge:
+
+1. **Initial onboarding**: Commit `598c0e2b` (2024-08-13, Simon Cozens) "Edu VIC WA NT Pre: Version 1.001 added". This commit added the font with commit hash `abab94d1` (v1.000 tag) and archive_url pointing to the v1.000 release. No explicit upstream commit reference in the commit message body.
+
+2. **Update quote spacing and kerning**: Commit `ac132fec` (2024-09-11, Simon Cozens) -- font binary update.
+
+3. **Update anchor positions**: Commit `8f0e4df5` (2024-09-27, Simon Cozens) -- font binary update.
+
+4. **PR merge**: PR #8022, merged 2024-10-02 by Emma Marichal. The final binary (1,298,364 bytes) differs from the initial onboarding (1,286,528 bytes), indicating the font was rebuilt with corrections between August and September 2024.
+
+5. **Batch update**: Commit `19cdcec5` (2025-03-31, Felipe Sanches) as part of "[Batch 1/4] port info from fontc_crater targets list" changed the commit hash from `abab94d1` (v1.000) to `6529c52` (current HEAD) and added `config_yaml: "sources/config.yaml"`.
+
+### Archive URL inconsistency
+
+The METADATA.pb currently references commit `6529c52` (post-squash HEAD) but the `archive_url` still points to the v1.000 release. However, the binary that was actually merged into google/fonts went through multiple rebuild iterations (quote spacing, anchor positions) in the PR, so it may not match the v1.000 release binary exactly. The final merged binary was likely built from a newer upstream state.
+
+### Commit hash accuracy concern
+
+The original METADATA.pb at onboarding used commit `abab94d1` (tag v1.000), but the font binary was updated twice within the PR (likely from newer upstream commits). The batch update changed the hash to `6529c52` (post-squash HEAD). Since the repo was force-pushed to squash history, `6529c52` is the only reachable commit.
+
+## Verification Summary
+
+| Field | Value | Status |
+|-------|-------|--------|
+| repository_url | https://github.com/SorkinType/VICWANTSchoolhandAustralia | Correct |
+| commit | 6529c525fceb9ec15e51dfa6d87244ef053c2d8a | Acceptable (post-squash HEAD; original was abab94d1 / v1.000) |
+| config_yaml | sources/config.yaml | Correct (exists in repo) |
+| archive_url | v1.000 release | May not match final merged binary (binary was updated in PR) |
+| branch | main | Correct |
+
+## Status
+
+- **Status**: complete
+- **Confidence**: HIGH
+- **Notes**: Source block is fully populated. The commit hash `6529c52` is the only commit in the (squashed) repo. The font binary went through multiple updates in PR #8022 (quote spacing, anchor positions) before merging. The archive_url still points to v1.000 which may not match the final binary. The config.yaml uses `fontprimer` recipe provider. No action needed.
--- /dev/null
+# Investigation Report: Edu NSW ACT Foundation
+
+## Summary
+
+| Field | Value |
+|-------|-------|
+| **Family Name** | Edu NSW ACT Foundation |
+| **Designer** | Tina Anderson, Corey Anderson |
+| **Category** | Handwriting |
+| **Date Added** | 2022-06-10 |
+| **Repository URL** | https://github.com/MezMerrit/AU-School-Handwriting-Fonts |
+| **Commit** | `0dbdee65c92d10e24e5d634719054f4f96b69133` |
+| **Config YAML** | `NSW-ACT-School-Fonts/sources/config.yaml` |
+| **Status** | needs_correction |
+| **Confidence** | HIGH |
+
+## Source Block Status
+
+The METADATA.pb already contains a `source {}` block, but it has an **incorrect `config_yaml` path**. The current value is:
+
+```
+config_yaml: "VIC-WA-NT-School-fonts/sources/config.yaml"
+```
+
+This points to the VIC WA NT Beginner config, which builds `EduVICWANTBeginner.glyphs`, not `EduNSWACTFoundation.glyphs`. The correct path should be:
+
+```
+config_yaml: "NSW-ACT-School-Fonts/sources/config.yaml"
+```
+
+The `NSW-ACT-School-Fonts/sources/config.yaml` file exists at commit `0dbdee6` and correctly references:
+```yaml
+sources:
+ - EduNSWACTFoundation.glyphs
+axisOrder:
+ - wght
+buildOTF: False
+familyName: Edu NSW ACT Foundation
+```
+
+## Upstream Repository
+
+- **Repository**: https://github.com/MezMerrit/AU-School-Handwriting-Fonts
+- **Cached at**: `MezMerrit/AU-School-Handwriting-Fonts`
+- **Status**: Clean, up to date with origin
+
+This is a monorepo containing all five Australian school handwriting font families:
+- `NSW-ACT-School-Fonts/` -- Edu NSW ACT Foundation
+- `QLD-School-Fonts/` -- Edu QLD Beginner
+- `SA-School-Fonts/` -- Edu SA Beginner
+- `TAS-School-Fonts/` -- Edu TAS Beginner
+- `VIC-WA-NT-School-fonts/` -- Edu VIC WA NT Beginner
+
+## Source Files
+
+At commit `0dbdee6`, the NSW ACT Foundation directory contains:
+- `NSW-ACT-School-Fonts/sources/EduNSWACTFoundation.glyphs` -- Glyphs source file
+- `NSW-ACT-School-Fonts/sources/config.yaml` -- gftools-builder config
+- `NSW-ACT-School-Fonts/sources/CustomFilterSet.plist`
+- `NSW-ACT-School-Fonts/fonts/variable/EduNSWACTFoundation[wght].ttf` -- Pre-built variable font
+
+Source format: **.glyphs** (Glyphs app format), variable font with `wght` axis (400-700).
+
+## Commit Verification
+
+The commit hash `0dbdee65c92d10e24e5d634719054f4f96b69133` ("Corrected vertical metrics", 2022-06-23) is **correct** for the current binary.
+
+### Version History in google/fonts
+
+1. **v1.001** -- PR #4761 (`6237c1316`, 2022-06-15): Initial onboarding from upstream commit `055799b` ("Update emails")
+2. **v1.002** -- PR #4823 (`506584e13`, 2022-06-22): Bulk update of all 5 families from upstream commit `8a71f27` ("Merge branch 'main'")
+3. **v1.003** -- PR #4831 (`536d37fd9`, 2022-06-23): Final update of all 5 families from upstream commit `0dbdee6` ("Corrected vertical metrics") -- **CURRENT**
+
+The v1.003 update was packaged by Rosalie Wagner using gftools-packager. All five families were updated together in a single PR, all referencing the same upstream commit `0dbdee6`.
+
+### Post-onboarding Upstream Changes
+
+After commit `0dbdee6`, the upstream repo has only had:
+- README updates
+- File cleanup (deleting dotted/outline variants)
+- Folder restructuring
+
+No source font files (`.glyphs`) were modified after the referenced commit.
+
+## Issues Found
+
+1. **WRONG config_yaml path**: The METADATA.pb `config_yaml` field points to `VIC-WA-NT-School-fonts/sources/config.yaml` instead of `NSW-ACT-School-Fonts/sources/config.yaml`. This was introduced by a "sources info" commit (`b9c8d846`, 2025-09-18) that incorrectly set the config path. The commit hash was correct, but the config_yaml path was wrong.
+
+## Recommended Fix
+
+Change the `config_yaml` field in the METADATA.pb source block from:
+```
+config_yaml: "VIC-WA-NT-School-fonts/sources/config.yaml"
+```
+to:
+```
+config_yaml: "NSW-ACT-School-Fonts/sources/config.yaml"
+```
+
+No other changes needed -- the repository_url, commit hash, files, and branch are all correct.
--- /dev/null
+# Investigation Report: Edu QLD Beginner
+
+## Summary
+
+| Field | Value |
+|-------|-------|
+| **Family Name** | Edu QLD Beginner |
+| **Designer** | Tina Anderson, Corey Anderson |
+| **Category** | Handwriting |
+| **Date Added** | 2022-06-22 |
+| **Repository URL** | https://github.com/MezMerrit/AU-School-Handwriting-Fonts |
+| **Commit** | `0dbdee65c92d10e24e5d634719054f4f96b69133` |
+| **Config YAML** | `QLD-School-Fonts/sources/config.yaml` |
+| **Status** | needs_correction |
+| **Confidence** | HIGH |
+
+## Source Block Status
+
+The METADATA.pb already contains a `source {}` block. The `config_yaml` path is correct (`QLD-School-Fonts/sources/config.yaml`), but the **commit hash is wrong**. The current value is:
+
+```
+commit: "1dd726bde8004743529cbeaab84ce993caf98f78"
+```
+
+This is the commit from the v1.002 update (PR #4824, "Passed Beginners to singular for consistency"), but the current font binary was updated to v1.003 in PR #4831, which used upstream commit `0dbdee6`. The correct commit should be:
+
+```
+commit: "0dbdee65c92d10e24e5d634719054f4f96b69133"
+```
+
+## Upstream Repository
+
+- **Repository**: https://github.com/MezMerrit/AU-School-Handwriting-Fonts
+- **Cached at**: `MezMerrit/AU-School-Handwriting-Fonts`
+- **Status**: Clean, up to date with origin
+
+This is a monorepo containing all five Australian school handwriting font families.
+
+## Source Files
+
+At commit `0dbdee6`, the QLD directory contains:
+- `QLD-School-Fonts/sources/EduQLDBeginner.glyphs` -- Glyphs source file
+- `QLD-School-Fonts/sources/config.yaml` -- gftools-builder config
+- `QLD-School-Fonts/sources/CustomFilterSet.plist`
+- `QLD-School-Fonts/fonts/variable/EduQLDBeginner[wght].ttf` -- Pre-built variable font
+
+Source format: **.glyphs** (Glyphs app format), variable font with `wght` axis (400-700).
+
+The config.yaml at this commit contains:
+```yaml
+sources:
+ - EduQLDBeginner.glyphs
+axisOrder:
+ - wght
+buildOTF: False
+familyName: Edu QLD Beginner
+```
+
+## Commit Verification
+
+The commit currently in METADATA.pb (`1dd726bde8004743529cbeaab84ce993caf98f78`, "Passed Beginners to singular for consistency", 2022-06-22) is **not the correct commit** for the current binary.
+
+### Version History in google/fonts
+
+1. **v1.002** -- PR #4824 (`9950d882`, 2022-06-22): QLD Beginner was onboarded separately from the other families at v1.002. This PR used upstream commit `1dd726b`.
+2. **v1.003** -- PR #4831 (`536d37fd9`, 2022-06-23): All five families updated together from upstream commit `0dbdee6` ("Corrected vertical metrics") -- **CURRENT**
+
+Note: QLD Beginner was NOT part of the initial v1.001 bulk onboarding. It was added later at v1.002 in a separate PR (#4824), then updated to v1.003 along with all other families.
+
+### How the Wrong Commit Was Set
+
+The PR #4831 (v1.003 update) originally set the correct commit `0dbdee6` in the source block. The April 2024 "Merge upstream.yaml into METADATA.pb" commit (`66f91f10f`) confirmed it still had `0dbdee6`. However, a "sources info" commit (`a2ec62f78`, 2025-09-18) incorrectly changed the commit from `0dbdee6` to `1dd726b` (referencing the earlier v1.002 PR #4824 instead of the current v1.003 PR #4831).
+
+### Post-onboarding Upstream Changes
+
+After commit `0dbdee6`, the upstream repo has only had README updates and file cleanup. No source font files were modified.
+
+## Issues Found
+
+1. **WRONG commit hash**: The METADATA.pb commit field points to `1dd726b` (v1.002 onboarding) instead of `0dbdee6` (v1.003 update, which is the current binary).
+
+## Recommended Fix
+
+Change the `commit` field in the METADATA.pb source block from:
+```
+commit: "1dd726bde8004743529cbeaab84ce993caf98f78"
+```
+to:
+```
+commit: "0dbdee65c92d10e24e5d634719054f4f96b69133"
+```
+
+No other changes needed -- the repository_url, config_yaml, files, and branch are all correct.
--- /dev/null
+# Investigation Report: Edu SA Beginner
+
+## Summary
+
+| Field | Value |
+|-------|-------|
+| **Family Name** | Edu SA Beginner |
+| **Designer** | Tina Anderson, Corey Anderson |
+| **Category** | Handwriting |
+| **Date Added** | 2022-06-10 |
+| **Repository URL** | https://github.com/MezMerrit/AU-School-Handwriting-Fonts |
+| **Commit** | `0dbdee65c92d10e24e5d634719054f4f96b69133` |
+| **Config YAML** | `SA-School-Fonts/sources/config.yaml` |
+| **Status** | needs_correction |
+| **Confidence** | HIGH |
+
+## Source Block Status
+
+The METADATA.pb already contains a `source {}` block. The `config_yaml` path is correct (`SA-School-Fonts/sources/config.yaml`), but the **commit hash is wrong**. The current value is:
+
+```
+commit: "055799b858017157b6138e59833ab5b1a8947bbd"
+```
+
+This is the commit from the v1.001 initial onboarding (PR #4763, "Update emails"), but the current font binary was updated through v1.002 (PR #4823) and then to v1.003 (PR #4831), which used upstream commit `0dbdee6`. The correct commit should be:
+
+```
+commit: "0dbdee65c92d10e24e5d634719054f4f96b69133"
+```
+
+## Upstream Repository
+
+- **Repository**: https://github.com/MezMerrit/AU-School-Handwriting-Fonts
+- **Cached at**: `MezMerrit/AU-School-Handwriting-Fonts`
+- **Status**: Clean, up to date with origin
+
+This is a monorepo containing all five Australian school handwriting font families.
+
+## Source Files
+
+At commit `0dbdee6`, the SA directory contains:
+- `SA-School-Fonts/sources/EduSABeginner.glyphs` -- Glyphs source file
+- `SA-School-Fonts/sources/config.yaml` -- gftools-builder config
+- `SA-School-Fonts/sources/CustomFilterSet.plist`
+- `SA-School-Fonts/fonts/variable/EduSABeginner[wght].ttf` -- Pre-built variable font
+
+Source format: **.glyphs** (Glyphs app format), variable font with `wght` axis (400-700).
+
+The config.yaml at this commit contains:
+```yaml
+sources:
+ - EduSABeginner.glyphs
+axisOrder:
+ - wght
+buildOTF: False
+familyName: Edu SA Beginner
+```
+
+## Commit Verification
+
+The commit currently in METADATA.pb (`055799b858017157b6138e59833ab5b1a8947bbd`, "Update emails", 2022-06-10) is **not the correct commit** for the current binary.
+
+### Version History in google/fonts
+
+1. **v1.001** -- PR #4763 (`d203a6ce1`, 2022-06-15): Initial onboarding from upstream commit `055799b` ("Update emails")
+2. **v1.002** -- PR #4823 (`506584e13`, 2022-06-22): Bulk update of all 5 families from upstream commit `8a71f27` ("Merge branch 'main'")
+3. **v1.003** -- PR #4831 (`536d37fd9`, 2022-06-23): Final update of all 5 families from upstream commit `0dbdee6` ("Corrected vertical metrics") -- **CURRENT**
+
+### How the Wrong Commit Was Set
+
+The PR #4831 (v1.003 update) originally set the correct commit `0dbdee6` in the source block. The April 2024 "Merge upstream.yaml into METADATA.pb" commit confirmed it still had `0dbdee6`. However, a "sources info" commit (`0370fcca9`, 2025-09-18) incorrectly changed the commit from `0dbdee6` to `055799b` (referencing the v1.001 initial onboarding PR #4763 instead of the current v1.003 PR #4831).
+
+### Post-onboarding Upstream Changes
+
+After commit `0dbdee6`, the upstream repo has only had README updates and file cleanup. No source font files were modified.
+
+## Issues Found
+
+1. **WRONG commit hash**: The METADATA.pb commit field points to `055799b` (v1.001 initial onboarding) instead of `0dbdee6` (v1.003 update, which is the current binary). This is two versions behind.
+
+## Recommended Fix
+
+Change the `commit` field in the METADATA.pb source block from:
+```
+commit: "055799b858017157b6138e59833ab5b1a8947bbd"
+```
+to:
+```
+commit: "0dbdee65c92d10e24e5d634719054f4f96b69133"
+```
+
+No other changes needed -- the repository_url, config_yaml, files, and branch are all correct.
--- /dev/null
+# Investigation Report: Edu TAS Beginner
+
+## Summary
+
+| Field | Value |
+|-------|-------|
+| **Family Name** | Edu TAS Beginner |
+| **Designer** | Tina Anderson, Corey Anderson |
+| **Category** | Handwriting |
+| **Date Added** | 2022-06-10 |
+| **Repository URL** | https://github.com/MezMerrit/AU-School-Handwriting-Fonts |
+| **Commit** | `0dbdee65c92d10e24e5d634719054f4f96b69133` |
+| **Config YAML** | `TAS-School-Fonts/sources/config.yaml` |
+| **Status** | needs_correction |
+| **Confidence** | HIGH |
+
+## Source Block Status
+
+The METADATA.pb already contains a `source {}` block. The `config_yaml` path is correct (`TAS-School-Fonts/sources/config.yaml`), but the **commit hash is wrong**. The current value is:
+
+```
+commit: "055799b858017157b6138e59833ab5b1a8947bbd"
+```
+
+This is the commit from the v1.001 initial onboarding (PR #4765, "Update emails"), but the current font binary was updated through v1.002 (PR #4823) and then to v1.003 (PR #4831), which used upstream commit `0dbdee6`. The correct commit should be:
+
+```
+commit: "0dbdee65c92d10e24e5d634719054f4f96b69133"
+```
+
+## Upstream Repository
+
+- **Repository**: https://github.com/MezMerrit/AU-School-Handwriting-Fonts
+- **Cached at**: `MezMerrit/AU-School-Handwriting-Fonts`
+- **Status**: Clean, up to date with origin
+
+This is a monorepo containing all five Australian school handwriting font families.
+
+## Source Files
+
+At commit `0dbdee6`, the TAS directory contains:
+- `TAS-School-Fonts/sources/EduTASBeginner.glyphs` -- Glyphs source file
+- `TAS-School-Fonts/sources/config.yaml` -- gftools-builder config
+- `TAS-School-Fonts/sources/CustomFilterSet.plist`
+- `TAS-School-Fonts/fonts/variable/EduTASBeginner[wght].ttf` -- Pre-built variable font
+
+Source format: **.glyphs** (Glyphs app format), variable font with `wght` axis (400-700).
+
+The config.yaml at this commit contains:
+```yaml
+sources:
+ - EduTASBeginner.glyphs
+axisOrder:
+ - wght
+buildOTF: False
+familyName: Edu TAS Beginner
+```
+
+## Commit Verification
+
+The commit currently in METADATA.pb (`055799b858017157b6138e59833ab5b1a8947bbd`, "Update emails", 2022-06-10) is **not the correct commit** for the current binary.
+
+### Version History in google/fonts
+
+1. **v1.001** -- PR #4765 (`64b1a836`, 2022-06-15): Initial onboarding from upstream commit `055799b` ("Update emails")
+2. **v1.002** -- PR #4823 (`506584e13`, 2022-06-22): Bulk update of all 5 families from upstream commit `8a71f27` ("Merge branch 'main'"). Note: TAS Beginner was actually updated twice in this PR -- first from `8a71f27`, then from `80ca0a0` ("Corrected TAS UPM").
+3. **v1.003** -- PR #4831 (`536d37fd9`, 2022-06-23): Final update of all 5 families from upstream commit `0dbdee6` ("Corrected vertical metrics") -- **CURRENT**
+
+### How the Wrong Commit Was Set
+
+The PR #4831 (v1.003 update) originally set the correct commit `0dbdee6` in the source block. The April 2024 "Merge upstream.yaml into METADATA.pb" commit confirmed it still had `0dbdee6`. However, a "sources info" commit (`265283482`, 2025-09-18) incorrectly changed the commit from `0dbdee6` to `055799b` (referencing the v1.001 initial onboarding PR #4765 instead of the current v1.003 PR #4831).
+
+### Post-onboarding Upstream Changes
+
+After commit `0dbdee6`, the upstream repo has only had README updates and file cleanup. No source font files were modified.
+
+## Issues Found
+
+1. **WRONG commit hash**: The METADATA.pb commit field points to `055799b` (v1.001 initial onboarding) instead of `0dbdee6` (v1.003 update, which is the current binary). This is two versions behind.
+
+## Recommended Fix
+
+Change the `commit` field in the METADATA.pb source block from:
+```
+commit: "055799b858017157b6138e59833ab5b1a8947bbd"
+```
+to:
+```
+commit: "0dbdee65c92d10e24e5d634719054f4f96b69133"
+```
+
+No other changes needed -- the repository_url, config_yaml, files, and branch are all correct.
--- /dev/null
+# Investigation Report: Edu VIC WA NT Beginner
+
+## Summary
+
+| Field | Value |
+|-------|-------|
+| **Family Name** | Edu VIC WA NT Beginner |
+| **Designer** | Tina Anderson, Corey Anderson |
+| **Category** | Handwriting |
+| **Date Added** | 2022-06-10 |
+| **Repository URL** | https://github.com/MezMerrit/AU-School-Handwriting-Fonts |
+| **Commit** | `0dbdee65c92d10e24e5d634719054f4f96b69133` |
+| **Config YAML** | `VIC-WA-NT-School-fonts/sources/config.yaml` |
+| **Status** | needs_correction |
+| **Confidence** | HIGH |
+
+## Source Block Status
+
+The METADATA.pb already contains a `source {}` block. The `config_yaml` path is correct (`VIC-WA-NT-School-fonts/sources/config.yaml`), but the **commit hash is wrong**. The current value is:
+
+```
+commit: "055799b858017157b6138e59833ab5b1a8947bbd"
+```
+
+This is the commit from the v1.001 initial onboarding (PR #4766, "Update emails"), but the current font binary was updated through v1.002 (PR #4823) and then to v1.003 (PR #4831), which used upstream commit `0dbdee6`. The correct commit should be:
+
+```
+commit: "0dbdee65c92d10e24e5d634719054f4f96b69133"
+```
+
+## Upstream Repository
+
+- **Repository**: https://github.com/MezMerrit/AU-School-Handwriting-Fonts
+- **Cached at**: `MezMerrit/AU-School-Handwriting-Fonts`
+- **Status**: Clean, up to date with origin
+
+This is a monorepo containing all five Australian school handwriting font families.
+
+## Source Files
+
+At commit `0dbdee6`, the VIC WA NT directory contains:
+- `VIC-WA-NT-School-fonts/sources/EduVICWANTBeginner.glyphs` -- Glyphs source file
+- `VIC-WA-NT-School-fonts/sources/config.yaml` -- gftools-builder config
+- `VIC-WA-NT-School-fonts/sources/CustomFilterSet.plist`
+- `VIC-WA-NT-School-fonts/fonts/variable/EduVICWANTBeginner[wght].ttf` -- Pre-built variable font
+
+Source format: **.glyphs** (Glyphs app format), variable font with `wght` axis (400-700).
+
+The config.yaml at this commit contains:
+```yaml
+sources:
+ - EduVICWANTBeginner.glyphs
+axisOrder:
+ - wght
+buildOTF: False
+familyName: Edu VIC WA NT Beginner
+```
+
+## Commit Verification
+
+The commit currently in METADATA.pb (`055799b858017157b6138e59833ab5b1a8947bbd`, "Update emails", 2022-06-10) is **not the correct commit** for the current binary.
+
+### Version History in google/fonts
+
+1. **v1.001** -- PR #4766 (`604f5fec5`, 2022-06-15): Initial onboarding from upstream commit `055799b` ("Update emails")
+2. **v1.002** -- PR #4823 (`506584e13`, 2022-06-22): Bulk update of all 5 families from upstream commit `8a71f27` ("Merge branch 'main'")
+3. **v1.003** -- PR #4831 (`536d37fd9`, 2022-06-23): Final update of all 5 families from upstream commit `0dbdee6` ("Corrected vertical metrics") -- **CURRENT**
+
+### How the Wrong Commit Was Set
+
+The PR #4831 (v1.003 update) originally set the correct commit `0dbdee6` in the source block. The April 2024 "Merge upstream.yaml into METADATA.pb" commit confirmed it still had `0dbdee6`. However, "sources info" commits (`db90ef439` and `308cb29c9`, 2025-09-24) incorrectly changed the commit from `0dbdee6` to `055799b` (referencing the v1.001 initial onboarding PR #4766 instead of the current v1.003 PR #4831).
+
+### Post-onboarding Upstream Changes
+
+After commit `0dbdee6`, the upstream repo has only had README updates and file cleanup. No source font files were modified.
+
+## Issues Found
+
+1. **WRONG commit hash**: The METADATA.pb commit field points to `055799b` (v1.001 initial onboarding) instead of `0dbdee6` (v1.003 update, which is the current binary). This is two versions behind.
+
+## Recommended Fix
+
+Change the `commit` field in the METADATA.pb source block from:
+```
+commit: "055799b858017157b6138e59833ab5b1a8947bbd"
+```
+to:
+```
+commit: "0dbdee65c92d10e24e5d634719054f4f96b69133"
+```
+
+No other changes needed -- the repository_url, config_yaml, files, and branch are all correct.
--- /dev/null
+# El Messiri
+
+**Date investigated**: 2026-02-27
+**Status**: complete
+**Designer**: Mohamed Gaber, Jovanny Lemonad
+**METADATA.pb path**: `ofl/elmessiri/METADATA.pb`
+
+## Source Data
+
+| Field | Value |
+|-------|-------|
+| Repository URL | https://github.com/Gue3bara/El-Messiri |
+| Commit | `553b98d8e374318694b50862849af666268fd278` |
+| Config YAML | `sources/config.yaml` |
+| Branch | `master` |
+
+## How the Repository URL Was Found
+
+The repository URL `https://github.com/Gue3bara/El-Messiri` was already present in the METADATA.pb `source { repository_url }` field. It is corroborated by multiple sources:
+
+1. The copyright string in the font: "Copyright 2015 The El Messiri Project Authors (https://github.com/Gue3bara/El-Messiri)"
+2. The gftools-packager commit `a1b41d3a8` in google/fonts (PR #3673, 2021-08-06) explicitly states: "El Messiri Version 2.020 taken from the upstream repo https://github.com/Gue3bara/El-Messiri"
+3. The `upstream.yaml` file created during onboarding references the same URL
+4. The DESCRIPTION.en_us.html links to the same repository
+
+The repository is owned by Mohamed Gaber (GitHub: Gue3bara), the lead designer of the typeface.
+
+## How the Commit Hash Was Identified
+
+The commit hash `553b98d8e374318694b50862849af666268fd278` is explicitly cited in the gftools-packager commit message of PR #3673 (google/fonts commit `a1b41d3a8`, authored by Rosalie Wagner on 2021-08-06): "El Messiri Version 2.020 taken from the upstream repo https://github.com/Gue3bara/El-Messiri at commit https://github.com/Gue3bara/El-Messiri/commit/553b98d8e374318694b50862849af666268fd278."
+
+This commit exists in the upstream repo and is a merge commit: "Merge pull request #23 from eliheuer/gf-bugfix-2021" (Google Fonts bugfixes 2021), dated 2021-08-06 09:52:27 +0200. The google/fonts commit was made the same day (2021-08-06 14:47:22 +0200), confirming the timeline is consistent.
+
+Binary verification confirms the match: the `fonts/variable/ElMessiri[wght].ttf` file at this upstream commit has an identical MD5 checksum (`7fd7b06b35a99518599c32b5f4c9ecb9`) to the file in `ofl/elmessiri/ElMessiri[wght].ttf` in google/fonts. Both files are 138,664 bytes.
+
+This commit is also the latest (and HEAD) commit on the `master` branch. No additional commits have been made to the upstream repo since this onboarding.
+
+## How Config YAML Was Resolved
+
+The config file `sources/config.yaml` exists in the upstream repository at the recorded commit. It contains gftools-builder configuration:
+
+- Source: `ElMessiri.glyphs`
+- Axis order: `wght`
+- Family name: "El Messiri"
+- STAT table definitions for the weight axis (Regular 400, Medium 500, SemiBold 600, Bold 700)
+
+No override `config.yaml` exists in the google/fonts family directory (`ofl/elmessiri/`).
+
+## Verification
+
+- Repository URL accessible: Yes
+- Commit exists in upstream repo: Yes
+- Commit is HEAD of master: Yes
+- Commit date: 2021-08-06 09:52:27 +0200
+- Commit message: "Merge pull request #23 from eliheuer/gf-bugfix-2021"
+- Binary file match: Yes (identical MD5 checksum, 138,664 bytes)
+- Source files at commit: `sources/ElMessiri.glyphs`, `sources/config.yaml`
+- Config YAML valid: Yes
+- No newer upstream commits: Confirmed
+
+## Confidence
+
+**HIGH**: All metadata fields are fully verified. The repository URL is corroborated by the copyright string, PR history, and upstream.yaml. The commit hash is explicitly cited in the gftools-packager message and verified by identical binary checksums. The config.yaml is present at the recorded path with valid gftools-builder configuration. The referenced commit is the HEAD of master, with no subsequent changes.
+
+## Open Questions
+
+None. All source metadata is complete and verified.
--- /dev/null
+# Investigation Report: Elms Sans
+
+## Family Overview
+- **Family Name**: Elms Sans
+- **Designer**: Amarachi Nwauwa, Gida Type Studio
+- **License**: OFL
+- **Date Added**: 2025-10-17
+- **Category**: Sans Serif
+- **Axes**: wght (100-900)
+- **Files**: ElmsSans[wght].ttf, ElmsSans-Italic[wght].ttf (variable fonts)
+
+## Source Repository
+- **Repository URL**: https://github.com/mara-aa/elms-sans
+- **Commit**: `bc5a52f3499f1a9858e56430da9e955c15366b3e`
+- **Branch**: main
+- **Config YAML**: `sources/config.yaml`
+
+## METADATA.pb Status
+The METADATA.pb already has a complete `source { }` block with:
+- `repository_url`: https://github.com/mara-aa/elms-sans
+- `commit`: bc5a52f3499f1a9858e56430da9e955c15366b3e
+- `branch`: main
+- `config_yaml`: sources/config.yaml
+- `files` mappings for OFL.txt, ElmsSans[wght].ttf, and ElmsSans-Italic[wght].ttf
+
+## Investigation Details
+
+### Onboarding History in google/fonts
+The font was onboarded via PR #9925, with the following commits in google/fonts:
+
+1. **a6d580b2** (2025-10-17) by Emma Marichal -- "Elms Sans: Version 1.061 added"
+ - Commit message explicitly states: "Taken from the upstream repo https://github.com/mara-aa/elms-sans at commit bc5a52f3499f1a9858e56430da9e955c15366b3e"
+ - Added font binaries, METADATA.pb, OFL.txt, and article
+2. **d3599724** (2025-10-17) -- "add article" (article images/videos)
+3. **c323e702** (2025-10-22) by Felipe Sanches -- "sources info for Elms Sans: Version 1.061 (PR #9925)" (added config_yaml to METADATA.pb)
+4. **b5a3b571** (2025-11-07) -- "add Gida Type Studio in designers"
+
+### Upstream Repository Analysis
+- The upstream repo at `mara-aa/elms-sans` has only a single commit: `bc5a52f` (a merge commit from PR #6 by emmamarichal, dated 2025-10-16)
+- This merge commit is titled "Update to QA, Fixes & Font Build" and contains the entire repository content (initial setup using the Google Fonts template)
+- The repo is clean and up-to-date with origin
+
+### Commit Hash Verification
+- **Binary file comparison**: SHA256 hashes of both `ElmsSans[wght].ttf` and `ElmsSans-Italic[wght].ttf` match exactly between the upstream repo at commit `bc5a52f` and google/fonts
+ - ElmsSans[wght].ttf: `5a5c6aca186c65ad8323212c4e336507e68f4ee09d75ae0366607b5eb1a4498f`
+ - ElmsSans-Italic[wght].ttf: `bc485f45f3090748e540223fe29f44bed69b67c7311a3f984dffa5295713a017`
+- The commit hash is confirmed correct
+
+### Source Files
+- **Source format**: Glyphs 3 (.glyphs file) -- `sources/ElmsSans.glyphs` (appVersion 3428, formatVersion 3)
+- **Config YAML**: `sources/config.yaml` exists in the upstream repo at the referenced commit
+ - Sources: ElmsSans.glyphs
+ - familyName: Elms Sans
+ - cleanUp: true
+ - splitItalic: true (Roman and Italic variable fonts are split from a single source)
+ - Full STAT table configuration for wght (100-900) and ital axes
+- **Additional source files**: `sources/CustomFilter_GF_Latin_All.plist`
+- **No override config.yaml** in the google/fonts family directory
+
+## Status
+- **Status**: Complete
+- **Confidence**: HIGH
+- **All source metadata is present and verified**
+
+No action needed. The METADATA.pb source block is complete with verified repository URL, commit hash, branch, config_yaml path, and file mappings. Binary files match the referenced commit exactly.
--- /dev/null
+# Investigation Report: Englebert
+
+## Source Data
+
+| Field | Value |
+|--------------------|-------|
+| Family Name | Englebert |
+| Designer | Astigmatic (Brian J. Bonislawsky) |
+| License | OFL |
+| Date Added | 2012-11-02 |
+| Repository URL | https://github.com/librefonts/englebert |
+| Commit Hash | `0b03ab09eab75a39c93f8fb0432459a7dca74176` |
+| Branch | master |
+| Config YAML | Override `config.yaml` in google/fonts |
+| Source Types | VFB (FontLab Studio) |
+| Status | complete |
+| Confidence | HIGH |
+
+## How Repository URL Was Found
+
+The repository URL `https://github.com/librefonts/englebert` was already present in the METADATA.pb source block. It was added by Simon Cozens in commit `c8a4f855` ("More upstreams (e,f)", 2024-01-14). The URL is also referenced in:
+
+- The copyright notice in METADATA.pb: `Copyright 2012 The Englebert Project Authors (https://github.com/librefonts/englebert)`
+- The DESCRIPTION.en_us.html file, which links to the same repository
+- The repository is accessible on GitHub under the `librefonts` organization
+
+The repository was created by Mikhail Kashkin (hash3g) on 2014-07-16 with the commit message "Move englebert font files to separate repository", indicating it was migrated from a larger collection into its own repo as part of the librefonts organization.
+
+## How Commit Hash Was Identified
+
+The commit hash `0b03ab09eab75a39c93f8fb0432459a7dca74176` was added to METADATA.pb by a prior investigation (commit `e8c781a6`, "sources info for Englebert v1.010 (PR #8688)", 2025-10-30). This hash is the HEAD of the upstream repository's `master` branch and represents the latest commit (dated 2014-10-17, "update .travis.yml").
+
+**Verification**: The upstream repository has only 12 commits total. All commits after the initial one (`3e3caf6`, 2014-07-16) are CI/Travis configuration changes only. A diff of the `src/` directory between the initial commit and HEAD shows no source file changes (only a file mode permission change on `src/METADATA_comments.txt`). The three VFB source files have been unchanged since the repository was created.
+
+Since the source files never changed, this commit hash is effectively equivalent to any other commit in the repository for the purpose of identifying the sources. Using HEAD (`0b03ab0`) is acceptable and correct.
+
+## How Config YAML Was Resolved
+
+The upstream repository has **no** `config.yaml` file. The source files are exclusively in VFB format (FontLab Studio binary):
+
+- `src/Englebert-Regular.vfb` — Original source with contour overlaps
+- `src/Englebert-Regular-TTF.vfb` — TrueType outlines with hinting adjustments
+- `src/Englebert-Regular-OTF.vfb` — Merged contours and optimized for OTF
+
+An override `config.yaml` already exists in the google/fonts family directory (`ofl/englebert/config.yaml`), added in commit `e8c781a6` (2025-10-30). It contains:
+
+```yaml
+buildVariable: false
+sources:
+ - src/Englebert-Regular.vfb
+ - src/Englebert-Regular-TTF.vfb
+ - src/Englebert-Regular-OTF.vfb
+```
+
+**Note on VFB sources**: VFB is a proprietary FontLab Studio format. While gftools-builder lists VFB as a potential input, practical support may be limited. The current font binary in google/fonts was NOT built using gftools-builder from these VFB sources. Instead, the font was originally onboarded as a pre-built binary and later hotfixed (binary patched) by Emma Marichal in PR #8688 to fix v-metrics issues (see issue #8679).
+
+Since the `config_yaml` field is omitted from the METADATA.pb source block (as per policy, google-fonts-sources auto-detects local override config files), this is correctly configured.
+
+## Verification
+
+### Repository Accessibility
+- GitHub URL verified accessible: `librefonts/englebert`, default branch `master`
+- Last pushed: 2014-10-17 (no activity in over 10 years)
+
+### Source Block in METADATA.pb
+The current source block contains:
+```
+source {
+ repository_url: "https://github.com/librefonts/englebert"
+ commit: "0b03ab09eab75a39c93f8fb0432459a7dca74176"
+}
+```
+This is correct and complete. The `config_yaml` field is intentionally omitted because an override config exists locally.
+
+### Font Binary History
+The font binary in google/fonts has been modified three times:
+1. **2015-03-07** (`90abd17b`) — Initial commit (the original v1.000 binary)
+2. **2024-12-04** (`05636835`) — Hotfixed v-metrics by Emma Marichal (PR #8688)
+3. **2024-12-12** (`b7f6aa92`) — Name table updated (copyright) by Emma Marichal (PR #8688)
+
+The current binary (v1.010) was hotfixed directly, not rebuilt from the VFB sources. The original v1.000 binary predates the upstream repository (added to Google Fonts 2012-11-02, upstream repo created 2014-07-16).
+
+### Upstream Repository Cache
+The repository is cloned at `upstream_repos/fontc_crater_cache/librefonts/englebert/` and is clean with no local modifications.
+
+## Confidence
+
+**HIGH** — The repository URL is confirmed through multiple sources (METADATA.pb copyright, DESCRIPTION.en_us.html, GitHub). The commit hash points to the HEAD of the upstream repo, which is appropriate since no source files changed across any commits. An override config.yaml is already in place in google/fonts. The source block is complete and correctly configured.
+
+## Additional Notes
+
+- The font was designed by Brian J. Bonislawsky (Astigmatic) and released in November 2012
+- The upstream repository was created as part of the librefonts organization by Mikhail Kashkin, migrating fonts from a larger collection
+- PR #8688 was a hotfix to address bad line spacing (v-metrics) reported in issue #8679, merged by Viviana Monsalve on 2024-12-12
+- The FONTLOG.txt in the upstream repo documents all three VFB source variants and their purposes
--- /dev/null
+# Investigation Report: Enriqueta
+
+## Family Details
+
+- **Family name**: Enriqueta
+- **Designer**: FontFuror (Viviana Monsalve & Gustavo Ibarra)
+- **License**: OFL
+- **Category**: SERIF
+- **Date added**: 2011-12-13
+- **Styles**: Regular (400), Medium (500), SemiBold (600), Bold (700)
+- **Path in google/fonts**: `ofl/enriqueta/`
+
+## Repository URL
+
+- **URL**: https://github.com/vv-monsalve/Enriqueta_2019
+- **Source**: METADATA.pb `source {}` block, added by Simon Cozens in commit `cd5db6b6e` ("Update upstreams", 2023-12-14)
+- **Confirmed by**: PR #1933 body and commit message both explicitly reference this repo
+- **Status**: Valid, accessible, repo is clean and up-to-date in cache at `upstream_repos/fontc_crater_cache/vv-monsalve/Enriqueta_2019/`
+
+## Commit Hash
+
+- **Commit**: `c1dbf07dd69dc7146e073a549810166587c65de3`
+- **Date**: 2019-04-10
+- **Message**: "Merge pull request #1 from m4rc1e/gf-mastering" -- merges Marc Foley's "v2.000 mastered for Google Fonts" PR into the upstream repo
+- **Source of hash**: Explicitly stated in both the google/fonts commit message (`58c23711f`) and the PR #1933 body: "Taken from the upstream repo https://github.com/vv-monsalve/Enriqueta_2019 at commit c1dbf07dd69dc7146e073a549810166587c65de3"
+- **Confidence**: HIGH
+
+### Cross-verification
+
+The binary font files in google/fonts (74K each) are **larger** than the fonts stored in the upstream repo at commit `c1dbf07` (71K each). This indicates Marc Foley rebuilt the fonts from the `.glyphs` source file (using Google Fonts tooling which adds metadata like `DSIG`, `GDEF`, etc.) rather than simply copying the pre-built TTFs from the upstream `fonts/` directory. This is normal onboarding behavior -- the commit hash references the source state, not necessarily a binary match.
+
+### Post-onboarding upstream changes
+
+After commit `c1dbf07` (2019-04-10), the upstream repo had further activity:
+- 2019-04-10: Deleted `fonts/text` file
+- 2019-04-20: Renamed source file from `enriqueta_masters_-GOOGLE.glyphs` to `enriqueta_masters_GOOGLE.glyphs` (removed dash), added AUTHORS.txt and CONTRIBUTORS.txt, uploaded new source file
+- 2019-04-23: Deleted the TTF files from the `fonts/` directory (cleanup)
+- 2019-08-07: Updated OFL.txt (PR #2, branch `qavv5`)
+
+These post-onboarding changes did NOT affect the source design itself (the `.glyphs` file was re-uploaded with a name fix, not content changes), so the commit hash `c1dbf07` accurately represents the design state used for onboarding.
+
+## Build Configuration
+
+- **Upstream config.yaml**: None. The upstream repo has no `config.yaml` file.
+- **Override config.yaml in google/fonts**: Yes, exists at `ofl/enriqueta/config.yaml`
+ - Added in commit `5ddf312e6` ("Add config_yaml enrichment for 82 font families", 2026-02-20)
+ - Contents: `sources: [source/enriqueta_masters_GOOGLE.glyphs]`
+ - **Note**: This references the **current** filename (without dash). At the onboarding commit `c1dbf07`, the file was named `enriqueta_masters_-GOOGLE.glyphs` (with dash). The override config uses the current HEAD filename, which is appropriate for building from the latest upstream state.
+- **config_yaml field in METADATA.pb**: Not set (correctly omitted since override config exists in google/fonts, and google-fonts-sources auto-detects it)
+
+## Source Files
+
+At the onboarding commit `c1dbf07`:
+- `source/enriqueta_masters_-GOOGLE.glyphs` -- Glyphs source file (note the dash in the name)
+- `fonts/Enriqueta-{Regular,Medium,SemiBold,Bold}.ttf` -- Pre-built TTFs
+
+At HEAD (`b089cc3`):
+- `source/enriqueta_masters_GOOGLE.glyphs` -- Glyphs source file (dash removed from name)
+- No pre-built TTFs (deleted in April 2019 cleanup)
+
+## google/fonts History
+
+| Commit | Date | Author | Description |
+|--------|------|--------|-------------|
+| `90abd17b4` | 2015-03-07 | Initial | Initial commit (Regular + Bold only) |
+| `58c23711f` | 2019-04-10 | Marc Foley | v2.000 added (4 styles, from upstream `c1dbf07`) |
+| `f113126dc` | 2019-07-12 | Marc Foley | Merge PR #1933 |
+| `cd5db6b6e` | 2023-12-14 | Simon Cozens | Added `source { repository_url }` to METADATA.pb |
+| `5ddf312e6` | 2026-02-20 | Felipe Sanches | Added override `config.yaml` |
+
+## PR History
+
+- **PR #1933** (google/fonts): "enriqueta: v2.000 added." by Marc Foley (@m4rc1e), merged 2019-07-12. Body explicitly states the upstream repo and commit hash.
+- **PR #1** (upstream): "v2.000 mastered for Google Fonts" by Marc Foley, merged into vv-monsalve/Enriqueta_2019 on 2019-04-10. This is the commit referenced for onboarding.
+
+## METADATA.pb Source Block
+
+Current state:
+```
+source {
+ repository_url: "https://github.com/vv-monsalve/Enriqueta_2019"
+}
+```
+
+Recommended complete state:
+```
+source {
+ repository_url: "https://github.com/vv-monsalve/Enriqueta_2019"
+ commit: "c1dbf07dd69dc7146e073a549810166587c65de3"
+}
+```
+
+Note: `config_yaml` field should remain omitted because the override `config.yaml` in google/fonts is auto-detected.
+
+## Status
+
+- **Status**: complete (pending commit hash addition to METADATA.pb)
+- **Confidence**: HIGH
+- **What's needed**: Add `commit: "c1dbf07dd69dc7146e073a549810166587c65de3"` to the source block in METADATA.pb
+- **Override config**: Already in place at `ofl/enriqueta/config.yaml`
projects / thirdparty / google / fonts.git / commitdiff
