--- /dev/null
+# Investigation Report: Homemade Apple
+
+## Summary
+
+Homemade Apple is a handwriting/display font designed by Font Diner, licensed under Apache 2.0. It was initially added to google/fonts in the 2015 "Initial commit" and received a hotfix update in 2017 (PR #776). The upstream repository at `https://github.com/librefonts/homemadeapple` contains only TTX-decomposed font tables and no buildable source files (.glyphs, .ufo, .designspace, .sfd, or .vfb). The font has no source block in METADATA.pb and no config.yaml. Since the upstream repo contains no compilable sources, a config.yaml cannot be created.
+
+## Key Findings
+
+| Field | Value |
+|--------------------|----------------------------------------------------|
+| Family Name | Homemade Apple |
+| Designer | Font Diner |
+| License | Apache 2.0 |
+| Directory | apache/homemadeapple |
+| Repository URL | https://github.com/librefonts/homemadeapple |
+| Onboarding Commit | N/A (no buildable sources in upstream) |
+| Config YAML | None (no compilable sources) |
+| Status | **no_config_possible** |
+| Confidence | HIGH |
+
+## Investigation Details
+
+### METADATA.pb Analysis
+
+The METADATA.pb file at `apache/homemadeapple/METADATA.pb` has no `source { }` block. The font was added on 2011-01-06 and is categorized as HANDWRITING and DISPLAY.
+
+### Git History in google/fonts
+
+The font file `HomemadeApple-Regular.ttf` has only one modifying commit:
+
+1. **8e94f9c12** (2017-08-07) by Marc Foley: "hotfix-homemadeapple: v1.001 added (#776)"
+ - Renamed `HomemadeApple.ttf` to `HomemadeApple-Regular.ttf`
+ - Updated METADATA.pb fields (filename, post_script_name, full_name, copyright)
+ - Updated DESCRIPTION.en_us.html
+
+The original addition was in the "Initial commit" (90abd17b4, 2015-03-07) by Dave Crossland.
+
+### Upstream Repository Analysis
+
+The cached repository at `librefonts/homemadeapple` (remote: `https://github.com/librefonts/homemadeapple`) contains:
+
+- **1 commit total**: `5159ae2` (2014-10-17) "update .travis.yml"
+- **Files**: TTX-decomposed font tables (HomemadeApple.ttf.*.ttx), LICENSE.txt, COPYRIGHT.txt, DESCRIPTION.en_us.html, METADATA.json
+- **src/ directory**: Contains only `VERSIONS.txt` (records "HomemadeApple.ttf: Version 1.000") and an empty `METADATA_comments.txt`
+- **No buildable sources**: No .glyphs, .ufo, .designspace, .sfd, or .vfb files found anywhere in the repository
+
+The repository is a legacy `librefonts` mirror containing TTX decompositions rather than actual design sources. This is consistent with early Google Fonts onboarding practices where some fonts were contributed as pre-compiled binaries without editable sources.
+
+### Font Diner Context
+
+Font Diner is a commercial foundry. The font was contributed under the Apache 2.0 license. The original design sources (likely proprietary format) were never made publicly available.
+
+## Conclusion
+
+**Status: no_config_possible**
+
+Homemade Apple has an upstream repository at `https://github.com/librefonts/homemadeapple`, but it contains only TTX decompositions of the compiled font, not editable design sources. No config.yaml can be created because there are no compilable source files (.glyphs, .ufo, .designspace) from which to build the font. The font is licensed under Apache 2.0 (not OFL) and resides in `apache/homemadeapple` rather than `ofl/`. This family is not currently tracked in `data/gfonts_library_sources.json` as the tracking system currently covers only OFL-licensed fonts.
+
+A source block could theoretically be added to METADATA.pb pointing to the librefonts repo, but without buildable sources, the `config_yaml` field cannot be populated. The repository URL could still be documented for reference purposes.
--- /dev/null
+# Investigation: Irish Grover
+
+## Summary
+
+| Field | Value |
+|-------|-------|
+| Family Name | Irish Grover |
+| Slug | irish-grover |
+| License Dir | apache |
+| Repository URL | unknown |
+| Commit Hash | unknown |
+| Config YAML | unknown |
+| Status | missing_url |
+| Confidence | LOW |
+
+## Source Data (METADATA.pb)
+
+```
+No source block
+```
+
+## Investigation
+
+The font is stored under `apache/irishgrover/` with an Apache 2.0 license. The METADATA.pb has no `source` block at all.
+
+The font history in google/fonts shows:
+- `90abd17b4` — "Initial commit" — the font was present from the very beginning of the google/fonts repository
+- `daa6505c6` — "hotfix-irishgrover: v1.001 added (#777)" — a hotfix that renamed the file from `IrishGrover.ttf` to `IrishGrover-Regular.ttf`
+
+The copyright in METADATA.pb states: "Copyright (c) 2010 by Font Diner, Inc DBA Sideshow. All rights reserved."
+
+The DESCRIPTION.en_us.html says:
+> "Presenting Irish Grover! No, it's not a coveted new AKC breed. No, it's not a tasty seasonal pilsner. It's a fun, flamboyant, new display font by Squid that's way better than any of those possibilities. Sure and it's free for Pete's sake! And you can't say that about dogs or beer."
+
+The designer is listed as "Sideshow" (Font Diner, Inc DBA Sideshow). Font Diner is a commercial type foundry; this font was donated to Google Fonts under Apache license. No GitHub repository has been identified for the upstream source. The font dates to 2010 and was contributed directly to Google Fonts without a tracked upstream repository.
+
+No cached upstream repository was found in `upstream_repos/fontc_crater_cache/` for this family.
+
+Given the Apache license and the vintage of the font (2010), it is likely that there is no open-source upstream repository. The font was contributed directly to Google Fonts by Font Diner/Sideshow.
+
+## Conclusion
+
+No upstream repository is known for this font. The font was contributed directly to google/fonts under Apache 2.0 license by Font Diner Inc / Sideshow. Investigation into Font Diner's website or archives may reveal source files, but there is likely no publicly accessible upstream repository. This font may be a case where `no_config_possible` applies due to the commercial foundry origin and lack of open source repository.
+
+Action needed: Determine if Font Diner/Sideshow has a public source repository or if this font was contributed as binaries only. If no upstream repo exists, document as `missing_url` with a note that no upstream repository was found.
--- /dev/null
+# Investigation Report: Homenaje
+
+## Summary
+
+Homenaje is a sans-serif font designed by Constanza Artigas Preller and Agustina Mingote, licensed under OFL. The upstream repository at `https://github.com/googlefonts/Homenaje` contains a single commit (d371ad8, 2025-02-24) by Felipe Sanches that set up the entire repo including a converted .glyphs source and config.yaml. The METADATA.pb source block is complete with repository_url, commit hash, and config_yaml path. The original v1.002 sources (VFB/SFD format) are preserved in the repo's `old/` directory.
+
+## Key Findings
+
+| Field | Value |
+|--------------------|----------------------------------------------------|
+| Family Name | Homenaje |
+| Designer | Constanza Artigas Preller, Agustina Mingote |
+| License | OFL |
+| Directory | ofl/homenaje |
+| Repository URL | https://github.com/googlefonts/Homenaje |
+| Commit Hash | d371ad8e2f096db1f866c8fdfb9804f90dc39453 |
+| Config YAML | sources/config.yaml |
+| Status | **complete** |
+| Confidence | HIGH |
+
+## Investigation Details
+
+### METADATA.pb Analysis
+
+The METADATA.pb at `ofl/homenaje/METADATA.pb` has a complete source block:
+
+```
+source {
+ repository_url: "https://github.com/googlefonts/Homenaje"
+ commit: "d371ad8e2f096db1f866c8fdfb9804f90dc39453"
+ config_yaml: "sources/config.yaml"
+}
+```
+
+The font was added on 2012-01-18 and the copyright references the Homenaje Project Authors with RFN.
+
+### Git History in google/fonts
+
+Key commits affecting the font binary:
+
+1. **90abd17b4** (2015-03-07) by Dave Crossland: "Initial commit" -- original addition
+2. **fbcc9a513** (2016-12-02) by Marc Foley: "homenaje: v1.100 added (#458)" -- updated the .ttf from 22,192 to 36,436 bytes, updated copyright, inherited vertical metrics
+
+Source block history:
+1. **2423d2aef** (2023-12-14) by Simon Cozens: "Update upstreams" -- added initial `source { repository_url }` block
+2. **19cdcec59** (2025-03-31) by Felipe Sanches: "[Batch 1/4] port info from fontc_crater targets list" -- added commit hash and config_yaml path
+
+### Upstream Repository Analysis
+
+The cached repository at `googlefonts/Homenaje` (remote: `https://github.com/googlefonts/Homenaje`) contains:
+
+- **1 commit total**: `d371ad8` (2025-02-24) by Felipe Sanches: "Add sources/config.yaml"
+- This single commit created the entire repository contents including:
+ - `sources/Homenaje.glyphs` (19,150 lines) -- converted .glyphs source file
+ - `sources/config.yaml` -- gftools-builder configuration
+ - `old/version-1.002/` -- archive of original v1.002 sources (VFB, SFD, OTF formats)
+ - Standard metadata files (OFL.txt, FONTLOG.txt, AUTHORS.txt, etc.)
+ - Pre-built `fonts/Homenaje-Regular.ttf`
+
+### Config.yaml Contents
+
+```yaml
+sources:
+ - Homenaje.glyphs
+```
+
+Simple configuration pointing to the single .glyphs source file.
+
+### Source Files
+
+The repository contains both legacy and modern sources:
+- **Modern**: `sources/Homenaje.glyphs` -- Glyphs format, compatible with gftools-builder
+- **Legacy (old/version-1.002/src/)**: `Homenaje-Regular-OTF.vfb`, `Homenaje-Regular.vfb`, `Homenaje-Regular-TTF.sfd`, `Homenaje-Regular.otf`
+
+### Note on Commit Hash
+
+The commit hash `d371ad8` in METADATA.pb points to the repo setup commit from 2025-02-24, which is the only commit in the repository. This commit was made well after the font was originally onboarded in 2016 (PR #458). The .glyphs file appears to be a conversion from the original VFB sources. Since this is the only commit in the repo and it contains the config.yaml and source files needed for building, the reference is technically correct for build purposes.
+
+## Conclusion
+
+**Status: complete**
+
+The source metadata for Homenaje is complete. The METADATA.pb has a valid repository_url, commit hash, and config_yaml path. The upstream repository contains a .glyphs source file and a properly configured config.yaml. The commit hash references the only commit in the repository, which set up the entire repo including converted sources. All data is consistent and the font can be rebuilt from the referenced sources.
--- /dev/null
+# Investigation Report: Host Grotesk
+
+## Summary
+
+Host Grotesk is a sans-serif variable font (wght 300-800) with both upright and italic styles, designed by Element Type, Dogukan Karapinar, and Ibrahim Kactioglu. It was onboarded to Google Fonts on 2024-10-10. The upstream repository is at `github.com/Element-Type/HostGrotesk`. The METADATA.pb has a complete source block with repository URL, commit hash, config_yaml path, and an archive_url for the release. However, the onboarding commit message references a different commit hash (`4f267d3`) than what is currently in METADATA.pb (`ab2ba67`). The original commit `4f267d3` no longer exists in the upstream repository, which appears to have been force-pushed (the repo has only a single commit from a merge PR). The current METADATA.pb commit `ab2ba67` is the only commit in the repo and post-dates the onboarding (2024-11-13 vs 2024-10-10), indicating a correction was made. The source block references `sources/config.yaml`, which exists and is valid.
+
+## Key Findings
+
+| Field | Value |
+|---|---|
+| Family Name | Host Grotesk |
+| Repository URL | https://github.com/Element-Type/HostGrotesk |
+| Commit Hash (METADATA.pb) | ab2ba6769119e7ae71aa2fab46eedcb993c670a3 |
+| Commit Hash (onboarding msg) | 4f267d366fec1961bb219fe156fe7b4821ce8a15 |
+| Config YAML | sources/config.yaml |
+| Config Exists at Commit | Yes |
+| Source Files | sources/HostGrotesk.glyphs, sources/HostGrotesk-Italic.glyphs |
+| Date Added | 2024-10-03 |
+| Status | needs_correction |
+| Confidence | LOW |
+
+## Investigation Details
+
+### METADATA.pb Analysis
+
+The METADATA.pb file contains a complete source block:
+- `repository_url`: `https://github.com/Element-Type/HostGrotesk`
+- `commit`: `ab2ba6769119e7ae71aa2fab46eedcb993c670a3`
+- `archive_url`: `https://github.com/Element-Type/HostGrotesk/releases/download/1.002/HostGrotesk-1.002.zip`
+- `config_yaml`: `sources/config.yaml`
+- `branch`: `main`
+- File mappings for OFL.txt, variable TTFs from `fonts/variable/`
+
+### Upstream Repository
+
+The repo at `github.com/Element-Type/HostGrotesk` has only a single commit:
+- `ab2ba67` (2024-11-13): "Merge pull request #14 from vv-monsalve/QA-Host2" — by ibrahim
+
+This is a merge commit that introduced the entire repository contents (all 45 files show as additions). The repository was evidently force-pushed at some point, destroying the original history. The original onboarding commit `4f267d3` no longer exists in the repo.
+
+### Commit Hash Discrepancy
+
+The google/fonts onboarding commit `5b5a99da9` (2024-10-10) states:
+> "Taken from the upstream repo https://github.com/Element-Type/HostGrotesk at commit https://github.com/Element-Type/HostGrotesk/commit/4f267d366fec1961bb219fe156fe7b4821ce8a15."
+
+However, the current METADATA.pb references `ab2ba67` (dated 2024-11-13), which is approximately one month after the onboarding date. This commit was set by the fontc_crater batch update on 2025-03-31 (`19cdcec59`). Since the repo was force-pushed and only has one commit, the batch update picked the only available commit.
+
+### Binary Files
+
+The METADATA.pb source block references files from `fonts/variable/` but no such directory exists in the upstream repo at commit `ab2ba67`. The font binaries were obtained via the `archive_url` pointing to the GitHub release `1.002`. The source block's `files {}` mappings appear to reference the release archive contents, not the repo tree.
+
+### Config YAML
+
+The file `sources/config.yaml` exists at commit `ab2ba67` and contains:
+```yaml
+buildStatic: true
+buildVariable: true
+buildTTF: true
+buildOTF: true
+buildWebfont: true
+sources:
+ - HostGrotesk.glyphs
+ - HostGrotesk-Italic.glyphs
+axisOrder:
+ - wght
+familyName: Host Grotesk
+```
+
+The source files (`.glyphs`) are present in the `sources/` directory.
+
+### Timeline
+
+- 2024-10-10: Onboarded to google/fonts from commit `4f267d3`
+- 2024-10-10 to 2024-11-13: Multiple updates (OFL, article, designers, fixes)
+- 2024-11-13: Upstream repo force-pushed, resulting in single commit `ab2ba67`
+- 2025-03-31: fontc_crater batch update set commit to `ab2ba67`
+
+## Conclusion
+
+**Status: needs_correction**
+
+The source block is mostly complete, but the commit hash situation is problematic. The original onboarding commit `4f267d3` no longer exists in the upstream repo due to force-pushing. The current METADATA.pb commit `ab2ba67` post-dates the onboarding and is the only commit left in the repo. While the config.yaml and source files are all present at this commit, the provenance chain is broken. The `fonts/variable/` paths in the file mappings do not correspond to actual files in the repo tree -- they appear to reference the release archive. This is an unusual configuration that may need review. Confidence is LOW because the original commit is unverifiable.
--- /dev/null
+# Investigation Report: Hubballi
+
+## Summary
+
+Hubballi is a Kannada and Latin sans-serif font designed by Erin McLaughlin. It was onboarded to Google Fonts on 2021-12-16 via gftools-packager by Yanone (Jan Gerner). The upstream repository is at `github.com/erinmclaughlin/Hubballi`. The METADATA.pb source block is complete with repository URL, commit hash, config_yaml path, and file mappings. The commit hash `e5c909be` in METADATA.pb matches the commit referenced in the google/fonts onboarding commit message and is the latest (HEAD) commit in the upstream repo. The builder.yaml file exists at the referenced commit. All data is consistent and verified.
+
+## Key Findings
+
+| Field | Value |
+|---|---|
+| Family Name | Hubballi |
+| Repository URL | https://github.com/erinmclaughlin/Hubballi |
+| Commit Hash | e5c909bedfc4a2395ea300f94acec0d245ff7635 |
+| Config YAML | source/builder.yaml |
+| Config Exists at Commit | Yes |
+| Source Files | source/Hubballi-Regular.glyphs |
+| Date Added | 2021-12-16 |
+| Status | complete |
+| Confidence | HIGH |
+
+## Investigation Details
+
+### METADATA.pb Analysis
+
+The METADATA.pb file contains a complete source block:
+- `repository_url`: `https://github.com/erinmclaughlin/Hubballi`
+- `commit`: `e5c909bedfc4a2395ea300f94acec0d245ff7635`
+- `config_yaml`: `source/builder.yaml`
+- `branch`: `master`
+- File mappings for OFL.txt, DESCRIPTION.en_us.html, and fonts/ttf/Hubballi-Regular.ttf
+
+### Google Fonts Commit History
+
+The onboarding commit `29cde031b` (2021-12-16) by Yanone states:
+> "[gftools-packager] Hubballi: Version 1.000; ttfautohint (v1.8.3) added"
+> "Hubballi Version 1.000; ttfautohint (v1.8.3) taken from the upstream repo https://github.com/erinmclaughlin/Hubballi at commit https://github.com/erinmclaughlin/Hubballi/commit/e5c909bedfc4a2395ea300f94acec0d245ff7635."
+
+The commit hash in the onboarding message matches the METADATA.pb exactly.
+
+A later commit `a6e5eec8e` (2025-09-18) added the source info to METADATA.pb, referencing the original onboarding commit.
+
+### Upstream Repository
+
+The repo at `github.com/erinmclaughlin/Hubballi` has commit `e5c909be` as its HEAD (latest commit, dated 2021-12-08):
+- "Merge pull request #10 from yanone/master" — merging Yanone's preparation work
+
+The merge brought in: builder.yaml, DESCRIPTION.en_us.html, updated source files, and compiled font binary. This is the commit used for onboarding.
+
+The repo has extensive history going back to 2015 showing the complete development of the Kannada font.
+
+### Config YAML (builder.yaml)
+
+The file `source/builder.yaml` exists at commit `e5c909be` and contains:
+```yaml
+sources:
+ - ../source/Hubballi-Regular.glyphs
+outputDir: "../fonts"
+buildTTF: true
+buildOTF: false
+buildWebfont: false
+buildVariable: false
+```
+
+This is a static-only build (no variable font), building only TTF output from a single Glyphs source file.
+
+### Binary Font Verification
+
+The font file `fonts/ttf/Hubballi-Regular.ttf` exists at the referenced commit, and the file was introduced in commit `173f9119` (2021-11-04, "Latest binary"), which is part of the merge at `e5c909be`.
+
+### Timeline
+
+- 2015-07 to 2016-05: Initial development by Erin McLaughlin
+- 2021-11-04: Yanone prepared the repo for Google Fonts (builder.yaml, binary, etc.)
+- 2021-12-08: Merge PR #10 from yanone/master (commit `e5c909be`)
+- 2021-12-16: Onboarded to google/fonts by Yanone via gftools-packager
+
+## Conclusion
+
+**Status: complete**
+
+All source metadata is present and verified. The repository URL is correct, the commit hash matches both the onboarding message and the HEAD of the upstream repo, the config_yaml path points to a valid builder.yaml file, and file mappings are correct. No corrections needed. Confidence is HIGH because the gftools-packager onboarding message explicitly references this exact commit, the commit exists in the repo, and the font binary is present at that commit.
--- /dev/null
+# Investigation Report: Hubot Sans
+
+## Summary
+
+Hubot Sans is a variable sans-serif font (wdth 75-125, wght 200-900) with both upright and italic styles, designed by Tobias Bjerrome Ahlin for GitHub. It was onboarded to Google Fonts on 2024-10-04 by Emma Marichal. The METADATA.pb source block points to `github.com/github/hubot-sans` with commit `d4b2f67` and config at `sources/config.yaml`. However, the original onboarding commit message in google/fonts references a different repository (`googlefonts/hubot-sans`) and a different commit hash (`9c2cc3ac`). The commit `9c2cc3ac` does not exist in the `github/hubot-sans` repo, suggesting it was in the `googlefonts/hubot-sans` fork used during onboarding. The current METADATA.pb commit `d4b2f67` is the only commit in the `github/hubot-sans` repo (a merge of PR #37 "Add Hubot Sans - PR n1" dated 2024-10-17, after the google/fonts onboarding date of 2024-10-04). The config.yaml and source files are present. The repo URL was corrected from the fork to the canonical repo.
+
+## Key Findings
+
+| Field | Value |
+|---|---|
+| Family Name | Hubot Sans |
+| Repository URL (METADATA.pb) | https://github.com/github/hubot-sans |
+| Repository URL (onboarding msg) | https://github.com/googlefonts/hubot-sans |
+| Commit Hash (METADATA.pb) | d4b2f67cd7686f5907296d3f027112bbc4f69f42 |
+| Commit Hash (onboarding msg) | 9c2cc3ac30ac77cc7c3b40e0813b3487a0c56b7b |
+| Config YAML | sources/config.yaml |
+| Config Exists at Commit | Yes |
+| Source Files | sources/HubotSans.glyphspackage |
+| Date Added | 2024-10-04 |
+| Status | needs_correction |
+| Confidence | MEDIUM |
+
+## Investigation Details
+
+### METADATA.pb Analysis
+
+The METADATA.pb file contains a source block:
+- `repository_url`: `https://github.com/github/hubot-sans`
+- `commit`: `d4b2f67cd7686f5907296d3f027112bbc4f69f42`
+- `config_yaml`: `sources/config.yaml`
+- `branch`: `main`
+- File mappings for OFL.txt and variable TTFs from `googlefonts/variable/`
+
+### Google Fonts Commit History
+
+The onboarding commit `ccca81e56` (2024-10-04) by Emma Marichal states:
+> "Taken from the upstream repo https://github.com/googlefonts/hubot-sans at commit https://github.com/googlefonts/hubot-sans/commit/9c2cc3ac30ac77cc7c3b40e0813b3487a0c56b7b."
+
+Key discrepancies:
+1. The onboarding references `googlefonts/hubot-sans` but METADATA.pb points to `github/hubot-sans`
+2. The onboarding commit hash `9c2cc3ac` does not exist in the `github/hubot-sans` repo
+
+Subsequent google/fonts commits:
+- `fe31254d7` (2024-11-14): "update metadata (designers)"
+- `1470dc70c` (2024-11-14): "Update METADATA.pb"
+- `c72a13bd2` (2024-11-14): "Update METADATA.pb"
+- `80f7d5650` (2025-01-07): "Capitalize H in GitHub"
+- `19cdcec59` (2025-03-31): fontc_crater batch update (set source block with commit/config)
+
+### Upstream Repository
+
+The repo at `github.com/github/hubot-sans` has a single commit:
+- `d4b2f67` (2024-10-17): "Merge pull request #37 from emmamarichal/v1.1" — by Tobias Ahlin
+
+This merge commit introduced the entire repository contents. The PR title "Add Hubot Sans - PR n1" suggests this was the initial setup of the canonical repo. The merge date (2024-10-17) is 13 days after the google/fonts onboarding date (2024-10-04).
+
+The `googlefonts/hubot-sans` fork was not found in the local cache and likely contains the original commit `9c2cc3ac` used during onboarding. The work was done in the fork first, then merged into the canonical `github/hubot-sans` repo.
+
+### Config YAML
+
+The file `sources/config.yaml` exists at commit `d4b2f67` and contains:
+```yaml
+sources:
+ - HubotSans.glyphspackage
+outputDir: "../googlefonts"
+buildOTF: False
+buildWebfont: False
+buildTTF: false
+axisOrder:
+ - wdth
+ - wght
+familyName: "Hubot Sans"
+stat:
+ - name: Width
+ tag: wdth
+ values: [Condensed(75), SemiCondensed(87.5), Normal(100), SemiExpanded(112.5), Expanded(125)]
+ - name: Weight
+ tag: wght
+ values: [ExtraLight(200), Light(300), Regular(400), Medium(500), SemiBold(600), Bold(700), ExtraBold(800), Black(900)]
+```
+
+The source file `sources/HubotSans.glyphspackage` exists. The config builds only variable fonts (no static, no OTF, no webfont).
+
+### Binary Font Verification
+
+The font files at `googlefonts/variable/` exist at commit `d4b2f67`:
+- `HubotSans[wdth,wght].ttf` (369,548 bytes)
+- `HubotSans-Italic[wdth,wght].ttf` (381,520 bytes)
+
+The repo also contains `master_ufo/` with a designspace and UFO masters, in addition to the `sources/HubotSans.glyphspackage`.
+
+### Timeline
+
+- 2024-10-04: Onboarded to google/fonts from `googlefonts/hubot-sans` fork at commit `9c2cc3ac`
+- 2024-10-17: Canonical `github/hubot-sans` repo receives merge of PR #37 (commit `d4b2f67`)
+- 2024-11-14: Multiple METADATA.pb updates (designers, etc.)
+- 2025-01-07: Capitalization fix in METADATA.pb
+- 2025-03-31: fontc_crater batch update set commit to `d4b2f67` and config_yaml
+
+## Conclusion
+
+**Status: needs_correction**
+
+The source block exists but has a provenance issue. The onboarding was done from the `googlefonts/hubot-sans` fork at commit `9c2cc3ac`, which does not exist in the canonical `github/hubot-sans` repo. The METADATA.pb commit `d4b2f67` is the only commit in the canonical repo, corresponding to the merge of the fork's work. While this commit contains the correct source files, config.yaml, and built fonts, the original onboarding commit cannot be verified in the current repo. The repository URL correction from `googlefonts/hubot-sans` to `github/hubot-sans` appears intentional (pointing to the canonical repository). The config_yaml and source files are valid. Confidence is MEDIUM because while the data is internally consistent within the canonical repo, the original onboarding commit is from a different repository and cannot be cross-verified.
--- /dev/null
+# Investigation Report: Huninn
+
+## Summary
+
+Huninn is a Traditional Chinese sans-serif font designed by justfont. It was added to Google Fonts on 2025-04-02. The METADATA.pb has a complete source block with repository URL, commit hash, and config_yaml path. All data has been verified against the upstream repository.
+
+## Key Findings
+
+| Field | Value | Status |
+|-------|-------|--------|
+| **Family Name** | Huninn | -- |
+| **Repository URL** | https://github.com/justfont/Huninn | Verified |
+| **Commit Hash** | `2f278099d0a6fdf77593c30bd6e4a44859800ee2` | Verified |
+| **Config Path** | `sources/config.yaml` | Verified |
+| **Source Type** | .glyphspackage | -- |
+| **Status** | **complete** | -- |
+| **Confidence** | HIGH | -- |
+
+## Investigation Details
+
+### METADATA.pb Analysis
+
+The METADATA.pb at `ofl/huninn/METADATA.pb` contains a complete source block:
+
+```
+source {
+ repository_url: "https://github.com/justfont/Huninn"
+ commit: "2f278099d0a6fdf77593c30bd6e4a44859800ee2"
+ config_yaml: "sources/config.yaml"
+}
+```
+
+### Git History in google/fonts
+
+The font was added to google/fonts through a series of commits:
+
+1. `2f44570b1` (2025-04-02) - "Updating font name" - Initial addition as `ofl/huninn`, renamed from `ofl/justfonthuninn`. Added by Aaron Bell.
+2. `c23a2b3d9` (2025-04-02) - "Update Huninn-Regular.ttf" - Tweaking license string.
+3. `9c93ba363` - "Hani to Hant (#9384)" - Script classification change.
+4. `ad45d3c64` - "Update justfont biography and Huninn font info" - Metadata updates.
+5. `cbc944878` (2025-10-30) - "sources info for Huninn: Version 1.003 (PR #9228)" - Source block added to METADATA.pb by Felipe Sanches.
+
+### Upstream Repository Verification
+
+The upstream repository at https://github.com/justfont/Huninn is cached at `upstream_repos/fontc_crater_cache/justfont/Huninn/`.
+
+The referenced commit `2f278099d0a6fdf77593c30bd6e4a44859800ee2` exists and is dated 2025-04-02, which is the same day the font was added to google/fonts. The commit message is "Update README.md".
+
+### Config Verification
+
+The config file at `sources/config.yaml` exists both at the referenced commit and in the current repo:
+
+```yaml
+sources:
+ - Huninn.glyphspackage
+familyName: Huninn
+buildVariable: False
+autohintTTF: False
+buildOTF: False
+buildWebfont: False
+```
+
+### Source Files
+
+The sources directory contains:
+- `Huninn.glyphspackage` - Main source file
+- `config.yaml` - Build configuration
+- `post.py` - Post-processing script
+
+## Conclusion
+
+**Status: complete**
+
+All source metadata is correctly documented. The repository URL points to a valid upstream repo, the commit hash is verified and dates to the same day as the google/fonts onboarding, and the config.yaml path is correct with proper gftools-builder configuration. No changes needed.
--- /dev/null
+# Investigation Report: Hurricane
+
+## Summary
+
+Hurricane is a handwriting/display font designed by Robert Leuschke. It was added to Google Fonts on 2021-10-14 via gftools-packager. The METADATA.pb has a complete source block with repository URL, commit hash, file mappings, branch, and config_yaml path. All data has been verified against the upstream repository.
+
+## Key Findings
+
+| Field | Value | Status |
+|-------|-------|--------|
+| **Family Name** | Hurricane | -- |
+| **Repository URL** | https://github.com/googlefonts/hurricane | Verified |
+| **Commit Hash** | `bb10369a4820ebee5af7892e8661978c015cb077` | Verified |
+| **Config Path** | `sources/config.yml` | Verified |
+| **Source Type** | .glyphs | -- |
+| **Status** | **complete** | -- |
+| **Confidence** | HIGH | -- |
+
+## Investigation Details
+
+### METADATA.pb Analysis
+
+The METADATA.pb at `ofl/hurricane/METADATA.pb` contains a complete source block with explicit file mappings:
+
+```
+source {
+ repository_url: "https://github.com/googlefonts/hurricane"
+ commit: "bb10369a4820ebee5af7892e8661978c015cb077"
+ files {
+ source_file: "OFL.txt"
+ dest_file: "OFL.txt"
+ }
+ files {
+ source_file: "DESCRIPTION.en_us.html"
+ dest_file: "DESCRIPTION.en_us.html"
+ }
+ files {
+ source_file: "fonts/ttf/Hurricane-Regular.ttf"
+ dest_file: "Hurricane-Regular.ttf"
+ }
+ branch: "master"
+ config_yaml: "sources/config.yml"
+}
+```
+
+### Git History in google/fonts
+
+The font was added to google/fonts via:
+
+1. `05e8975af` (2021-10-14) - "Hurricane: Version 1.010; ttfautohint (v1.8.3) added (#3932)" - Added by gftools-packager. The commit body states: "Hurricane Version 1.010; ttfautohint (v1.8.3) taken from the upstream repo https://github.com/googlefonts/hurricane at commit https://github.com/googlefonts/hurricane/commit/8cc30aac85d0b3d1205cc9f99fe654a4bac316b6."
+
+Note: The gftools-packager message references commit `8cc30aac`, but the METADATA.pb references `bb10369a`. The current METADATA.pb commit (`bb10369a`) is dated 2021-10-14, which is the same day the font was added to google/fonts, and its message is "git url fixed". This is the HEAD of the master branch and appears to be a later commit than what was originally referenced by the packager, containing a git URL fix.
+
+### Upstream Repository Verification
+
+The upstream repository at https://github.com/googlefonts/hurricane is cached at `upstream_repos/fontc_crater_cache/googlefonts/hurricane/`. Note: The cached repo is a shallow clone with only 1 commit (the HEAD commit `bb10369a`). The original packager commit `8cc30aac` is not available in the shallow clone.
+
+The referenced commit `bb10369a4820ebee5af7892e8661978c015cb077` exists and is dated 2021-10-14, with the message "git url fixed". Since this is the only commit in the upstream repo (it has just 1 commit in the shallow clone, and it appears to also be the latest commit on the remote), the METADATA.pb correctly points to the latest state of the master branch.
+
+### Config Verification
+
+The config file at `sources/config.yml` (note: `.yml` extension, not `.yaml`) exists at the referenced commit:
+
+```yaml
+sources:
+ - Hurricane-Pro.glyphs
+familyName: "Hurricane"
+buildVariable: false
+#autohintTTF: false
+```
+
+### Source Files
+
+The sources directory contains:
+- `Hurricane-Pro.glyphs` - Main source file
+- `config.yml` - Build configuration
+
+## Conclusion
+
+**Status: complete**
+
+All source metadata is correctly documented. The repository URL points to a valid upstream repo, the commit hash `bb10369a` is verified (it is the HEAD of the master branch and represents the final state used for onboarding, after a URL fix that happened on the same day as the google/fonts addition). The config path correctly uses the `.yml` extension. File mappings are explicit and correct. No changes needed.
--- /dev/null
+# Investigation Report: Iansui
+
+## Summary
+
+Iansui is a Traditional Chinese handwriting font designed by But Ko. It was originally added to Google Fonts on 2024-11-25 at version 1.003, and has been updated multiple times since. The METADATA.pb has a complete source block with repository URL, commit hash, and config_yaml path. The current source block references commit `a66e7fe5b` (v1.011), which is a more recent version than the original onboarding commit.
+
+## Key Findings
+
+| Field | Value | Status |
+|-------|-------|--------|
+| **Family Name** | Iansui | -- |
+| **Repository URL** | https://github.com/ButTaiwan/iansui | Verified |
+| **Commit Hash** | `a66e7fe5bc492b358d8dc916f359157133a1d23c` | Verified |
+| **Config Path** | `sources/config.yaml` | Verified |
+| **Source Type** | .glyphspackage | -- |
+| **Status** | **complete** | -- |
+| **Confidence** | HIGH | -- |
+
+## Investigation Details
+
+### METADATA.pb Analysis
+
+The METADATA.pb at `ofl/iansui/METADATA.pb` contains a complete source block:
+
+```
+source {
+ repository_url: "https://github.com/ButTaiwan/iansui"
+ commit: "a66e7fe5bc492b358d8dc916f359157133a1d23c"
+ config_yaml: "sources/config.yaml"
+}
+```
+
+### Git History in google/fonts
+
+The font has a rich history in google/fonts:
+
+1. `7bf55551d` (2024-11-25) - "Iansui: 1.003 added" - Original onboarding. Commit body: "Taken from the upstream repo https://github.com/ButTaiwan/iansui at commit https://github.com/ButTaiwan/iansui/tree/41190e8094a9a5b47626c5d927daf0dcb226babf"
+2. `a1452e408` - "Forgot that we received permission to remove RFN"
+3. `c6e196b54` - "Update METADATA.pb"
+4. `ab1d5bc7f` - "Adding article image into article folder"
+5. `925640c0c` - "Update OFL.txt"
+6. `8813969bf` - "Update Iansui-Regular.ttf" - Font update: "Fonts are now building from .glyphspackage source; Vertical metrics updated"
+7. `19cdcec59` (2025-03-31) - "[Batch 1/4] port info from fontc_crater targets list" - Source block added.
+8. `6eac36785` (2025-04-02) - "Update Iansui-Regular.ttf" - Another font update with OO-poj glyphs and GASP/vmtx fixes.
+9. `8df4a8215`, `ef006da2c`, `c2ab770a6` - METADATA.pb updates (localized name changes).
+10. `d4e9f646b` (2025-05-14) - "removed localised family names" - Most recent change.
+
+### Upstream Repository Verification
+
+The upstream repository at https://github.com/ButTaiwan/iansui is cached at `upstream_repos/fontc_crater_cache/ButTaiwan/iansui/`.
+
+**Original onboarding commit**: `41190e8094a9a5b47626c5d927daf0dcb226babf` - "Merge pull request #43 from aaronbell/main" - This was used for the initial v1.003 onboarding. At this commit, the sources contained `Iansui-Regular.ufo` and `config.yaml`.
+
+**Current METADATA.pb commit**: `a66e7fe5bc492b358d8dc916f359157133a1d23c` (2025-01-28) - "v1.011 changelog" - This represents a newer version with significant source restructuring. Between the two commits, there were 10 intermediate commits including:
+- Source migration from UFO to .glyphspackage format
+- Addition of `-src` and `-build` versions
+- Updated config and requirements
+
+The current commit `a66e7fe5b` represents the v1.011 release, which aligns with the font updates pushed to google/fonts in early 2025.
+
+### Config Verification
+
+The config file at `sources/config.yaml` exists at the referenced commit `a66e7fe5b`:
+
+```yaml
+familyName: Iansui
+sources:
+- Iansui-build.glyphspackage
+buildVariable: False
+autohintTTF: False
+buildOTF: False
+buildWebfont: False
+```
+
+Note: The config at the original onboarding commit (`41190e80`) was different, referencing a UFO source:
+```yaml
+sources:
+ - Iansui-Regular.ufo
+familyName: Iansui
+autohintTTF: False
+buildOTF: False
+buildWebfont: False
+removeOutlineOverlaps: False
+```
+
+### Source Files
+
+The current sources directory contains:
+- `Iansui-build.glyphspackage` - Build-ready source
+- `Iansui-src.glyphspackage` - Development source
+- `config.yaml` - Build configuration
+- `gen-iansui-build.py` - Build generation script
+- `build-1757988489158208617.ninja` - Ninja build file
+
+## Conclusion
+
+**Status: complete**
+
+All source metadata is correctly documented. The repository URL is valid, the commit hash `a66e7fe5b` is verified and corresponds to the v1.011 release used for the latest font update in google/fonts, and the config_yaml path correctly points to a valid gftools-builder configuration file. No changes needed.
--- /dev/null
+# Investigation Report: Ibarra Real Nova
+
+## Summary
+
+Ibarra Real Nova is a serif/display variable font designed by Jose Maria Ribagorda and Octavio Pardo. It was added to Google Fonts on 2020-10-07 via gftools-packager at version 2.000. The METADATA.pb has a source block with repository URL, commit hash, explicit file mappings, and branch, but no config_yaml field. An override `config.yaml` exists in the google/fonts family directory, which is the correct approach since the upstream repo at the referenced commit had no config.yaml (it used a custom `build.sh` script).
+
+## Key Findings
+
+| Field | Value | Status |
+|-------|-------|--------|
+| **Family Name** | Ibarra Real Nova | -- |
+| **Repository URL** | https://github.com/googlefonts/ibarrareal | Verified |
+| **Commit Hash** | `7ae92a27f13f8e187db49312e7111041d1fa2a17` | Verified |
+| **Config Path** | Override config.yaml in google/fonts | Verified |
+| **Source Type** | .designspace + .ufo | -- |
+| **Status** | **complete** | -- |
+| **Confidence** | HIGH | -- |
+
+## Investigation Details
+
+### METADATA.pb Analysis
+
+The METADATA.pb at `ofl/ibarrarealnova/METADATA.pb` contains a source block with explicit file mappings but no config_yaml:
+
+```
+source {
+ repository_url: "https://github.com/googlefonts/ibarrareal"
+ commit: "7ae92a27f13f8e187db49312e7111041d1fa2a17"
+ files {
+ source_file: "OFL.txt"
+ dest_file: "OFL.txt"
+ }
+ files {
+ source_file: "DESCRIPTION.en_us.html"
+ dest_file: "DESCRIPTION.en_us.html"
+ }
+ files {
+ source_file: "fonts/variable/IbarraRealNova-Italic[wght].ttf"
+ dest_file: "IbarraRealNova-Italic[wght].ttf"
+ }
+ files {
+ source_file: "fonts/variable/IbarraRealNova[wght].ttf"
+ dest_file: "IbarraRealNova[wght].ttf"
+ }
+ files {
+ source_file: "fonts/ttf/IbarraRealNova-Bold.ttf"
+ dest_file: "static/IbarraRealNova-Bold.ttf"
+ }
+ files {
+ source_file: "fonts/ttf/IbarraRealNova-BoldItalic.ttf"
+ dest_file: "static/IbarraRealNova-BoldItalic.ttf"
+ }
+ files {
+ source_file: "fonts/ttf/IbarraRealNova-Italic.ttf"
+ dest_file: "static/IbarraRealNova-Italic.ttf"
+ }
+ files {
+ source_file: "fonts/ttf/IbarraRealNova-Regular.ttf"
+ dest_file: "static/IbarraRealNova-Regular.ttf"
+ }
+ files {
+ source_file: "fonts/ttf/IbarraRealNova-SemiBold.ttf"
+ dest_file: "static/IbarraRealNova-SemiBold.ttf"
+ }
+ files {
+ source_file: "fonts/ttf/IbarraRealNova-SemiBoldItalic.ttf"
+ dest_file: "static/IbarraRealNova-SemiBoldItalic.ttf"
+ }
+ branch: "master"
+}
+```
+
+The absence of `config_yaml` in the source block is correct because an override config.yaml exists in the google/fonts family directory.
+
+### Override config.yaml
+
+The file `ofl/ibarrarealnova/config.yaml` exists in google/fonts with the following content:
+
+```yaml
+buildVariable: true
+sources:
+ - sources/IbarraRealNova-Roman.designspace
+ - sources/IbarraRealNova-Italic.designspace
+```
+
+This was added on 2025-10-30 in commit `e980bb401` ("sources info for Ibarra Real Nova: Version 2.000 (PR #2709)"). The config references two designspace files that exist at the referenced commit `7ae92a27`.
+
+### Git History in google/fonts
+
+1. `89ade4fa7` (2020-10-07) - "Ibarra Real Nova: Version 2.000 added (#2709)" - Added by gftools-packager. Commit body: "Ibarra Real Nova Version 2.000 taken from the upstream repo https://github.com/googlefonts/ibarrareal at commit https://github.com/googlefonts/ibarrareal/commit/7ae92a27f13f8e187db49312e7111041d1fa2a17."
+2. `9f77052d4` - "Fix license text."
+3. `70b0fc8a8` - "Remove static fonts for unhinted variable font families (#3695)"
+4. Various metadata-only updates (language support, stroke/classification).
+5. `e980bb401` (2025-10-30) - "sources info for Ibarra Real Nova: Version 2.000 (PR #2709)" - Source block and override config added by Felipe Sanches.
+
+### Upstream Repository Verification
+
+The upstream repository at https://github.com/googlefonts/ibarrareal is cached at `upstream_repos/fontc_crater_cache/googlefonts/ibarrareal/`.
+
+The referenced commit `7ae92a27f13f8e187db49312e7111041d1fa2a17` (2020-09-30) exists and is a merge commit: "Merge pull request #15 from TypeNetwork/master". This predates the google/fonts addition by about a week, which is consistent with a normal packaging workflow.
+
+The gftools-packager message in the google/fonts commit directly confirms this exact commit hash, providing strong corroboration.
+
+**Note**: The upstream repo has since been modernized. Commit `e19809f` (2025-02-05) "Modernize tooling; upgrade to designspace v5" merged PR #41, which consolidated the two separate designspace files (`IbarraRealNova-Roman.designspace` and `IbarraRealNova-Italic.designspace`) into a single `IbarraRealNova.designspace` and removed the old `build.sh` script. However, the METADATA.pb correctly references the older commit `7ae92a27` which was the version actually used for the google/fonts onboarding.
+
+### Source Files at Referenced Commit
+
+At commit `7ae92a27`, the sources directory contained:
+- `IbarraRealNova-Roman.designspace` - Roman variable font source
+- `IbarraRealNova-Italic.designspace` - Italic variable font source
+- `IbarraRealNova-Regular.ufo/` - Regular master
+- `IbarraRealNova-Bold.ufo/` - Bold master
+- `IbarraRealNova-Italic.ufo/` - Italic master
+- `IbarraRealNova-BoldItalic.ufo/` - Bold Italic master
+- `build.sh` - Custom build script (no config.yaml at this commit)
+
+The override config.yaml in google/fonts correctly references `sources/IbarraRealNova-Roman.designspace` and `sources/IbarraRealNova-Italic.designspace`, both of which exist at the referenced commit.
+
+## Conclusion
+
+**Status: complete**
+
+All source metadata is correctly documented. The repository URL is valid, the commit hash is verified and matches what gftools-packager recorded, and an override config.yaml in the google/fonts family directory correctly references the designspace files at the referenced commit. The `config_yaml` field is intentionally omitted from METADATA.pb since google-fonts-sources auto-detects local override configs. No changes needed.
--- /dev/null
+# Investigation Report: IBM Plex Mono
+
+## Summary
+
+IBM Plex Mono is the monospace variant of the IBM Plex typeface family, designed by Mike Abbink and Bold Monday. It was first added to Google Fonts on 2018-03-12 and last updated to Version 2.3 on 2022-11-09. The upstream repository is `googlefonts/plex` (a fork of IBM/plex). The METADATA.pb has a complete source block with repository URL, commit hash, and file mappings. An override config.yaml exists in google/fonts pointing to .designspace sources that exist at the referenced commit.
+
+## Key Findings
+
+| Field | Value |
+|--------------------|-------|
+| Family Name | IBM Plex Mono |
+| Repository URL | https://github.com/googlefonts/plex |
+| Commit Hash | 9ab3b5b3b96325fb20f365ee0804adca92024cbf |
+| Commit Date | 2022-11-09 |
+| Commit Message | "Latest Mono fonts" |
+| Config YAML | Override config.yaml in google/fonts |
+| Source Files | IBM-Plex-Mono/sources/masters/IBM Plex Mono Roman.designspace, IBM-Plex-Mono/sources/masters/IBM Plex Mono Italic.designspace |
+| Build Type | Pre-compiled TTFs from Google-Fonts-Fixes (override config available for gftools-builder) |
+| Status | **complete** |
+| Confidence | HIGH |
+
+## Investigation Details
+
+### METADATA.pb Analysis
+
+The METADATA.pb contains a complete source block:
+- `repository_url`: `https://github.com/googlefonts/plex`
+- `commit`: `9ab3b5b3b96325fb20f365ee0804adca92024cbf`
+- `branch`: `master`
+- File mappings pull pre-compiled TTFs from `Google-Fonts-Fixes/fonts/IBM-Plex-Mono/fonts/complete/ttf/`
+- 14 static TTF weights (Thin through Bold, Roman and Italic)
+
+### Git History in google/fonts
+
+The font file history shows multiple updates:
+1. `b271bab46` - Initial addition: "ibmplexmono: v2.000 added (#1481)"
+2. `115c6eb01` - "Add updated and new versions of IBM Plex (#1837)"
+3. `465b90c97` - "IBM Plex Mono: Version 2.1 added (#3527)"
+4. `633f32005` - Last font update: "[gftools-packager] IBM Plex Mono: Version 2.3 added (#5524)" (2022-11-09, by Yanone)
+
+The commit `633f32005` explicitly references the upstream commit `9ab3b5b` in its body: "IBM Plex Mono Version 2.3 taken from the upstream repo https://github.com/googlefonts/plex at commit 9ab3b5b3b96325fb20f365ee0804adca92024cbf."
+
+### Upstream Repository Verification
+
+The cached repo at `upstream_repos/fontc_crater_cache/googlefonts/plex/` confirms:
+- Remote: `https://github.com/googlefonts/plex` (fork of IBM/plex)
+- Commit `9ab3b5b` exists and dates to 2022-11-09, message: "Latest Mono fonts"
+- At this commit, source files exist:
+ - `IBM-Plex-Mono/sources/masters/IBM Plex Mono Roman.designspace`
+ - `IBM-Plex-Mono/sources/masters/IBM Plex Mono Italic.designspace`
+ - 6 UFO master directories (Bold, Bold Italic, Italic, Regular, Thin, Thin Italic)
+
+Note: Source files were later removed from the repo in January 2024 (`98d717710`), but they exist at the referenced commit.
+
+### Override config.yaml
+
+An override config.yaml exists at `ofl/ibmplexmono/config.yaml` in google/fonts:
+```yaml
+sources:
+ - IBM-Plex-Mono/sources/masters/IBM Plex Mono Roman.designspace
+ - IBM-Plex-Mono/sources/masters/IBM Plex Mono Italic.designspace
+familyName: IBM Plex Mono
+buildStatic: true
+buildOTF: false
+```
+
+This was added in commit `f6c68379a` ("Add override config.yaml for 50 font families").
+
+### Repository Structure Note
+
+The `googlefonts/plex` repo is a Google-maintained fork of the original `IBM/plex` repository. It contains a `Google-Fonts-Fixes` directory with pre-compiled fonts specifically prepared for Google Fonts. The original IBM/plex monorepo structure had source files under `IBM-Plex-{Family}/sources/masters/`, but these were removed in January 2024 when the repo was reorganized into a `packages/` structure with only distribution files.
+
+## Conclusion
+
+IBM Plex Mono has a complete source block in METADATA.pb with a verified commit hash. The override config.yaml correctly points to .designspace source files that exist at the referenced commit. No corrections needed.
+
+**Status: complete**
--- /dev/null
+# Investigation Report: IBM Plex Sans
+
+## Summary
+
+IBM Plex Sans is the primary sans-serif variant of the IBM Plex typeface family, designed by Mike Abbink and Bold Monday. It was first added to Google Fonts on 2018-03-12 and last updated to Version 3.201 on 2025-01-10 as a variable font (wdth + wght axes). The upstream repository is `googlefonts/plex`. The METADATA.pb has a complete source block with repository URL and commit hash, but the referenced commit (from January 2025) post-dates the removal of source files from the repository. No config.yaml exists for this family.
+
+## Key Findings
+
+| Field | Value |
+|--------------------|-------|
+| Family Name | IBM Plex Sans |
+| Repository URL | https://github.com/googlefonts/plex |
+| Commit Hash | 3e312890b3b9e47378b30dedfe4196a42151243c |
+| Commit Date | 2025-01-10 |
+| Commit Message | "Discard static Sans entirely, pretend Var Sans is the only Sans moving forward" |
+| Config YAML | None |
+| Source Files | None at referenced commit (sources removed Jan 2024) |
+| Build Type | Pre-compiled variable TTFs from Google-Fonts-Fixes |
+| Status | **missing_config** |
+| Confidence | HIGH |
+
+## Investigation Details
+
+### METADATA.pb Analysis
+
+The METADATA.pb contains a source block with:
+- `repository_url`: `https://github.com/googlefonts/plex`
+- `commit`: `3e312890b3b9e47378b30dedfe4196a42151243c`
+- `branch`: `master`
+- File mappings pull variable TTFs from `Google-Fonts-Fixes/fonts/IBM-Plex-Sans/fonts/complete/ttf/`
+- 2 variable font files: `IBMPlexSans[wdth,wght].ttf` and `IBMPlexSans-Italic[wdth,wght].ttf`
+- Axes: wdth (75-100), wght (100-700)
+
+This was a major update from static instances (14 TTFs) to variable fonts.
+
+### Git History in google/fonts
+
+The font file history shows:
+1. `42ee46942` - Initial addition: "ibmplexsans: v2.001 added (#1483)"
+2. `115c6eb01` - "Add updated and new versions of IBM Plex (#1837)"
+3. `e0b9f6ca2` - "IBM Plex Sans: Version 3.2 added (#3439)"
+4. `8409f033c` - Last font update: "IBM Plex Sans: Version 3.201 added" (2025-01-10, by Yanone)
+
+The commit body says: "Taken from the upstream repo https://github.com/googlefonts/plex at commit 3e312890b3b9e47378b30dedfe4196a42151243c. Resolves #2407."
+
+### Upstream Repository Verification
+
+The cached repo at `upstream_repos/fontc_crater_cache/googlefonts/plex/` confirms:
+- Commit `3e31289` exists and dates to 2025-01-10, message: "Discard static Sans entirely, pretend Var Sans is the only Sans moving forward"
+- At this commit, NO source files exist for IBM Plex Sans (the `IBM-Plex-Sans/sources/` directory was removed in January 2024)
+- Only pre-compiled variable TTFs exist at `Google-Fonts-Fixes/fonts/IBM-Plex-Sans/fonts/complete/ttf/`
+
+Sources existed before January 2024:
+- `IBM-Plex-Sans/sources/masters/IBM Plex Sans Roman.designspace`
+- `IBM-Plex-Sans/sources/masters/IBM Plex Sans Italic.designspace`
+
+But these were deleted in commits `d8d4ace23` (2024-01-23) and `98d717710` (2024-01-26).
+
+### Config.yaml Status
+
+No config.yaml exists in google/fonts for IBM Plex Sans, and no config.yaml exists in the upstream repo. Since the referenced commit has no buildable sources, creating an override config.yaml would require pointing to an older commit or to the original IBM/plex repo where sources may still exist.
+
+### Repository Structure Note
+
+The referenced commit is the HEAD of the googlefonts/plex fork. The original source files were stored under `IBM-Plex-Sans/sources/masters/` with .designspace and .ufo files, but these were removed when the repository was reorganized in January 2024. The fonts served to Google Fonts are pre-compiled variable TTFs placed in the `Google-Fonts-Fixes/` directory.
+
+## Conclusion
+
+The METADATA.pb source block has correct repository URL and commit hash for the pre-compiled font delivery. However, no config.yaml can be created for this commit since source files do not exist at the referenced commit. A config.yaml pointing to sources would require referencing a commit prior to January 2024 when sources still existed, but that would not match the current fonts being served.
+
+**Status: missing_config**
--- /dev/null
+# Investigation Report: IBM Plex Sans Arabic
+
+## Summary
+
+IBM Plex Sans Arabic is the Arabic script variant of the IBM Plex typeface family, designed by Mike Abbink, Bold Monday, Khajag Apelian, and Wael Morcos. It was added to Google Fonts on 2021-06-17 and last updated to Version 1.101 on 2024-11-08. The upstream repository is `googlefonts/plex`. The METADATA.pb has a complete source block with repository URL and commit hash, but the referenced commit (from November 2024) post-dates the removal of source files from the repository. No config.yaml exists for this family.
+
+## Key Findings
+
+| Field | Value |
+|--------------------|-------|
+| Family Name | IBM Plex Sans Arabic |
+| Repository URL | https://github.com/googlefonts/plex |
+| Commit Hash | e80bf9282a630e70d6c1459f4125c9ec0e75316b |
+| Commit Date | 2024-11-08 |
+| Commit Message | "Delete old temp folder" |
+| Config YAML | None |
+| Source Files | None at referenced commit (sources removed Jan 2024) |
+| Build Type | Pre-compiled static TTFs from Google-Fonts-Fixes |
+| Status | **missing_config** |
+| Confidence | HIGH |
+
+## Investigation Details
+
+### METADATA.pb Analysis
+
+The METADATA.pb contains a source block with:
+- `repository_url`: `https://github.com/googlefonts/plex`
+- `commit`: `e80bf9282a630e70d6c1459f4125c9ec0e75316b`
+- `branch`: `master`
+- `primary_script`: `Arab`
+- File mappings pull static TTFs from `Google-Fonts-Fixes/fonts/IBM-Plex-Sans-Arabic/fonts/complete/ttf/`
+- 7 static TTF weights (Thin through Bold, no italics)
+
+### Git History in google/fonts
+
+The font file history shows:
+1. `121e596e0` - Initial addition: "IBM Plex Sans Arabic: Version 1.1 added (#3545)"
+2. `2cf301086` - Last font update: "IBM Plex Sans Arabic: Version 1.101 added" (2024-11-08, by Yanone)
+
+The commit body says: "Taken from the upstream repo https://github.com/googlefonts/plex at commit e80bf9282a630e70d6c1459f4125c9ec0e75316b. Resolves #7611."
+
+### Upstream Repository Verification
+
+The cached repo at `upstream_repos/fontc_crater_cache/googlefonts/plex/` confirms:
+- Commit `e80bf92` exists and dates to 2024-11-08, message: "Delete old temp folder"
+- At this commit, NO source files exist for IBM Plex Sans Arabic (the `IBM-Plex-Sans-Arabic/sources/` directory was removed in January 2024)
+- Only pre-compiled TTFs exist at `Google-Fonts-Fixes/fonts/IBM-Plex-Sans-Arabic/fonts/complete/ttf/`
+
+Sources existed before January 2024:
+- `IBM-Plex-Sans-Arabic/sources/masters/IBM Plex Sans Arabic.designspace`
+- Plus .ufo master directories
+
+These were deleted in commits `d8d4ace23` (2024-01-23) and `98d717710` (2024-01-26).
+
+### Config.yaml Status
+
+No config.yaml exists in google/fonts for IBM Plex Sans Arabic, and no config.yaml exists in the upstream repo. Since the referenced commit has no buildable sources, creating an override config.yaml is not possible for this commit.
+
+### Repository Structure Note
+
+The `googlefonts/plex` repo is a Google-maintained fork of IBM/plex. The font files in Google-Fonts-Fixes were prepared specifically for Google Fonts consumption. The original sources under `IBM-Plex-Sans-Arabic/sources/masters/` were removed in January 2024 when the repo was reorganized.
+
+## Conclusion
+
+The METADATA.pb source block has correct repository URL and commit hash for the pre-compiled font delivery. However, no config.yaml can be created for this commit since source files do not exist at the referenced commit. A config pointing to sources would require referencing a commit prior to January 2024.
+
+**Status: missing_config**
--- /dev/null
+# Investigation Report: IBM Plex Sans JP
+
+## Summary
+
+IBM Plex Sans JP is the Japanese variant of the IBM Plex typeface family, designed by Mike Abbink and Bold Monday. It was added to Google Fonts on 2022-09-12 (its first and only font update). The upstream repository is `googlefonts/plex`. The METADATA.pb has a complete source block with repository URL, commit hash, and file mappings. An override config.yaml exists in google/fonts pointing to a .glyphs source file that exists at the referenced commit.
+
+## Key Findings
+
+| Field | Value |
+|--------------------|-------|
+| Family Name | IBM Plex Sans JP |
+| Repository URL | https://github.com/googlefonts/plex |
+| Commit Hash | 80fcb676509354caa75c6bfc7f9db598545d466f |
+| Commit Date | 2022-09-12 |
+| Commit Message | "Converted all packager files to new format" |
+| Config YAML | Override config.yaml in google/fonts |
+| Source Files | IBM-Plex-Sans-JP/sources/masters/IBM Plex Sans JP.glyphs |
+| Build Type | Pre-compiled static TTFs from Google-Fonts-Fixes (override config available for gftools-builder) |
+| Status | **complete** |
+| Confidence | HIGH |
+
+## Investigation Details
+
+### METADATA.pb Analysis
+
+The METADATA.pb contains a source block with:
+- `repository_url`: `https://github.com/googlefonts/plex`
+- `commit`: `80fcb676509354caa75c6bfc7f9db598545d466f`
+- `branch`: `master`
+- `primary_script`: `Jpan`
+- File mappings pull static TTFs from `Google-Fonts-Fixes/fonts/IBM-Plex-Sans-JP/fonts/complete/ttf/`
+- 7 static TTF weights (Thin through Bold, no italics)
+
+### Git History in google/fonts
+
+The font file history shows:
+1. `f6d4d2bf9` - Initial and only font update: "[gftools-packager] IBM Plex Sans JP: Version 1.001 added (#5226)" (2022-09-22, by Yanone)
+2. `6a2dc64d2` - "Update METADATA.pb (#5295)" (metadata changes only)
+3. `591845e2c` - "IBM Plex JP: trying another lang ID (#5439)" (metadata changes only)
+
+The commit body says: "IBM Plex Sans JP Version 1.001 taken from the upstream repo https://github.com/googlefonts/plex at commit https://github.com/googlefonts/plex/commit/80fcb676509354caa75c6bfc7f9db598545d466f."
+
+### Upstream Repository Verification
+
+The cached repo at `upstream_repos/fontc_crater_cache/googlefonts/plex/` confirms:
+- Commit `80fcb67` exists and dates to 2022-09-12, message: "Converted all packager files to new format"
+- At this commit, source files exist:
+ - `IBM-Plex-Sans-JP/sources/masters/IBM Plex Sans JP.glyphs`
+ - `IBM-Plex-Sans-JP/sources/instances/postscript/IBM Plex Sans JP-*.glyphs` (per-instance .glyphs files)
+ - `IBM-Plex-Sans-JP/sources/instances/truetype/IBM Plex Sans JP-*.glyphs` (per-instance .glyphs files)
+
+Note: Source files were later removed from the repo in January 2024, but they exist at the referenced commit.
+
+### Override config.yaml
+
+An override config.yaml exists at `ofl/ibmplexsansjp/config.yaml` in google/fonts:
+```yaml
+sources:
+ - IBM-Plex-Sans-JP/sources/masters/IBM Plex Sans JP.glyphs
+familyName: IBM Plex Sans JP
+buildStatic: true
+buildOTF: false
+```
+
+This was added in commit `f6c68379a` ("Add override config.yaml for 50 font families").
+
+### Repository Structure Note
+
+The `googlefonts/plex` repo is a Google-maintained fork of IBM/plex. At the referenced commit, the original IBM/plex monorepo structure was still intact with source files under `IBM-Plex-{Family}/sources/`. These sources were removed in January 2024 when the repo was reorganized.
+
+## Conclusion
+
+IBM Plex Sans JP has a complete source block in METADATA.pb with a verified commit hash. The override config.yaml correctly points to the .glyphs source file that exists at the referenced commit. No corrections needed.
+
+**Status: complete**
--- /dev/null
+# Investigation: Iceberg
+
+## Summary
+
+| Field | Value |
+|-------|-------|
+| Family Name | Iceberg |
+| Slug | iceberg |
+| License Dir | ofl |
+| Repository URL | https://github.com/librefonts/iceberg |
+| Commit Hash | db1c024077a00f9999b5f6437a70c19ced5c1fc5 |
+| Config YAML | override config.yaml in google/fonts |
+| Status | complete |
+| Confidence | HIGH |
+
+## Source Data (METADATA.pb)
+
+```
+source {
+ repository_url: "https://github.com/librefonts/iceberg"
+ commit: "db1c024077a00f9999b5f6437a70c19ced5c1fc5"
+}
+```
+
+## Investigation
+
+The METADATA.pb at `ofl/iceberg/METADATA.pb` already contains a complete source block with both a repository URL and a commit hash. The font was added to google/fonts in the initial commit (90abd17b4f97671435798b6147b698aa9087612f, dated 2015-03-07) by Dave Crossland. No PR number is associated with this initial onboarding.
+
+The referenced repository `https://github.com/librefonts/iceberg` is available in the upstream cache at `upstream_repos/fontc_crater_cache/librefonts/iceberg`. The remote URL confirms this is `https://github.com/librefonts/iceberg`.
+
+Commit `db1c024077a00f9999b5f6437a70c19ced5c1fc5` exists in the cached repo with the message "update .travis.yml" (dated 2014-10-17). It is the only commit in the repository and includes the full font source: TTX disassembled files and the binary source files `src/Iceberg-Regular-OTF.vfb` and `src/Iceberg-Regular-TTF.vfb` (FontLab VFB format).
+
+There is no `config.yaml` in the upstream repository. However, an override `config.yaml` exists in `ofl/iceberg/config.yaml` within google/fonts with the following content:
+
+```yaml
+buildVariable: false
+sources:
+ - src/Iceberg-Regular-TTF.vfb
+ - src/Iceberg-Regular-OTF.vfb
+```
+
+This config references VFB source files that exist in the upstream repo at the referenced commit. The `cyrealtype/Iceberg` repository is a different, newer repository (with only 2 commits starting from 2016) and does not contain commit `db1c024`. The correct upstream is `librefonts/iceberg`.
+
+## Conclusion
+
+The source block in METADATA.pb is complete and correct. The repository URL points to `librefonts/iceberg`, the commit hash `db1c024` is verified to exist in the cached repo, and an override `config.yaml` is present in the google/fonts family directory. No action is needed.
--- /dev/null
+# Investigation: Iceland
+
+## Summary
+
+| Field | Value |
+|-------|-------|
+| Family Name | Iceland |
+| Slug | iceland |
+| License Dir | ofl |
+| Repository URL | https://github.com/cyrealtype/Iceland |
+| Commit Hash | bb43144b50825221060747ddba7b23bc05e7c960 |
+| Config YAML | override config.yaml in google/fonts |
+| Status | complete |
+| Confidence | HIGH |
+
+## Source Data (METADATA.pb)
+
+```
+source {
+ repository_url: "https://github.com/cyrealtype/Iceland"
+ commit: "bb43144b50825221060747ddba7b23bc05e7c960"
+}
+```
+
+## Investigation
+
+The METADATA.pb at `ofl/iceland/METADATA.pb` already contains a complete source block with both a repository URL and a commit hash. The font was added to google/fonts in the initial commit (90abd17b4f97671435798b6147b698aa9087612f, dated 2015-03-07) by Dave Crossland, and the current METADATA.pb source block was added or updated at some point after that.
+
+The referenced repository `https://github.com/cyrealtype/Iceland` is available in the upstream cache at `upstream_repos/fontc_crater_cache/cyrealtype/Iceland`. The remote URL confirms this is `https://github.com/cyrealtype/Iceland`.
+
+Commit `bb43144b50825221060747ddba7b23bc05e7c960` exists in the cached repo with the message "adding img" (dated 2016-04-06). This is the most recent commit in the repository. The repository contains the font source files: `src/Iceland-Regular-OTF.vfb`, `src/Iceland-Regular-TTF.vfb` (FontLab VFB format), `src/Iceland-Regular-OTF.otf`, and `src/sample.png`. The VFB source file `src/Iceland-Regular-TTF.vfb` was verified to exist at this commit.
+
+There is no `config.yaml` in the upstream repository. However, an override `config.yaml` exists in `ofl/iceland/config.yaml` within google/fonts with the following content:
+
+```yaml
+buildVariable: false
+sources:
+ - src/Iceland-Regular-TTF.vfb
+ - src/Iceland-Regular-OTF.vfb
+```
+
+This config references VFB source files that exist in the upstream repo at the referenced commit.
+
+Note: A separate `https://github.com/librefonts/iceland` repository does not appear to exist in the cache. The `cyrealtype/Iceland` repo is the canonical upstream for Iceland, designed by Cyreal (Alex Tarbovsky).
+
+## Conclusion
+
+The source block in METADATA.pb is complete and correct. The repository URL points to `cyrealtype/Iceland`, the commit hash `bb43144` is verified to exist in the cached repo, and an override `config.yaml` is present in the google/fonts family directory. No action is needed.
--- /dev/null
+# Investigation: Idiqlat
+
+## Summary
+
+| Field | Value |
+|-------|-------|
+| Family Name | Idiqlat |
+| Slug | idiqlat |
+| License Dir | ofl |
+| Repository URL | https://github.com/silnrsi/font-idiqlat |
+| Commit Hash | 37a6c68fa053f4b4b4c9f6d67c569f66621b6daa |
+| Config YAML | none (uses archive_url with prebuilt TTFs) |
+| Status | complete |
+| Confidence | HIGH |
+
+## Source Data (METADATA.pb)
+
+```
+source {
+ repository_url: "https://github.com/silnrsi/font-idiqlat"
+ commit: "37a6c68fa053f4b4b4c9f6d67c569f66621b6daa"
+ archive_url: "https://github.com/silnrsi/font-idiqlat/releases/download/v2.000/Idiqlat-2.000.zip"
+ files {
+ source_file: "Idiqlat-2.000/OFL.txt"
+ dest_file: "OFL.txt"
+ }
+ files {
+ source_file: "Idiqlat-2.000/Idiqlat-ExtraLight.ttf"
+ dest_file: "Idiqlat-ExtraLight.ttf"
+ }
+ files {
+ source_file: "Idiqlat-2.000/Idiqlat-Light.ttf"
+ dest_file: "Idiqlat-Light.ttf"
+ }
+ files {
+ source_file: "Idiqlat-2.000/Idiqlat-Regular.ttf"
+ dest_file: "Idiqlat-Regular.ttf"
+ }
+ branch: "main"
+}
+```
+
+## Investigation
+
+The METADATA.pb at `ofl/idiqlat/METADATA.pb` contains a complete source block with a repository URL, commit hash, archive URL, and explicit file mappings. The font was added to google/fonts by Emma Marichal in commit `5f85f5cbc91cc82480e505da3dfa150fb296a1ff`.
+
+The commit message body for `5f85f5cbc` explicitly states:
+
+> "Taken from the upstream repo https://github.com/silnrsi/font-idiqlat at commit https://github.com/silnrsi/font-idiqlat/commit/37a6c68fa053f4b4b4c9f6d67c569f66621b6daa."
+
+This directly confirms the repository URL and commit hash recorded in METADATA.pb.
+
+The upstream repository `https://github.com/silnrsi/font-idiqlat` is **not** present in the local cache at `upstream_repos/fontc_crater_cache/silnrsi/` (the silnrsi cache contains other SIL repositories but not font-idiqlat). The METADATA.pb uses `archive_url` to fetch prebuilt TTF files from a GitHub release (`v2.000`), rather than building from source files. This is the standard approach for SIL fonts that don't have gftools-builder compatible source files exposed.
+
+The `date_added` field is `2026-01-22`, indicating this is a very recently added font. A subsequent commit `8d66a498f6a0b489538a8bbaabf08558a0ead238` added an article for the family, confirming the onboarding was complete.
+
+Since the source block uses `archive_url` to fetch prebuilt binaries, no `config.yaml` is needed or applicable. The `config_yaml` field is absent from the METADATA.pb source block, which is correct for this pattern.
+
+## Conclusion
+
+The source block in METADATA.pb is complete and correct. The repository URL, commit hash, archive URL, and file mappings are all documented. The `archive_url` approach means no `config.yaml` is needed. No action is required. The `silnrsi/font-idiqlat` repository should be added to the fontc_crater_cache when disk space allows.
--- /dev/null
+# Investigation: Imbue
+
+## Summary
+
+| Field | Value |
+|-------|-------|
+| Family Name | Imbue |
+| Slug | imbue |
+| License Dir | ofl |
+| Repository URL | https://github.com/Etcetera-Type-Co/Imbue |
+| Commit Hash | 41b16f3fd61d33cacad0e579c35ef9566817184b |
+| Config YAML | override config.yaml in google/fonts |
+| Status | complete |
+| Confidence | HIGH |
+
+## Source Data (METADATA.pb)
+
+```
+source {
+ repository_url: "https://github.com/Etcetera-Type-Co/Imbue"
+ commit: "41b16f3fd61d33cacad0e579c35ef9566817184b"
+ files {
+ source_file: "fonts/variable/Imbue[opsz,wght].ttf"
+ dest_file: "Imbue[opsz,wght].ttf"
+ }
+ files {
+ source_file: "fonts/ttf/Imbue10pt-Black.ttf"
+ dest_file: "static/Imbue10pt-Black.ttf"
+ }
+ ... (additional static file mappings)
+ files {
+ source_file: "OFL.txt"
+ dest_file: "OFL.txt"
+ }
+ branch: "master"
+}
+```
+
+## Investigation
+
+The METADATA.pb at `ofl/imbue/METADATA.pb` contains a complete source block with repository URL, commit hash, file mappings, and branch. The font was added to google/fonts via PR #2805, committed by Rosalie Wagner (commit `5377e4c5ca6b224e0deb0dee313888bb46eaea35`).
+
+The PR commit message body explicitly states:
+
+> "Imbue Version 1.102 taken from the upstream repo https://github.com/Etcetera-Type-Co/Imbue at commit https://github.com/Etcetera-Type-Co/Imbue/commit/41b16f3fd61d33cacad0e579c35ef9566817184b."
+
+This directly confirms the repository URL and commit hash recorded in METADATA.pb.
+
+The upstream repository `https://github.com/Etcetera-Type-Co/Imbue` is available in the cache at `upstream_repos/fontc_crater_cache/Etcetera-Type-Co/Imbue`. Commit `41b16f3fd61d33cacad0e579c35ef9566817184b` exists in the cached repository with the message "Merge pull request #2 from RosaWagner/master" (dated 2020-12-01), confirming this is the correct merge commit for version 1.102.
+
+The upstream repository contains the Glyphs source file `Sources/Imbue.glyphs`. There is no `config.yaml` in the upstream repository, but an override `config.yaml` exists in `ofl/imbue/config.yaml` within google/fonts with the following content:
+
+```yaml
+buildVariable: true
+sources:
+ - Sources/Imbue.glyphs
+```
+
+This config correctly references the Glyphs source file that exists in the upstream repo. The `build.sh` and `build-others.sh` shell scripts in `Sources/` are legacy build scripts.
+
+Note: The METADATA.pb also includes explicit `files {}` mappings for the prebuilt TTFs, which means gftools-packager fetched the prebuilt binaries rather than compiling from source. This is consistent with the variable font era approach used for Imbue 1.102.
+
+## Conclusion
+
+The source block in METADATA.pb is complete and correct. The repository URL points to `Etcetera-Type-Co/Imbue`, the commit hash `41b16f3` is verified to exist in the cached repo, and an override `config.yaml` is present in the google/fonts family directory. No action is needed.
--- /dev/null
+# Investigation: IM Fell Double Pica
+
+## Summary
+
+| Field | Value |
+|-------|-------|
+| Family Name | IM Fell Double Pica |
+| Slug | im-fell-double-pica |
+| License Dir | ofl |
+| Repository URL | unknown |
+| Commit Hash | unknown |
+| Config YAML | unknown |
+| Status | missing_url |
+| Confidence | LOW |
+
+## Source Data (METADATA.pb)
+
+```
+No source block
+```
+
+## Investigation
+
+The METADATA.pb at `ofl/imfelldoublepica/METADATA.pb` contains no source block. The font was added to google/fonts in the initial commit (`90abd17b4f97671435798b6147b698aa9087612f`, dated 2015-03-07) by Dave Crossland, along with all other IM Fell variants. This predates the practice of tracking upstream repository information.
+
+The git log for `ofl/imfelldoublepica/` shows:
+- `49cd93129` — "imfelldoublepica: rename fonts and regenerate METADATA.pb" (renamed `IMFeDPit28P.ttf` → `IMFELLDoublePica-Italic.ttf` and `IMFeDPrm28P.ttf` → `IMFELLDoublePica-Regular.ttf`)
+- `90abd17b4` — "Initial commit"
+
+None of these commits reference an upstream repository URL or commit hash.
+
+The font was designed by Igino Marini (iginomarini.com). The copyright string reads: "© 2007 Igino Marini (www.iginomarini.com mail@iginomarini.com)".
+
+A repository `https://github.com/librefonts/imfelldoublepica` exists in the local cache at `upstream_repos/fontc_crater_cache/librefonts/imfelldoublepica`. This repo has a single commit (`35b0c6ea`, "update .travis.yml", 2014-10-17) and contains only TTX-disassembled font data (no VFB or other editable source files, only `src/METADATA_comments.txt` and `src/VERSIONS.txt`). The font version documented is 3.00.
+
+This `librefonts/imfelldoublepica` repository appears to be an archival mirror of the compiled TTF, not the original design source. Igino Marini does not appear to have a public GitHub repository for the IM Fell fonts; the actual sources were originally provided from his personal website (www.iginomarini.com).
+
+Since the available "source" is only a TTX decomposition of prebuilt binaries (not editable design files), and there are no VFB or Glyphs/UFO/designspace sources available, it is unclear whether a `config.yaml` can be meaningfully constructed. The `librefonts/imfelldoublepica` repo does not provide a buildable source.
+
+No Google Fonts config.yaml override exists in `ofl/imfelldoublepica/` in google/fonts.
+
+## Conclusion
+
+The source block is missing from METADATA.pb. The most likely upstream candidate is `https://github.com/librefonts/imfelldoublepica` (an archival TTX mirror), but this is not a true upstream design source. The actual designer (Igino Marini) does not appear to maintain a public GitHub repository. A question should be raised with the Google Fonts team about whether `librefonts/imfelldoublepica` is the appropriate repository to reference, and what commit to use. Until the upstream source situation is clarified, this family requires further investigation or a question to the original onboarding engineer (Dave Crossland).
--- /dev/null
+# Investigation: IM Fell Double Pica SC
+
+## Summary
+
+| Field | Value |
+|-------|-------|
+| Family Name | IM Fell Double Pica SC |
+| Slug | im-fell-double-pica-sc |
+| License Dir | ofl |
+| Repository URL | unknown |
+| Commit Hash | unknown |
+| Config YAML | unknown |
+| Status | missing_url |
+| Confidence | LOW |
+
+## Source Data (METADATA.pb)
+
+```
+No source block
+```
+
+## Investigation
+
+The METADATA.pb at `ofl/imfelldoublepicasc/METADATA.pb` contains no source block. The font was added to google/fonts in the initial commit (`90abd17b4f97671435798b6147b698aa9087612f`, dated 2015-03-07) by Dave Crossland, along with all other IM Fell variants. This predates the practice of tracking upstream repository information.
+
+The git log for `ofl/imfelldoublepicasc/` shows that only metadata/language updates were made after the initial commit; no upstream repository references appear anywhere.
+
+The font was designed by Igino Marini (iginomarini.com). The copyright string reads: "© 2007 Igino Marini (www.iginomarini.com mail@iginomarini.com)". The family is a small caps variant of IM Fell Double Pica. The single font file is `IMFeDPsc28P.ttf` (version 3.00, per the `VERSIONS.txt` in the librefonts archive).
+
+A repository `https://github.com/librefonts/imfelldoublepicasc` exists in the local cache at `upstream_repos/fontc_crater_cache/librefonts/imfelldoublepicasc`. This repo has a single commit (`2274064`, "update .travis.yml", 2014-10-17) and contains only TTX-disassembled font data (no VFB or other editable source files, only `src/METADATA_comments.txt` and `src/VERSIONS.txt`).
+
+Like the non-SC variant, this `librefonts/imfelldoublepicasc` repository is an archival mirror of the compiled TTF, not the original design source. The SC variant was originally provided alongside the other IM Fell variants from Igino Marini's personal website. No public GitHub repository for the actual design sources has been identified.
+
+No Google Fonts config.yaml override exists in `ofl/imfelldoublepicasc/` in google/fonts.
+
+## Conclusion
+
+The source block is missing from METADATA.pb. The situation is identical to IM Fell Double Pica: the only available "upstream" is a TTX archival mirror (`librefonts/imfelldoublepicasc`) with no buildable design sources. A question should be raised with the Google Fonts team (Dave Crossland) about whether `librefonts/imfelldoublepicasc` is the appropriate repository to reference and what the appropriate commit would be. Until clarified, this family requires further investigation into Igino Marini's original source distribution or the `librefonts` organization's use as the canonical source mirror.
--- /dev/null
+# Investigation: Imperial Script
+
+## Summary
+
+| Field | Value |
+|-------|-------|
+| Family Name | Imperial Script |
+| Slug | imperial-script |
+| License Dir | ofl |
+| Repository URL | https://github.com/googlefonts/imperial-script |
+| Commit Hash | 01a1656c6ffebe306262129aafee029fe6a7f3f3 |
+| Config YAML | sources/config.yml |
+| Status | complete |
+| Confidence | HIGH |
+
+## Source Data (METADATA.pb)
+
+```
+source {
+ repository_url: "https://github.com/googlefonts/imperial-script"
+ commit: "01a1656c6ffebe306262129aafee029fe6a7f3f3"
+ files {
+ source_file: "OFL.txt"
+ dest_file: "OFL.txt"
+ }
+ files {
+ source_file: "DESCRIPTION.en_us.html"
+ dest_file: "DESCRIPTION.en_us.html"
+ }
+ files {
+ source_file: "fonts/ttf/ImperialScript-Regular.ttf"
+ dest_file: "ImperialScript-Regular.ttf"
+ }
+ branch: "master"
+ config_yaml: "sources/config.yml"
+}
+```
+
+## Investigation
+
+The METADATA.pb for Imperial Script (at `google/fonts/ofl/imperialscript/METADATA.pb`) already contains a complete source block with `repository_url`, `commit`, and `config_yaml` fields.
+
+The upstream repository is cached at `upstream_repos/fontc_crater_cache/googlefonts/imperial-script/`. Verification confirmed:
+
+1. **Commit hash**: `01a1656c6ffebe306262129aafee029fe6a7f3f3` exists in the upstream repo. The commit message is "v10 updated glyph info" authored by Viviana Monsalve on 2021-11-12. This is also the HEAD commit of the repository.
+
+2. **Config file**: `sources/config.yml` exists at the referenced path and contains:
+ ```yaml
+ sources:
+ - ImperialScript.glyphs
+ familyName: "Imperial Script"
+ buildVariable: false
+ ```
+
+3. **Source format**: The repository uses a `.glyphs` source file (`ImperialScript.glyphs`), which is gftools-builder compatible.
+
+The font was designed by Robert Leuschke. The family was added to Google Fonts on 2021-11-18, shortly after the commit date (2021-11-12), consistent with the source metadata.
+
+## Conclusion
+
+The source block for Imperial Script is complete and verified. Repository URL, commit hash, and config_yaml all check out. No action needed.
--- /dev/null
+# Investigation: Imprima
+
+## Summary
+
+| Field | Value |
+|-------|-------|
+| Family Name | Imprima |
+| Slug | imprima |
+| License Dir | ofl |
+| Repository URL | https://github.com/etunni/imprima |
+| Commit Hash | efec6ee25d2ba461487c391b62ae26817614741a |
+| Config YAML | unknown |
+| Status | missing_config |
+| Confidence | HIGH |
+
+## Source Data (METADATA.pb)
+
+```
+source {
+ repository_url: "https://github.com/etunni/imprima"
+ commit: "efec6ee25d2ba461487c391b62ae26817614741a"
+ files {
+ source_file: "OFL.txt"
+ dest_file: "OFL.txt"
+ }
+ files {
+ source_file: "fonts/ttf/Imprima-Regular.ttf"
+ dest_file: "Imprima-Regular.ttf"
+ }
+ branch: "master"
+}
+```
+
+## Investigation
+
+The METADATA.pb for Imprima (at `google/fonts/ofl/imprima/METADATA.pb`) contains a source block with `repository_url` and `commit` but no `config_yaml`.
+
+The upstream repository is cached at `upstream_repos/fontc_crater_cache/etunni/imprima/`. Verification confirmed:
+
+1. **Commit hash**: `efec6ee25d2ba461487c391b62ae26817614741a` exists in the upstream repo. The commit is a merge commit ("Merge pull request #1 from emmamarichal/master") by Eduardo Rodríguez Tunni on 2023-02-10. This is also the HEAD commit of the repository (the latest commit on master).
+
+2. **Source format**: The repository has a `sources/` directory containing `Imprima.glyphs`, which is a gftools-builder-compatible source file.
+
+3. **Config file**: No `config.yaml` or `config.yml` exists anywhere in the repository. The `sources/` directory contains only `Imprima.glyphs`.
+
+The font was designed by Eduardo Tunni and was originally added to Google Fonts on 2012-03-14. The source block was evidently updated with the commit hash and repo URL reflecting a 2023 mastering/update, but no `config.yaml` was added to the upstream repository.
+
+An override `config.yaml` could be created in the google/fonts family directory referencing the `.glyphs` source, enabling automated rebuilds.
+
+## Conclusion
+
+The source block for Imprima has `repository_url` and `commit` but is missing `config_yaml`. The upstream repository has a `.glyphs` source file (`sources/Imprima.glyphs`) but no `config.yaml`. An override `config.yaml` should be created in the google/fonts `ofl/imprima/` directory referencing `sources/Imprima.glyphs`. Status: `missing_config`.
--- /dev/null
+# Investigation: Inclusive Sans
+
+## Summary
+
+| Field | Value |
+|-------|-------|
+| Family Name | Inclusive Sans |
+| Slug | inclusive-sans |
+| License Dir | ofl |
+| Repository URL | https://github.com/LivKing/Inclusive-Sans |
+| Commit Hash | 38b8ed1dd67bd25ef4180140492810cf050ef501 |
+| Config YAML | sources/config.yaml |
+| Status | complete |
+| Confidence | HIGH |
+
+## Source Data (METADATA.pb)
+
+```
+source {
+ repository_url: "https://github.com/LivKing/Inclusive-Sans"
+ commit: "38b8ed1dd67bd25ef4180140492810cf050ef501"
+ files {
+ source_file: "OFL.txt"
+ dest_file: "OFL.txt"
+ }
+ files {
+ source_file: "fonts/variable/InclusiveSans[wght].ttf"
+ dest_file: "InclusiveSans[wght].ttf"
+ }
+ files {
+ source_file: "fonts/variable/InclusiveSans-Italic[wght].ttf"
+ dest_file: "InclusiveSans-Italic[wght].ttf"
+ }
+ branch: "main"
+ config_yaml: "sources/config.yaml"
+}
+```
+
+## Investigation
+
+The METADATA.pb for Inclusive Sans (at `google/fonts/ofl/inclusivesans/METADATA.pb`) already contains a complete source block with `repository_url`, `commit`, and `config_yaml` fields.
+
+The upstream repository is cached at `upstream_repos/fontc_crater_cache/LivKing/Inclusive-Sans/`. Verification confirmed:
+
+1. **Commit hash**: `38b8ed1dd67bd25ef4180140492810cf050ef501` exists in the upstream repo. The commit message is "fixed r caron top anchor position in regular" authored by Olivia King on 2025-02-21. This is also the HEAD commit of the repository.
+
+2. **Config file**: `sources/config.yaml` exists and contains:
+ ```yaml
+ sources:
+ - InclusiveSans.glyphs
+ - InclusiveSans-Italic.glyphs
+ axisOrder:
+ - wght
+ - ital
+ familyName: "Inclusive Sans"
+ cleanUp: true
+ stat:
+ ...
+ ```
+
+3. **Source format**: The repository uses `.glyphs` source files, which are gftools-builder compatible.
+
+The font was designed by Olivia King. The family was added to Google Fonts on 2023-08-04 and the referenced commit is dated 2025-02-21, suggesting the METADATA.pb was updated after the initial onboarding to reflect a recent maintenance commit.
+
+## Conclusion
+
+The source block for Inclusive Sans is complete and verified. Repository URL, commit hash, and config_yaml all check out. No action needed.
--- /dev/null
+# Investigation: Inconsolata
+
+## Summary
+
+| Field | Value |
+|-------|-------|
+| Family Name | Inconsolata |
+| Slug | inconsolata |
+| License Dir | ofl |
+| Repository URL | https://github.com/googlefonts/Inconsolata |
+| Commit Hash | fc1fc21081558b39a2db43bfd9b65bf9acb50701 |
+| Config YAML | sources/config.yaml |
+| Status | complete |
+| Confidence | HIGH |
+
+## Source Data (METADATA.pb)
+
+```
+source {
+ repository_url: "https://github.com/googlefonts/Inconsolata"
+ commit: "fc1fc21081558b39a2db43bfd9b65bf9acb50701"
+ config_yaml: "sources/config.yaml"
+}
+```
+
+## Investigation
+
+The METADATA.pb for Inconsolata (at `google/fonts/ofl/inconsolata/METADATA.pb`) already contains a source block with `repository_url`, `commit`, and `config_yaml` fields.
+
+The upstream repository is cached at `upstream_repos/fontc_crater_cache/googlefonts/Inconsolata/`. Verification confirmed:
+
+1. **Commit hash**: `fc1fc21081558b39a2db43bfd9b65bf9acb50701` exists in the upstream repo. The commit message is "Merge pull request #70 from googlefonts/gf-mastering2" by Marc Foley on 2022-04-28. This is also the HEAD commit of the repository.
+
+2. **Config file**: `sources/config.yaml` exists and contains:
+ ```yaml
+ sources:
+ - Inconsolata.glyphs
+ axisOrder:
+ - wdth
+ - wght
+ familyName: Inconsolata
+ buildStatic: true
+ flattenComponents: false
+ decomposeTransformedComponents: true
+ vttSources:
+ Inconsolata[wdth,wght].ttf: vtt_hinting.ttx
+ includeSourceFixes: true
+ ```
+
+3. **Source format**: The repository uses a `.glyphs` source file (`Inconsolata.glyphs`), which is gftools-builder compatible. The font is a variable font with `wdth` and `wght` axes.
+
+The font was originally designed by Raph Levien and is now maintained in the `googlefonts` organization. The family was originally added to Google Fonts in 2010, and the current source block reflects the modernized variable font version.
+
+## Conclusion
+
+The source block for Inconsolata is complete and verified. Repository URL, commit hash, and config_yaml all check out. No action needed.
--- /dev/null
+# Investigation: Indie Flower
+
+## Summary
+
+| Field | Value |
+|-------|-------|
+| Family Name | Indie Flower |
+| Slug | indie-flower |
+| License Dir | ofl |
+| Repository URL | https://github.com/googlefonts/indieflower |
+| Commit Hash | db44d10c34c1d74011b7f3bee8c7c12123b6068e |
+| Config YAML | sources/config.yaml |
+| Status | complete |
+| Confidence | HIGH |
+
+## Source Data (METADATA.pb)
+
+```
+source {
+ repository_url: "https://github.com/googlefonts/indieflower"
+ commit: "db44d10c34c1d74011b7f3bee8c7c12123b6068e"
+ config_yaml: "sources/config.yaml"
+}
+```
+
+## Investigation
+
+The METADATA.pb for Indie Flower (at `google/fonts/ofl/indieflower/METADATA.pb`) already contains a source block with `repository_url`, `commit`, and `config_yaml` fields.
+
+The upstream repository is cached at `upstream_repos/fontc_crater_cache/googlefonts/indieflower/`. Verification confirmed:
+
+1. **Commit hash**: `db44d10c34c1d74011b7f3bee8c7c12123b6068e` exists in the upstream repo. The commit message is "Add sources/config.yaml" authored by Felipe Corrêa da Silva Sanches on 2025-02-25. This is also the HEAD commit of the repository.
+
+2. **Config file**: `sources/config.yaml` exists and contains:
+ ```yaml
+ sources:
+ - IndieFlower.glyphs
+ ```
+
+3. **Source format**: The repository uses a `.glyphs` source file (`IndieFlower.glyphs`), which is gftools-builder compatible.
+
+The font was designed by Kimberly Geswein. The family was originally added to Google Fonts in 2011 and the repository is now maintained under the `googlefonts` organization. The referenced commit (`db44d10`) is very recent (2025-02-25), reflecting a maintenance commit that added the `config.yaml`.
+
+## Conclusion
+
+The source block for Indie Flower is complete and verified. Repository URL, commit hash, and config_yaml all check out. No action needed.
--- /dev/null
+# Investigation: Ingrid Darling
+
+## Summary
+
+| Field | Value |
+|-------|-------|
+| Family Name | Ingrid Darling |
+| Slug | ingrid-darling |
+| License Dir | ofl |
+| Repository URL | https://github.com/googlefonts/ingrid-darling |
+| Commit Hash | ea2b4893cf8dc8cd0e7fb2b89f9631b38fde4ed3 |
+| Config YAML | sources/config.yml |
+| Status | complete |
+| Confidence | HIGH |
+
+## Source Data (METADATA.pb)
+
+```
+source {
+ repository_url: "https://github.com/googlefonts/ingrid-darling"
+ commit: "ea2b4893cf8dc8cd0e7fb2b89f9631b38fde4ed3"
+ files {
+ source_file: "OFL.txt"
+ dest_file: "OFL.txt"
+ }
+ files {
+ source_file: "documentation/DESCRIPTION.en_us.html"
+ dest_file: "DESCRIPTION.en_us.html"
+ }
+ files {
+ source_file: "fonts/ttf/IngridDarling-Regular.ttf"
+ dest_file: "IngridDarling-Regular.ttf"
+ }
+ branch: "master"
+ config_yaml: "sources/config.yml"
+}
+```
+
+## Investigation
+
+The METADATA.pb for Ingrid Darling (at `google/fonts/ofl/ingriddarling/METADATA.pb`) already contains a complete source block with `repository_url`, `commit`, and `config_yaml` fields.
+
+The upstream repository is cached at `upstream_repos/fontc_crater_cache/googlefonts/ingrid-darling/`. Verification confirmed:
+
+1. **Commit hash**: `ea2b4893cf8dc8cd0e7fb2b89f9631b38fde4ed3` exists in the upstream repo. The commit message is "description file moved o documentation" authored by Viviana Monsalve on 2022-03-11. This is also the HEAD commit of the repository.
+
+2. **Config file**: `sources/config.yml` exists and contains:
+ ```yaml
+ sources:
+ - IngridDarling.glyphs
+ familyName: "Ingrid Darling"
+ buildVariable: false
+ ```
+
+3. **Source format**: The repository uses a `.glyphs` source file (`IngridDarling.glyphs`), which is gftools-builder compatible.
+
+The font was designed by Robert Leuschke. The family was added to Google Fonts on 2022-03-11, matching the commit date exactly, suggesting this was the onboarding commit.
+
+## Conclusion
+
+The source block for Ingrid Darling is complete and verified. Repository URL, commit hash, and config_yaml all check out. No action needed.
--- /dev/null
+# Investigation: Inknut Antiqua
+
+## Summary
+
+| Field | Value |
+|-------|-------|
+| Family Name | Inknut Antiqua |
+| Slug | inknut-antiqua |
+| License Dir | ofl |
+| Repository URL | https://github.com/clauseggers/Inknut-Antiqua |
+| Commit Hash | unknown |
+| Config YAML | unknown |
+| Status | missing_commit |
+| Confidence | MEDIUM |
+
+## Source Data (METADATA.pb)
+
+```
+source {
+ repository_url: "https://github.com/clauseggers/Inknut-Antiqua"
+}
+```
+
+## Investigation
+
+The METADATA.pb for Inknut Antiqua (at `google/fonts/ofl/inknutantiqua/METADATA.pb`) contains a partial source block with only `repository_url` — no `commit` and no `config_yaml`.
+
+The `repository_url` field was added to METADATA.pb by Simon Cozens in commit `21e98aac8` on 2024-01-14 ("More upstreams (i,j,k)"), alongside several other families.
+
+The upstream repository is cached at `upstream_repos/fontc_crater_cache/clauseggers/Inknut-Antiqua/`. The repository structure is:
+- `Inknut Antiqua uprights.glyphs` — a `.glyphs` source file at the repo root
+- `UFOs/` — contains `Inknut Antiqua-Regular.ufo` and `Inknut Antiqua-Bold.ufo`
+- `Inknut Antiqua LATIN ONLY/Inknut Antiqua uprights 124 LATIN ONLY.glyphs`
+- `TTF-OTF/` — compiled TTF/OTF files
+- `OFL.txt`, `README.md`, and other assets
+
+The repository has a `.glyphs` source file, which is gftools-builder-compatible, but no `config.yaml` exists anywhere in the repository.
+
+**Google/fonts history for Inknut Antiqua:**
+- Initial commit `90abd17b4` (2015-03-07): Initial add
+- `a1eda398f` (2015-05-20): "Updating Inknut Antiqua" — updated all TTF files
+- `afd76e905` (2017-05-08): "hotfix-inknutantiqua: v1.003 added" — TTF files updated (PR #895)
+- `fab83f4be` (2020-10-08): "HindGuntur, InknutAntiqua, Khula, Padauk Hinting (#2378)" — re-hinted TTFs
+
+The upstream repo commit history shows the most recent activity is `91d14bf032cc0b44360a5adf56f3af16639786c7` (2026-01-02, "Fix image link for Inknut Antiqua specimen"), with most font development activity clustered in 2014-2015.
+
+Given the last substantive font file update in google/fonts was the hinting PR in October 2020, and that PR operated on the TTF files directly (not from upstream source), the correct onboarding commit is unclear. The fonts in google/fonts were likely derived from an early upstream commit (2014-2015), but cross-referencing the exact commit requires comparing binary file properties. The HEAD commit of the upstream is `91d14bf032cc0b44360a5adf56f3af16639786c7` (January 2026).
+
+An override `config.yaml` in the google/fonts family directory could reference the `.glyphs` source for potential rebuilds, but the correct commit hash needs to be identified first.
+
+## Conclusion
+
+The source block for Inknut Antiqua is incomplete: it has `repository_url` but is missing both `commit` and `config_yaml`. The upstream repository has `.glyphs` source files but no `config.yaml`. Status: `missing_commit`. Actions needed: (1) identify the correct upstream commit corresponding to the current binary files in google/fonts; (2) create an override `config.yaml` in the google/fonts directory referencing `Inknut Antiqua uprights.glyphs`.
--- /dev/null
+# Investigation: Inria Sans
+
+## Summary
+
+| Field | Value |
+|-------|-------|
+| Family Name | Inria Sans |
+| Slug | inria-sans |
+| License Dir | ofl |
+| Repository URL | https://github.com/BlackFoundryCom/InriaFonts |
+| Commit Hash | unknown |
+| Config YAML | none (custom build scripts, no gftools-builder config) |
+| Status | missing_commit |
+| Confidence | MEDIUM |
+
+## Source Data (METADATA.pb)
+
+```
+source {
+ repository_url: "https://github.com/BlackFoundryCom/InriaFonts"
+}
+```
+
+## Investigation
+
+The family was added to google/fonts on 2019-12-05 at 15:53 UTC+1 (commit `1878f904fc`), in PR #2273 by Yanone. The commit message is "Added Inria Sans 1.2".
+
+The upstream repository at `https://github.com/BlackFoundryCom/InriaFonts` is cached at `upstream_repos/fontc_crater_cache/BlackFoundryCom/InriaFonts`. The repo contains UFO sources for both Inria Sans and Inria Serif under `masters/INRIA-SANS/` and `masters/INRIA-SERIF/`.
+
+The upstream commit history around the onboarding date shows:
+- `d13f0df3` — "Fresh Sans TTFs" — 2019-12-05 15:21 UTC+1 (by Yanone)
+- `2bb3549c` — "Fresh Serif TTFs" — 2019-12-05 15:34 UTC+1 (by Yanone)
+- `3accdda3` — "Bumped Inria Serif to Google Fonts specs" — 2019-12-05 15:33 UTC+1
+- `94732c5a` — "Separate build scripts for each family" — 2019-12-05 15:41 UTC+1
+- `8caa79ae` — "Merge pull request #8 from yanone/master" — 2019-12-06 11:19 UTC+1
+
+Since google/fonts was updated at 15:53 and the last upstream commit before that is `94732c5a` at 15:41, the onboarding was most likely from commit `94732c5a`. The "Fresh Sans TTFs" commit (`d13f0df3`) at 15:21 may also be a candidate.
+
+**Source format**: The repository uses `.ufo` files (UFO format), not `.glyphs` or `.designspace`. There is **no `config.yaml`** in the upstream repository. Build was done using a custom `build-sans.sh` / `build-serif.sh` shell script using `fontmake` directly.
+
+The METADATA.pb currently has `repository_url` but no `commit` field. An override `config.yaml` would be needed since the upstream repo has no gftools-builder configuration.
+
+Note: Inria Sans (PR #2273) and Inria Serif (PR #2272) were both contributed by Yanone at the same time, and Yanone is also the author of the upstream commits.
+
+## Conclusion
+
+The `repository_url` is present and correct. The `commit` field is missing. The upstream repository uses UFO sources but has no `config.yaml` — the build was done with custom scripts. An override `config.yaml` would need to be created pointing to the UFO sources. The most likely onboarding commit is `94732c5a` ("Separate build scripts for each family") or `d13f0df3` ("Fresh Sans TTFs"), both from 2019-12-05.
+
+Action needed: Identify the correct onboarding commit (likely `94732c5a` or `d13f0df3`), create an override `config.yaml`, and update METADATA.pb to add the `commit` field.
--- /dev/null
+# Investigation: Inria Serif
+
+## Summary
+
+| Field | Value |
+|-------|-------|
+| Family Name | Inria Serif |
+| Slug | inria-serif |
+| License Dir | ofl |
+| Repository URL | https://github.com/BlackFoundryCom/InriaFonts |
+| Commit Hash | unknown |
+| Config YAML | none (custom build scripts, no gftools-builder config) |
+| Status | missing_commit |
+| Confidence | MEDIUM |
+
+## Source Data (METADATA.pb)
+
+```
+source {
+ repository_url: "https://github.com/BlackFoundryCom/InriaFonts"
+}
+```
+
+## Investigation
+
+The family was added to google/fonts on 2019-12-05 at 15:55 UTC+1 (commit `a2b3b38b97`), in PR #2272 by Yanone. The commit message is "Added Inria Serif 1.0".
+
+The upstream repository at `https://github.com/BlackFoundryCom/InriaFonts` is cached at `upstream_repos/fontc_crater_cache/BlackFoundryCom/InriaFonts`. The repo contains UFO sources for both Inria Sans and Inria Serif under `masters/INRIA-SANS/` and `masters/INRIA-SERIF/`.
+
+The upstream commit history around the onboarding date shows:
+- `d13f0df3` — "Fresh Sans TTFs" — 2019-12-05 15:21 UTC+1 (by Yanone)
+- `2bb3549c` — "Fresh Serif TTFs" — 2019-12-05 15:34 UTC+1 (by Yanone)
+- `3accdda3` — "Bumped Inria Serif to Google Fonts specs" — 2019-12-05 15:33 UTC+1
+- `94732c5a` — "Separate build scripts for each family" — 2019-12-05 15:41 UTC+1
+- `8caa79ae` — "Merge pull request #8 from yanone/master" — 2019-12-06 11:19 UTC+1
+
+Since google/fonts was updated at 15:55 and the last upstream commit before that is `94732c5a` at 15:41, the onboarding for Inria Serif was most likely from commit `94732c5a`. The serif-specific commit `2bb3549c` ("Fresh Serif TTFs") at 15:34 is also a candidate.
+
+**Source format**: The repository uses `.ufo` files (UFO format), not `.glyphs` or `.designspace`. There is **no `config.yaml`** in the upstream repository. Build was done using a custom `build-sans.sh` / `build-serif.sh` shell script using `fontmake` directly.
+
+The METADATA.pb currently has `repository_url` but no `commit` field. An override `config.yaml` would be needed since the upstream repo has no gftools-builder configuration.
+
+Note: Inria Sans (PR #2273) and Inria Serif (PR #2272) were both contributed by Yanone at the same time. The upstream repo is shared (both families are in the same repository).
+
+## Conclusion
+
+The `repository_url` is present and correct. The `commit` field is missing. The upstream repository uses UFO sources but has no `config.yaml` — the build was done with custom scripts. An override `config.yaml` would need to be created pointing to the UFO sources under `masters/INRIA-SERIF/`. The most likely onboarding commit is `94732c5a` ("Separate build scripts for each family") or `2bb3549c` ("Fresh Serif TTFs"), both from 2019-12-05.
+
+Action needed: Identify the correct onboarding commit (likely `94732c5a` or `2bb3549c`), create an override `config.yaml`, and update METADATA.pb to add the `commit` field.
--- /dev/null
+# Investigation: Inspiration
+
+## Summary
+
+| Field | Value |
+|-------|-------|
+| Family Name | Inspiration |
+| Slug | inspiration |
+| License Dir | ofl |
+| Repository URL | https://github.com/googlefonts/inspiration |
+| Commit Hash | 629ca27262fbcc6cfe745bd95d2e7b72a8e3b047 |
+| Config YAML | override config.yaml in google/fonts (ofl/inspiration/config.yaml) |
+| Status | complete |
+| Confidence | HIGH |
+
+## Source Data (METADATA.pb)
+
+```
+source {
+ repository_url: "https://github.com/googlefonts/inspiration"
+ commit: "629ca27262fbcc6cfe745bd95d2e7b72a8e3b047"
+ files {
+ source_file: "OFL.txt"
+ dest_file: "OFL.txt"
+ }
+ files {
+ source_file: "DESCRIPTION.en_us.html"
+ dest_file: "DESCRIPTION.en_us.html"
+ }
+ files {
+ source_file: "fonts/ttf/Inspiration-Regular.ttf"
+ dest_file: "Inspiration-Regular.ttf"
+ }
+ branch: "master"
+}
+```
+
+## Investigation
+
+The font was added to google/fonts in commit `245758c4d` ("Inspiration: Version 2.010; ttfautohint (v1.8.3) added (#4114)"). The commit body confirms the source:
+
+> Inspiration Version 2.010; ttfautohint (v1.8.3) taken from the upstream repo https://github.com/googlefonts/inspiration at commit https://github.com/googlefonts/inspiration/commit/629ca27262fbcc6cfe745bd95d2e7b72a8e3b047.
+
+The upstream repository is cached at `upstream_repos/fontc_crater_cache/googlefonts/inspiration`. The commit `629ca27262` was verified to exist in the cache. The log shows this commit was created on 2021-11-26 with message "v2.010 glyphs info updated".
+
+**Source format**: The repository contains `sources/InspirationPro.glyphs` (a single Glyphs source file). There is **no `config.yaml`** in the upstream repository itself.
+
+However, an override `config.yaml` exists in the google/fonts family directory at `ofl/inspiration/config.yaml` with content:
+```yaml
+buildVariable: false
+sources:
+ - sources/InspirationPro.glyphs
+```
+
+Per policy, when an override `config.yaml` exists locally, the `config_yaml` field in METADATA.pb is not needed. The current METADATA.pb does not set `config_yaml`, which is correct.
+
+The commit hash in METADATA.pb (`629ca27262`) matches the onboarding commit confirmed in the gftools-packager message. This is verified against the cached repo.
+
+## Conclusion
+
+The source block is complete and correct. The `repository_url` and `commit` are verified. An override `config.yaml` exists in the google/fonts directory. No changes needed.
--- /dev/null
+# Investigation: Instrument Sans
+
+## Summary
+
+| Field | Value |
+|-------|-------|
+| Family Name | Instrument Sans |
+| Slug | instrument-sans |
+| License Dir | ofl |
+| Repository URL | https://github.com/Instrument/instrument-sans |
+| Commit Hash | 7fa22308a3d0c94ee2b3cd537a1196b65db34a3e |
+| Config YAML | sources/config.yaml |
+| Status | complete |
+| Confidence | MEDIUM |
+
+## Source Data (METADATA.pb)
+
+```
+source {
+ repository_url: "https://github.com/Instrument/instrument-sans"
+ commit: "7fa22308a3d0c94ee2b3cd537a1196b65db34a3e"
+ files {
+ source_file: "OFL.txt"
+ dest_file: "OFL.txt"
+ }
+ files {
+ source_file: "fonts/variable/InstrumentSans[wdth,wght].ttf"
+ dest_file: "InstrumentSans[wdth,wght].ttf"
+ }
+ files {
+ source_file: "fonts/variable/InstrumentSans-Italic[wdth,wght].ttf"
+ dest_file: "InstrumentSans-Italic[wdth,wght].ttf"
+ }
+ branch: "master"
+ config_yaml: "sources/config.yaml"
+}
+```
+
+## Investigation
+
+The font was initially added to google/fonts in commit `2fc9491da` ("Instrument Sans: Version 1.000;gftools[0.9.28] added"). The original onboarding commit body stated:
+
+> Instrument Sans Version 1.000;gftools[0.9.28] taken from the upstream repo https://github.com/Instrument/instrument-sans at commit https://github.com/Instrument/instrument-sans/commit/4a27996becc1c7d8e8d4095df4bb485068252bb2.
+
+The METADATA.pb was subsequently updated by two commits:
+1. `66f91f10f` (2024-04-03) — "Merge upstream.yaml into METADATA.pb" — added `files` and `branch` fields, kept commit `4a27996`
+2. `19cdcec59` (2025-03-31) — "[Batch 1/4] port info from fontc_crater targets list" (by Felipe Sanches) — changed commit to `7fa22308a3d0c94ee2b3cd537a1196b65db34a3e` and added `config_yaml: "sources/config.yaml"`
+
+The upstream repository is cached at `upstream_repos/fontc_crater_cache/Instrument/instrument-sans`. **The repository has only a single commit**: `7fa22308a3d0c94ee2b3cd537a1196b65db34a3e` (2023-06-14, "feat: updated example gif"). The original onboarding commit `4a27996` does not exist in the current repository, indicating the repo was likely squash-reset or recreated.
+
+The current METADATA.pb commit `7fa22308` is the only commit in the repo and is verified to exist. The `sources/config.yaml` file exists in the upstream repo with `.glyphs` sources listed.
+
+**Source format**: The repository contains `sources/InstrumentSans.glyphs` and `sources/InstrumentSans-Italic.glyphs`. A `config.yaml` exists at `sources/config.yaml`.
+
+Note: Confidence is MEDIUM because the original onboarding commit (`4a27996`) no longer exists in the repo. The current commit hash (`7fa22308`) was set by the batch update from fontc_crater targets, which corresponds to the only available state of the repository.
+
+## Conclusion
+
+The source block is complete. The `repository_url`, `commit`, and `config_yaml` are all set. The commit hash was updated by Felipe Sanches in the fontc_crater batch update to match the only available commit in the repository. No further changes are strictly needed, though the discrepancy between the original onboarding commit (now gone) and the current commit should be noted.
--- /dev/null
+# Investigation: Instrument Serif
+
+## Summary
+
+| Field | Value |
+|-------|-------|
+| Family Name | Instrument Serif |
+| Slug | instrument-serif |
+| License Dir | ofl |
+| Repository URL | https://github.com/Instrument/instrument-serif |
+| Commit Hash | 65c0ef225f386a3c7e87570a4aa9cc0262c2fd81 |
+| Config YAML | sources/config.yaml |
+| Status | complete |
+| Confidence | MEDIUM |
+
+## Source Data (METADATA.pb)
+
+```
+source {
+ repository_url: "https://github.com/Instrument/instrument-serif"
+ commit: "65c0ef225f386a3c7e87570a4aa9cc0262c2fd81"
+ files {
+ source_file: "OFL.txt"
+ dest_file: "OFL.txt"
+ }
+ files {
+ source_file: "fonts/ttf/InstrumentSerif-Regular.ttf"
+ dest_file: "InstrumentSerif-Regular.ttf"
+ }
+ files {
+ source_file: "fonts/ttf/InstrumentSerif-Italic.ttf"
+ dest_file: "InstrumentSerif-Italic.ttf"
+ }
+ branch: "main"
+ config_yaml: "sources/config.yaml"
+}
+```
+
+## Investigation
+
+The font was initially added to google/fonts in commit `5e0122a40` ("Instrument Serif: Version 1.000; ttfautohint (v1.8.4.7-5d5b);gftools[0.9.23] added (#5981)"). The original onboarding commit body stated:
+
+> Instrument Serif Version 1.000; ttfautohint (v1.8.4.7-5d5b);gftools[0.9.27] taken from the upstream repo https://github.com/Instrument/instrument-serif at commit https://github.com/Instrument/instrument-serif/commit/9aefd76b9b96dffbdc7b65d38c0dc5bcae2717a9.
+
+The METADATA.pb was subsequently updated by two commits:
+1. `66f91f10f` (2024-04-03) — "Merge upstream.yaml into METADATA.pb" — added `files` and `branch` fields
+2. `19cdcec59` (2025-03-31) — "[Batch 1/4] port info from fontc_crater targets list" (by Felipe Sanches) — changed commit from `9aefd76b` to `65c0ef225f386a3c7e87570a4aa9cc0262c2fd81` and added `config_yaml: "sources/config.yaml"`
+
+The upstream repository is cached at `upstream_repos/fontc_crater_cache/Instrument/instrument-serif`. **The repository has only a single commit**: `65c0ef225f386a3c7e87570a4aa9cc0262c2fd81` (2023-04-26, "Update README.md"). The original onboarding commit `9aefd76b` does not exist in the current repository, indicating the repo was likely squash-reset or recreated.
+
+The current METADATA.pb commit `65c0ef22` is the only commit in the repo and is verified to exist. The `sources/config.yaml` file exists in the upstream repo.
+
+**Source format**: The repository contains `sources/Instrument_Serif.glyphs` and `sources/Instrument_Serif_Italic.glyphs`. A `config.yaml` exists at `sources/config.yaml` with content listing both Glyphs sources.
+
+Note: Confidence is MEDIUM because the original onboarding commit (`9aefd76b`) no longer exists in the repo. The current commit hash (`65c0ef22`) was set by the batch update from fontc_crater targets, corresponding to the only available state of the repository.
+
+## Conclusion
+
+The source block is complete. The `repository_url`, `commit`, and `config_yaml` are all set. The commit hash was updated by Felipe Sanches in the fontc_crater batch update to match the only available commit in the repository. No further changes are strictly needed.
--- /dev/null
+# Investigation: Intel One Mono
+
+## Summary
+
+| Field | Value |
+|-------|-------|
+| Family Name | Intel One Mono |
+| Slug | intel-one-mono |
+| License Dir | ofl |
+| Repository URL | https://github.com/intel/intel-one-mono |
+| Commit Hash | cec102c3890991d35e3766424923fa4afc099a1d |
+| Config YAML | override config.yaml in google/fonts (ofl/intelonemono/config.yaml) |
+| Status | needs_correction |
+| Confidence | LOW |
+
+## Source Data (METADATA.pb)
+
+```
+source {
+ repository_url: "https://github.com/intel/intel-one-mono"
+ commit: "cec102c3890991d35e3766424923fa4afc099a1d"
+ files {
+ source_file: "article/ARTICLE.en_us.html"
+ dest_file: "article/ARTICLE.en_us.html"
+ }
+ files {
+ source_file: "article/showing.png"
+ dest_file: "article/showing.png"
+ }
+ files {
+ source_file: "OFL.txt"
+ dest_file: "OFL.txt"
+ }
+ files {
+ source_file: "fonts/variable/IntelOneMono[wght].ttf"
+ dest_file: "IntelOneMono[wght].ttf"
+ }
+ files {
+ source_file: "fonts/variable/IntelOneMono-Italic[wght].ttf"
+ dest_file: "IntelOneMono-Italic[wght].ttf"
+ }
+ branch: "main"
+}
+```
+
+## Investigation
+
+The font was added to google/fonts in commit `f9bed585f` ("Intel One Mono: Version 1.004 added"). The original onboarding commit body stated:
+
+> Taken from the upstream repo https://github.com/googlefonts/intel-one-mono at commit https://github.com/googlefonts/intel-one-mono/commit/cec102c3890991d35e3766424923fa4afc099a1d.
+
+This means the original onboarding used the **googlefonts/intel-one-mono mirror**, not the canonical `intel/intel-one-mono` repository.
+
+The METADATA.pb was subsequently updated in commit `d0e1cc42c` (2025-06-03, "intelonemono: add hinted statics" by Marc Foley) which changed:
+- `repository_url` from `https://github.com/googlefonts/intel-one-mono` to `https://github.com/intel/intel-one-mono`
+- `copyright` fields from `googlefonts/intel-one-mono` to `intel/intel-one-mono`
+- **But the `commit` field `cec102c3` was NOT changed**
+
+This creates an inconsistency: the commit hash `cec102c3890991d35e3766424923fa4afc099a1d` comes from the `googlefonts/intel-one-mono` mirror but the `repository_url` now points to `intel/intel-one-mono`. This hash does **not exist** in the `intel/intel-one-mono` repository (verified against the cached repo at `upstream_repos/fontc_crater_cache/intel/intel-one-mono`).
+
+Subsequent updates to google/fonts:
+- `d27aca07a` — "intelonemono: Update vf" — updated variable fonts only
+- `fbba48d1d` — "intelonemono: v1.005 add SemiBold instances" — added static instances
+
+**Source format**: The upstream repository uses `.designspace` and `.ufo` sources. There is **no `config.yaml`** in the intel/intel-one-mono repository itself.
+
+An override `config.yaml` exists in the google/fonts family directory at `ofl/intelonemono/config.yaml`:
+```yaml
+sources:
+ - sources/masters/IntelOneMono-Roman.designspace
+ - sources/masters/IntelOneMono-Italic.designspace
+```
+
+Per policy, when an override `config.yaml` exists locally, the `config_yaml` field in METADATA.pb is not needed. The current METADATA.pb does not set `config_yaml`, which is correct.
+
+## Conclusion
+
+The `repository_url` was corrected to point to the canonical `intel/intel-one-mono` repo, but the `commit` hash `cec102c3` was not updated and is now incorrect — it belongs to the `googlefonts/intel-one-mono` mirror, not the canonical repo. The correct commit from `intel/intel-one-mono` that corresponds to version 1.004 needs to be identified. The override `config.yaml` in google/fonts correctly references the designspace sources.
+
+Action needed: Find the commit hash in `intel/intel-one-mono` that corresponds to version 1.004 (the version that was onboarded via the googlefonts mirror at `cec102c3`) and update the `commit` field in METADATA.pb.
--- /dev/null
+# Investigation: Inter
+
+## Summary
+
+| Field | Value |
+|-------|-------|
+| Family Name | Inter |
+| Slug | inter |
+| License Dir | ofl |
+| Repository URL | https://www.github.com/rsms/inter |
+| Commit Hash | 66647c0bbbe41a850d79d9c76fb13add3378940f |
+| Config YAML | override config.yaml in google/fonts (ofl/inter/config.yaml) |
+| Status | complete |
+| Confidence | HIGH |
+
+## Source Data (METADATA.pb)
+
+```
+source {
+ repository_url: "https://www.github.com/rsms/inter"
+ commit: "66647c0bbbe41a850d79d9c76fb13add3378940f"
+ archive_url: "https://github.com/rsms/inter/files/15438431/Inter-4.1-GoogleFonts.zip"
+ files {
+ source_file: "Inter[opsz,wght].ttf"
+ dest_file: "Inter[opsz,wght].ttf"
+ }
+ files {
+ source_file: "Inter-Italic[opsz,wght].ttf"
+ dest_file: "Inter-Italic[opsz,wght].ttf"
+ }
+ branch: "master"
+}
+```
+
+## Investigation
+
+The font was most recently updated in google/fonts by commit `e1d648010` ("Inter: Version 4.001;git-66647c0bb added"). The commit body confirms:
+
+> Taken from the upstream repo https://www.github.com/rsms/inter at commit https://www.github.com/rsms/inter/commit/66647c0bbbe41a850d79d9c76fb13add3378940f.
+> Resolves #3429
+
+The METADATA.pb uses an `archive_url` (a zip file from a GitHub release) as the actual source for the font binaries. This is a special case — the fonts were taken from a pre-built release archive rather than built from source.
+
+The upstream repository is cached at `upstream_repos/fontc_crater_cache/rsms/inter`. The commit `66647c0bbbe41a850d79d9c76fb13add3378940f` was verified to exist in the cached repo (2024-05-24, "makefile: make sure dist runs googlefonts so that dist_zip_gf succeed").
+
+The `repository_url` uses `www.github.com` instead of `github.com` — this is a minor inconsistency but functional.
+
+**Source format**: The repository contains `src/Inter-Roman.glyphspackage` and `src/Inter-Italic.glyphspackage` (Glyphs Package format). There is **no `config.yaml`** in the upstream repository.
+
+An override `config.yaml` exists in the google/fonts family directory at `ofl/inter/config.yaml`:
+```yaml
+sources:
+ - src/Inter-Roman.glyphspackage
+ - src/Inter-Italic.glyphspackage
+familyName: Inter
+buildVariable: true
+buildOTF: false
+```
+
+Per policy, when an override `config.yaml` exists locally, the `config_yaml` field in METADATA.pb is not needed. The current METADATA.pb does not set `config_yaml`, which is correct.
+
+The family also has a `minisite_url: "https://rsms.me/inter"` field.
+
+## Conclusion
+
+The source block is complete and correct. The `repository_url` and `commit` are verified against the cached repo. An override `config.yaml` exists in the google/fonts directory. The `archive_url` field indicates fonts were taken from a pre-built release zip rather than built from source. No changes are strictly needed. The `www.github.com` URL prefix is a minor cosmetic inconsistency but functional.
--- /dev/null
+# Investigation: Inter Tight
+
+## Summary
+
+| Field | Value |
+|-------|-------|
+| Family Name | Inter Tight |
+| Slug | inter-tight |
+| License Dir | ofl |
+| Repository URL | https://github.com/rsms/inter-gf-tight |
+| Commit Hash | c194f94c60b569b47876811321f5ef1f0c2614a2 |
+| Config YAML | sources/config.yaml |
+| Status | complete |
+| Confidence | HIGH |
+
+## Source Data (METADATA.pb)
+
+```
+source {
+ repository_url: "https://github.com/rsms/inter-gf-tight"
+ commit: "c194f94c60b569b47876811321f5ef1f0c2614a2"
+ files {
+ source_file: "OFL.txt"
+ dest_file: "OFL.txt"
+ }
+ files {
+ source_file: "fonts/variable/InterTight[wght].ttf"
+ dest_file: "InterTight[wght].ttf"
+ }
+ files {
+ source_file: "fonts/variable/InterTight-Italic[wght].ttf"
+ dest_file: "InterTight-Italic[wght].ttf"
+ }
+ branch: "main"
+ config_yaml: "sources/config.yaml"
+}
+```
+
+## Investigation
+
+The font was most recently updated in google/fonts by commit `fac60545c` ("Inter Tight: Version 3.004 added (#5681)"). The commit body confirms:
+
+> Inter Tight Version 3.004 taken from the upstream repo https://github.com/rsms/inter-gf-tight at commit https://github.com/rsms/inter-gf-tight/commit/c194f94c60b569b47876811321f5ef1f0c2614a2.
+
+The upstream repository is cached at `upstream_repos/fontc_crater_cache/rsms/inter-gf-tight`. The commit `c194f94c60b569b47876811321f5ef1f0c2614a2` was verified to exist in the cached repo (2022-12-08, "very quick fix on some obvious spacing issues in Greek script"). This is the **only commit** in the repository.
+
+**Source format**: The repository contains `sources/InterTight.glyphs` and `sources/InterTight-Italic.glyphs` (Glyphs format). A `config.yaml` exists at `sources/config.yaml` with content:
+```yaml
+sources:
+ - InterTight.glyphs
+ - InterTight-Italic.glyphs
+buildOTF: False
+axisOrder:
+ - wght
+ - ital
+familyName: Inter Tight
+```
+
+The `config_yaml: "sources/config.yaml"` in METADATA.pb is correctly set and matches the file in the upstream repo.
+
+The copyright notice references `https://github.com/rsms/inter-tight` which is a different repository name than the actual repo used (`inter-gf-tight`). This discrepancy is noted but does not affect the source tracking.
+
+Note: The font was also updated in earlier commits `0f620f526` (Version 3.003) and `87338f0ad` (Version 3.002). The current METADATA.pb commit `c194f94c` corresponds to the latest version (3.004).
+
+## Conclusion
+
+The source block is complete and correct. The `repository_url`, `commit`, and `config_yaml` are all verified. The commit `c194f94c` exists in the cached repository and is the only commit in the `inter-gf-tight` repo. No changes needed.
--- /dev/null
+# Iosevka Charon — Investigation Report
+
+**Date**: 2026-03-03
+**Model**: Claude Opus 4.6
+**Family slug**: `iosevkacharon`
+**Status**: complete (no config — Iosevka custom build system)
+
+## Initial State
+
+METADATA.pb already contained a complete source block with:
+- `repository_url`: `https://github.com/jul-sh/iosevka-charon`
+- `commit`: `727f1343e957cadd354f9ec4ee98eba9b645143d`
+- `archive_url`: `https://github.com/jul-sh/iosevka-charon/releases/download/v34.100/iosevka-charon.zip`
+- `branch`: `main`
+- File mappings for all 8 TTF files (Light, LightItalic, Regular, Italic, Medium, MediumItalic, Bold, BoldItalic) from `iosevkacharon/` subdirectory in the release archive
+- No `config_yaml` field (expected — see below)
+- No override `config.yaml` in the google/fonts family directory
+- No DESCRIPTION.en_us.html file
+
+## Investigation
+
+### Onboarding History
+
+The font was onboarded via **PR #10245** ("Iosevka Charon: Version 34.100 added"), authored by **Emma Marichal** (emmamarichal), created on 2026-02-19 and merged on 2026-02-27.
+
+The initial commit `3d418cc3ab7320c8493efebdb8048d24f3c65e25` explicitly references the upstream repo and commit:
+> "Taken from the upstream repo https://github.com/jul-sh/iosevka-charon at commit https://github.com/jul-sh/iosevka-charon/commit/727f1343e957cadd354f9ec4ee98eba9b645143d."
+
+The PR body repeats this same information. The PR contained 5 commits total:
+1. `3d418cc` — Initial onboarding (fonts, METADATA.pb, OFL.txt)
+2. `335885b` — Add article
+3. `ac3fea7` — Update OFL link
+4. `a7c1e55` — Fix formatting and content of OFL.txt
+5. `13394c5` — Refine description of Iosevka Charon font
+
+A sibling PR #10247 ("Iosevka Charon Mono: Version 34.100 added") was also merged on the same date for the monospace variant.
+
+### Commit Hash Verification
+
+The referenced commit `727f1343e957cadd354f9ec4ee98eba9b645143d` was verified in the upstream repo:
+- It is a merge commit dated **2026-02-13**: "Merge pull request #16 from jul-sh/v34.1.0-w-almost-flat-top"
+- It is tagged as **v34.100** in the upstream repo
+- The `pre-727f1343e957cadd354f9ec4ee98eba9b645143d` tag also exists, pointing to the same commit
+- The archive URL (`v34.100` release) corresponds to this exact commit
+
+Timeline is consistent: upstream commit (Feb 13) predates the google/fonts onboarding commit (Feb 19) and PR merge (Feb 27).
+
+Two commits exist after the referenced commit in the upstream repo:
+- `5501bc4` (2026-02-20) — "Update README description" (README.md only)
+- `343fcf7` (2026-02-20) — "Fix stray conflict marker text in README" (README.md only)
+
+Both are documentation-only changes that do not affect font files.
+
+### Build System Analysis
+
+Iosevka Charon uses a **custom build system** that is fundamentally incompatible with gftools-builder:
+- Fonts are built from the [Iosevka](https://github.com/be5invis/Iosevka) source using a Node.js-based build pipeline
+- The `sources/iosevka/` directory is a git subtree of the upstream Iosevka project
+- Build configuration is in `sources/private-build-plans.toml` (TOML format, Iosevka-specific)
+- The build process uses a Makefile with Nix-based dependency management
+- Post-processing scripts in `scripts/` handle Google Fonts compliance
+- There are **no** `.glyphs`, `.ufo`, or `.designspace` files — the source format is Iosevka's custom parametric system
+
+Since there are no gftools-builder compatible sources, a `config.yaml` is neither present nor applicable. The fonts are distributed as pre-built TTFs via GitHub releases, and the `archive_url` + `files` mapping in METADATA.pb correctly reflects this distribution method.
+
+### Repository Details
+
+- **Owner/Repo**: jul-sh/iosevka-charon
+- **Designer**: Juliette Pluto (jul-sh)
+- **License**: SIL OFL 1.1 (fonts), MIT (code/docs)
+- **Copyright**: "Copyright 2015-2025 The Iosevka Project Authors (https://github.com/be5invis/Iosevka)"
+
+## Actions Taken
+
+No changes were needed. The source block in METADATA.pb is already complete and accurate. The upstream repo was cloned to the cache at `upstream_repos/fontc_crater_cache/jul-sh/iosevka-charon/` for reference.
+
+## Final State
+
+The METADATA.pb source block is complete with repository URL, commit hash, archive URL, branch, and file mappings. No `config_yaml` is needed because the project uses Iosevka's custom build system (not gftools-builder). The commit hash `727f134` has been verified against the upstream repo and matches the v34.100 tag.
+
+## Source Block
+
+```
+source {
+ repository_url: "https://github.com/jul-sh/iosevka-charon"
+ commit: "727f1343e957cadd354f9ec4ee98eba9b645143d"
+ archive_url: "https://github.com/jul-sh/iosevka-charon/releases/download/v34.100/iosevka-charon.zip"
+ files {
+ source_file: "OFL.txt"
+ dest_file: "OFL.txt"
+ }
+ files {
+ source_file: "iosevkacharon/IosevkaCharon-Light.ttf"
+ dest_file: "IosevkaCharon-Light.ttf"
+ }
+ files {
+ source_file: "iosevkacharon/IosevkaCharon-LightItalic.ttf"
+ dest_file: "IosevkaCharon-LightItalic.ttf"
+ }
+ files {
+ source_file: "iosevkacharon/IosevkaCharon-Regular.ttf"
+ dest_file: "IosevkaCharon-Regular.ttf"
+ }
+ files {
+ source_file: "iosevkacharon/IosevkaCharon-Italic.ttf"
+ dest_file: "IosevkaCharon-Italic.ttf"
+ }
+ files {
+ source_file: "iosevkacharon/IosevkaCharon-Medium.ttf"
+ dest_file: "IosevkaCharon-Medium.ttf"
+ }
+ files {
+ source_file: "iosevkacharon/IosevkaCharon-MediumItalic.ttf"
+ dest_file: "IosevkaCharon-MediumItalic.ttf"
+ }
+ files {
+ source_file: "iosevkacharon/IosevkaCharon-Bold.ttf"
+ dest_file: "IosevkaCharon-Bold.ttf"
+ }
+ files {
+ source_file: "iosevkacharon/IosevkaCharon-BoldItalic.ttf"
+ dest_file: "IosevkaCharon-BoldItalic.ttf"
+ }
+ branch: "main"
+}
+```
--- /dev/null
+# Iosevka Charon Mono — Investigation Report
+
+**Date**: 2026-03-03
+**Model**: Claude Opus 4.6
+**Family slug**: `iosevkacharonmono`
+**Status**: complete (archive-based onboarding, no gftools-builder config applicable)
+
+## Initial State
+
+The METADATA.pb at `ofl/iosevkacharonmono/METADATA.pb` already contained a complete `source { }` block:
+
+```
+source {
+ repository_url: "https://github.com/jul-sh/iosevka-charon"
+ commit: "727f1343e957cadd354f9ec4ee98eba9b645143d"
+ archive_url: "https://github.com/jul-sh/iosevka-charon/releases/download/v34.100/iosevka-charon.zip"
+ files { source_file: "OFL.txt" dest_file: "OFL.txt" }
+ files { source_file: "iosevkacharonmono/IosevkaCharonMono-Light.ttf" dest_file: "IosevkaCharonMono-Light.ttf" }
+ files { source_file: "iosevkacharonmono/IosevkaCharonMono-LightItalic.ttf" dest_file: "IosevkaCharonMono-LightItalic.ttf" }
+ files { source_file: "iosevkacharonmono/IosevkaCharonMono-Regular.ttf" dest_file: "IosevkaCharonMono-Regular.ttf" }
+ files { source_file: "iosevkacharonmono/IosevkaCharonMono-Italic.ttf" dest_file: "IosevkaCharonMono-Italic.ttf" }
+ files { source_file: "iosevkacharonmono/IosevkaCharonMono-Medium.ttf" dest_file: "IosevkaCharonMono-Medium.ttf" }
+ files { source_file: "iosevkacharonmono/IosevkaCharonMono-MediumItalic.ttf" dest_file: "IosevkaCharonMono-MediumItalic.ttf" }
+ files { source_file: "iosevkacharonmono/IosevkaCharonMono-Bold.ttf" dest_file: "IosevkaCharonMono-Bold.ttf" }
+ files { source_file: "iosevkacharonmono/IosevkaCharonMono-BoldItalic.ttf" dest_file: "IosevkaCharonMono-BoldItalic.ttf" }
+ branch: "main"
+}
+```
+
+The family directory contained 8 TTF files (Light, LightItalic, Regular, Italic, Medium, MediumItalic, Bold, BoldItalic), METADATA.pb, OFL.txt, and an article directory with ARTICLE.en_us.html. No DESCRIPTION.en_us.html and no override config.yaml were present.
+
+## Investigation
+
+### Upstream Repository
+
+The upstream repository is https://github.com/jul-sh/iosevka-charon, maintained by Juliette Pluto (jul-sh). The repository was created on 2021-10-31 and describes both "Iosevka Charon" (quasi-proportional) and "Iosevka Charon Mono" (true monospace) as derivatives of the Iosevka open source font project by be5invis.
+
+### Build System
+
+This font does NOT use gftools-builder and has no `.glyphs`, `.ufo`, or `.designspace` source files. Instead, it uses Iosevka's own parametric build system:
+
+1. **Source**: The Iosevka source code is embedded as a git subtree under `sources/iosevka/`
+2. **Build plans**: Font variants are defined in `sources/private-build-plans.toml` — a TOML configuration that specifies character variants, weights (Light/300, Regular/400, Medium/500, Bold/700), slopes (Upright, Italic), and spacing (quasi-proportional for Charon, normal monospace for Charon Mono)
+3. **Build pipeline**: A `Makefile` orchestrates a multi-stage build:
+ - Stage 1: `scripts/iosevka_build.py` compiles raw fonts from Iosevka sources using the build plan
+ - Stage 2: `scripts/fix_fonts.py` post-processes fonts for Google Fonts compliance (vertical metrics, component flattening, copyright notices, etc.)
+4. **Environment**: The build uses Nix (flake.nix) for reproducible dependency management
+5. **Distribution**: Pre-built TTFs are published as GitHub Release assets
+
+Since gftools-builder cannot build Iosevka-based fonts (they require Node.js and the Iosevka build toolchain), no `config.yaml` is applicable. The fonts are onboarded via the `archive_url` and `files` mapping mechanism in METADATA.pb.
+
+### Commit Hash Verification
+
+The commit `727f1343e957cadd354f9ec4ee98eba9b645143d` was verified against the upstream repository:
+
+- **Commit message**: "Merge pull request #16 from jul-sh/v34.1.0-w-almost-flat-top — v34.1.0: w = curly-almost-flat-top-serifless"
+- **Commit date**: 2026-02-13T16:09:26Z
+- **Author**: jul-sh
+- **Release**: This commit corresponds exactly to the `v34.100` release tag, created at the same timestamp (2026-02-13T16:09:26Z)
+
+The archive_url `https://github.com/jul-sh/iosevka-charon/releases/download/v34.100/iosevka-charon.zip` correctly points to the v34.100 release asset.
+
+Two subsequent commits were found between the referenced commit and the PR merge date (2026-02-27):
+- `5501bc426a3f` (2026-02-20): "Update README description"
+- `343fcf7a5004` (2026-02-20): "Fix stray conflict marker text in README"
+
+These are documentation-only changes and do not affect font files or build configuration, confirming the referenced commit is correct for the font binaries.
+
+### Google Fonts PR History
+
+The font was onboarded via PR [#10247](https://github.com/google/fonts/pull/10247):
+- **Title**: "Iosevka Charon Mono: Version 34.100 added"
+- **Author**: Emma Marichal (@emmamarichal)
+- **Created**: 2026-02-19
+- **Merged**: 2026-02-27 by Marc Foley (@m4rc1e)
+- **Body**: "Taken from the upstream repo https://github.com/jul-sh/iosevka-charon at commit https://github.com/jul-sh/iosevka-charon/commit/727f1343e957cadd354f9ec4ee98eba9b645143d."
+
+The google/fonts commit history for this directory shows 4 commits:
+1. `691932aca` (2026-02-19): "Iosevka Charon Mono: Version 34.100 added" — initial onboarding with font files, METADATA.pb, and OFL.txt
+2. `34457f077` (2026-02-19): "article" — added ARTICLE.en_us.html
+3. `7a0413213` (2026-02-19): "OFL update"
+4. `c7f2c84d2` (2026-02-20): "Refine description of Iosevka Charon font"
+
+### Sibling Family
+
+The repository also produces "Iosevka Charon" (quasi-proportional variant), onboarded in the sibling directory `ofl/iosevkacharon/` via PR [#10245](https://github.com/google/fonts/pull/10245).
+
+### Copyright
+
+The font copyright reads: "Copyright 2015-2025 The Iosevka Project Authors (https://github.com/be5invis/Iosevka)" — referring to the upstream Iosevka project from which Iosevka Charon derives.
+
+## Actions Taken
+
+No changes were needed. The METADATA.pb already contained a complete and accurate source block. The investigation verified all existing metadata:
+- Repository URL is valid and accessible
+- Commit hash matches the v34.100 release and is the correct onboarding commit
+- Archive URL points to the correct release asset
+- File mappings correctly reference paths within the release ZIP
+- Branch field is set to "main"
+
+## Final State
+
+The source block in METADATA.pb is complete and correct. No `config_yaml` field is needed because the font uses Iosevka's custom build system, not gftools-builder. The fonts are distributed as pre-built binaries via GitHub Releases, and the `archive_url` + `files` mechanism properly handles this onboarding pattern.
+
+The upstream repo is not yet cloned in the local cache at `upstream_repos/fontc_crater_cache/`. If needed, it can be cloned to `upstream_repos/fontc_crater_cache/jul-sh/iosevka-charon/`.
+
+## Source Block
+
+The existing source block is complete and verified:
+
+```
+source {
+ repository_url: "https://github.com/jul-sh/iosevka-charon"
+ commit: "727f1343e957cadd354f9ec4ee98eba9b645143d"
+ archive_url: "https://github.com/jul-sh/iosevka-charon/releases/download/v34.100/iosevka-charon.zip"
+ files {
+ source_file: "OFL.txt"
+ dest_file: "OFL.txt"
+ }
+ files {
+ source_file: "iosevkacharonmono/IosevkaCharonMono-Light.ttf"
+ dest_file: "IosevkaCharonMono-Light.ttf"
+ }
+ files {
+ source_file: "iosevkacharonmono/IosevkaCharonMono-LightItalic.ttf"
+ dest_file: "IosevkaCharonMono-LightItalic.ttf"
+ }
+ files {
+ source_file: "iosevkacharonmono/IosevkaCharonMono-Regular.ttf"
+ dest_file: "IosevkaCharonMono-Regular.ttf"
+ }
+ files {
+ source_file: "iosevkacharonmono/IosevkaCharonMono-Italic.ttf"
+ dest_file: "IosevkaCharonMono-Italic.ttf"
+ }
+ files {
+ source_file: "iosevkacharonmono/IosevkaCharonMono-Medium.ttf"
+ dest_file: "IosevkaCharonMono-Medium.ttf"
+ }
+ files {
+ source_file: "iosevkacharonmono/IosevkaCharonMono-MediumItalic.ttf"
+ dest_file: "IosevkaCharonMono-MediumItalic.ttf"
+ }
+ files {
+ source_file: "iosevkacharonmono/IosevkaCharonMono-Bold.ttf"
+ dest_file: "IosevkaCharonMono-Bold.ttf"
+ }
+ files {
+ source_file: "iosevkacharonmono/IosevkaCharonMono-BoldItalic.ttf"
+ dest_file: "IosevkaCharonMono-BoldItalic.ttf"
+ }
+ branch: "main"
+}
+```
--- /dev/null
+# Investigation: Island Moments
+
+## Summary
+
+| Field | Value |
+|-------|-------|
+| Family Name | Island Moments |
+| Slug | island-moments |
+| License Dir | ofl |
+| Repository URL | https://github.com/googlefonts/island-moments |
+| Commit Hash | 665d59f297c782358f09699fc2231c0eee293f25 |
+| Config YAML | sources/config.yml |
+| Status | complete |
+| Confidence | HIGH |
+
+## Source Data (METADATA.pb)
+
+```
+source {
+ repository_url: "https://github.com/googlefonts/island-moments"
+ commit: "665d59f297c782358f09699fc2231c0eee293f25"
+ files {
+ source_file: "OFL.txt"
+ dest_file: "OFL.txt"
+ }
+ files {
+ source_file: "DESCRIPTION.en_us.html"
+ dest_file: "DESCRIPTION.en_us.html"
+ }
+ files {
+ source_file: "fonts/ttf/IslandMoments-Regular.ttf"
+ dest_file: "IslandMoments-Regular.ttf"
+ }
+ branch: "master"
+ config_yaml: "sources/config.yml"
+}
+```
+
+## Investigation
+
+The font was added to google/fonts in commit `4eeaeee72` ("Island Moments: Version 1.010 added (#4085)"). The commit body confirms:
+
+> Island Moments Version 1.010 taken from the upstream repo https://github.com/googlefonts/island-moments at commit https://github.com/googlefonts/island-moments/commit/665d59f297c782358f09699fc2231c0eee293f25.
+
+The upstream repository is cached at `upstream_repos/fontc_crater_cache/googlefonts/island-moments`. The commit `665d59f297c782358f09699fc2231c0eee293f25` was verified to exist in the cached repo. The repo has **only one commit** (2021-11-11, "sample image updated") which matches the METADATA.pb.
+
+**Source format**: The repository contains `sources/IslandMomentsPro.glyphs` (a single Glyphs source file). A `config.yml` exists at `sources/config.yml`:
+```yaml
+sources:
+ - IslandMomentsPro.glyphs
+familyName: "Island Moments"
+buildVariable: false
+autohintTTF: false
+```
+
+The `config_yaml: "sources/config.yml"` in METADATA.pb is correctly set and the file exists in the upstream repo.
+
+## Conclusion
+
+The source block is complete and correct. The `repository_url`, `commit`, and `config_yaml` are all verified. The commit `665d59f` is the only commit in the repository and matches METADATA.pb exactly. No changes needed.
--- /dev/null
+# Investigation: Istok Web
+
+## Summary
+
+| Field | Value |
+|-------|-------|
+| Family Name | Istok Web |
+| Slug | istok-web |
+| License Dir | ofl |
+| Repository URL | unknown |
+| Commit Hash | unknown |
+| Config YAML | unknown |
+| Status | missing_url |
+| Confidence | LOW |
+
+## Source Data (METADATA.pb)
+
+```
+No source block
+```
+
+## Investigation
+
+The font is stored under `ofl/istokweb/` with an OFL license. The METADATA.pb has no `source` block at all.
+
+The font history in google/fonts shows:
+- `90abd17b4` — "Initial commit" — the font was present from the very beginning of the google/fonts repository (2015)
+
+The copyright states: "Copyright (c) 2008-2014, Andrey V. Panov (panov@canopus.iacp.dvo.ru), with Reserved Font Name Istok"
+
+The FONTLOG.txt in the google/fonts directory reveals:
+> The sources and truetype fonts are available at http://code.google.com/p/istok/
+
+This points to **Google Code** (code.google.com/p/istok), which has been shut down since 2016. The font sources were originally hosted on Google Code, not GitHub.
+
+The FONTLOG also describes the build requirements:
+> "You need fontforge (http://fontforge.sourceforge.net/), TTX/FontTools, xgridfit (http://xgridfit.sourceforge.net/ - version as of April 2010) and font-helpers (http://code.google.com/p/font-helpers/) in order to build the truetype fonts from the sources."
+
+The sources were in SFD format (FontForge native format) based on the build instructions mentioning fontforge and xgridfit. There is no known GitHub mirror of the original Google Code repository.
+
+No cached upstream repository was found in `upstream_repos/fontc_crater_cache/` for this family.
+
+The designer is Andrey V. Panov (email: panov@canopus.iacp.dvo.ru). The font supports Latin and Cyrillic scripts.
+
+## Conclusion
+
+The original source repository was on Google Code (`http://code.google.com/p/istok/`) which has been shut down. No GitHub repository has been identified. The source format was SFD (FontForge) files, and there is likely no modern gftools-builder compatible `config.yaml` possible for this font.
+
+Action needed: Check if there is a GitHub mirror of the Google Code repository, or if the font can be considered `no_config_possible` given its SFD source format and the Google Code origin.
--- /dev/null
+# Investigation: Italiana
+
+## Summary
+
+| Field | Value |
+|-------|-------|
+| Family Name | Italiana |
+| Slug | italiana |
+| License Dir | ofl |
+| Repository URL | unknown |
+| Commit Hash | unknown |
+| Config YAML | unknown |
+| Status | missing_url |
+| Confidence | LOW |
+
+## Source Data (METADATA.pb)
+
+```
+No source block
+```
+
+## Investigation
+
+The font is stored under `ofl/italiana/` with an OFL license. The METADATA.pb has no `source` block at all.
+
+The font history in google/fonts shows:
+- `90abd17b4` — "Initial commit" — the font was present from the very beginning of the google/fonts repository (2015)
+
+The copyright states: "Copyright (c) 2011 by Santiago Orozco (hi@typemade.mx) with reserved name Italiana"
+
+The FONTLOG.txt reveals:
+- Designer: Santiago Orozco (hi@typemade.mx, www.typemade.mx, Twitter: @Typemade)
+- Version 1.001 — Initial release on 11 March 2012
+- The font was designed for use in newspaper and magazine headlines, inspired by Italian calligraphy masters
+
+No GitHub repository has been identified for this font. The designer (Santiago Orozco / typemade.mx) appears to have submitted this font directly to Google Fonts. No cached upstream repository was found in `upstream_repos/fontc_crater_cache/` for this family.
+
+The font has only a regular weight (no italics or other variants), suggesting it may be a very early submission before version control workflows were established.
+
+The font date_added is "2012-03-14" and has never been updated in google/fonts since the initial commit.
+
+## Conclusion
+
+No upstream repository is known for this font. The font was contributed directly to google/fonts by Santiago Orozco of typemade.mx. No GitHub repository has been found for this designer's work on Italiana specifically.
+
+Action needed: Contact Santiago Orozco (hi@typemade.mx / @Typemade) to determine if source files are available and whether there is a repository for this font. If no upstream repo exists or can be created, document as `missing_url`.
--- /dev/null
+# Investigation: Italianno
+
+## Summary
+
+| Field | Value |
+|-------|-------|
+| Family Name | Italianno |
+| Slug | italianno |
+| License Dir | ofl |
+| Repository URL | https://github.com/googlefonts/italianno |
+| Commit Hash | 3e3995ef5b90bd2b9dc587fb8f831f3a158cb95b |
+| Config YAML | sources/config.yml |
+| Status | complete |
+| Confidence | MEDIUM |
+
+## Source Data (METADATA.pb)
+
+```
+source {
+ repository_url: "https://github.com/googlefonts/italianno"
+ commit: "3e3995ef5b90bd2b9dc587fb8f831f3a158cb95b"
+ files {
+ source_file: "OFL.txt"
+ dest_file: "OFL.txt"
+ }
+ files {
+ source_file: "DESCRIPTION.en_us.html"
+ dest_file: "DESCRIPTION.en_us.html"
+ }
+ files {
+ source_file: "fonts/ttf/Italianno-Regular.ttf"
+ dest_file: "Italianno-Regular.ttf"
+ }
+ branch: "master"
+ config_yaml: "sources/config.yml"
+}
+```
+
+## Investigation
+
+The font was most recently updated in google/fonts in commit `c7039c870` ("Italianno: Version 1.100; ttfautohint (v1.8.3) added (#3379)", 2021-05-05). The commit body confirms:
+
+> Italianno Version 1.100; ttfautohint (v1.8.3) taken from the upstream repo https://github.com/googlefonts/italianno at commit https://github.com/googlefonts/italianno/commit/d183cfb030ba783dd91c010926e315afe33815d0.
+
+The original onboarding commit was `d183cfb030ba783dd91c010926e315afe33815d0`. However, the current METADATA.pb shows commit `3e3995ef5b90bd2b9dc587fb8f831f3a158cb95b`.
+
+The upstream repository is cached at `upstream_repos/fontc_crater_cache/googlefonts/italianno`. The cached repo has **only one commit**: `3e3995ef5b90bd2b9dc587fb8f831f3a158cb95b` (2021-08-30, "original font file deleted" by Viviana Monsalve). The original commit `d183cfb` does **not** exist in the cached repository. This suggests the repository was recreated or its history was reset.
+
+The single commit `3e3995ef` in the current repo appears to be a fresh setup that added all the project files: `.github/workflows/CI-static-ttf.yml`, `.gitignore`, `AUTHORS.txt`, `CONTRIBUTORS.txt`, `DESCRIPTION.en_us.html`, `OFL.txt`, font files in `fonts/`, `requirements.txt`, `sources/Italianno.glyphs`, and `sources/config.yml`.
+
+**Source format**: The repository contains `sources/Italianno.glyphs` (a single Glyphs source file). A `config.yml` exists at `sources/config.yml`:
+```yaml
+sources:
+ - Italianno.glyphs
+familyName: "Italianno"
+buildVariable: false
+# autohintTTF: false
+```
+
+The commit `3e3995ef` in METADATA.pb is verified to exist in the cached repo. The `config_yaml: "sources/config.yml"` is correctly set and the file exists.
+
+Note: Confidence is MEDIUM because the original onboarding commit (`d183cfb`) no longer exists. The current commit (`3e3995ef`) represents a fresh setup of the repository after a reset. The fonts in google/fonts were built from `d183cfb`, not `3e3995ef`.
+
+## Conclusion
+
+The source block is structurally complete. The `repository_url`, `commit`, and `config_yaml` are all set. The commit `3e3995ef` exists in the current (single-commit) repository. However, this commit is the result of a repository reset — the actual onboarding commit `d183cfb` no longer exists. The current state is acceptable since the single existing commit includes all source files and the `config.yml`.
--- /dev/null
+# Investigation: Itim
+
+## Summary
+
+| Field | Value |
+|-------|-------|
+| Family Name | Itim |
+| Slug | itim |
+| License Dir | ofl |
+| Repository URL | https://github.com/cadsondemak/itim |
+| Commit Hash | eb5e37a5412ea61cbc048f57dad5a97285d470e1 |
+| Config YAML | override config.yaml in google/fonts (ofl/itim/config.yaml) |
+| Status | complete |
+| Confidence | HIGH |
+
+## Source Data (METADATA.pb)
+
+```
+source {
+ repository_url: "https://github.com/cadsondemak/itim"
+ commit: "eb5e37a5412ea61cbc048f57dad5a97285d470e1"
+}
+```
+
+## Investigation
+
+The font was added to google/fonts in commit `daa233403` ("Adding Itim"). The font's date_added is "2015-07-01".
+
+The METADATA.pb source block has only `repository_url` and `commit` — no `files`, no `branch`, no `config_yaml`.
+
+The upstream repository is cached at `upstream_repos/fontc_crater_cache/cadsondemak/itim`. The commit `eb5e37a5412ea61cbc048f57dad5a97285d470e1` was verified to exist in the cached repo (2015-06-27, "Merge pull request #1 from davelab6/master"). This matches the font's `date_added` of 2015-07-01 (within days), confirming this is the correct onboarding commit.
+
+**Source format**: The repository contains `sources/Itim-Regular.ufo`, `sources/Itim.glyphs`, `sources/Itim-Regular.vfb`, `sources/Itim-Regular_SS01.vfb`, and `sources/Itim-Regular_SS02.vfb`. There is **no `config.yaml`** in the upstream repository.
+
+An override `config.yaml` exists in the google/fonts family directory at `ofl/itim/config.yaml`:
+```yaml
+buildVariable: false
+sources:
+ - source/Itim-Regular.ufo
+```
+
+Per policy, when an override `config.yaml` exists locally, the `config_yaml` field in METADATA.pb is not needed. The current METADATA.pb does not set `config_yaml`, which is correct.
+
+Note: The copyright mentions Pablo Impallari for the initial OpenType handwriting feature development. The font supports Latin and Thai scripts.
+
+The git log for the upstream repo shows the commit `eb5e37a5` is the 3rd-oldest commit in the repository (2015-06-27), close to the initial push of font files.
+
+## Conclusion
+
+The source block has `repository_url` and `commit` correctly set. The commit `eb5e37a5` is verified against the cached repository. An override `config.yaml` exists in the google/fonts directory using the UFO source. No changes needed.
projects / thirdparty / google / fonts.git / commitdiff
