--- /dev/null
+# 42dot Sans
+
+**Date investigated**: 2026-03-03
+**Model**: Claude Opus 4.6
+**Status**: complete
+**Designer**: 42dot
+**METADATA.pb path**: `ofl/42dotsans/METADATA.pb`
+
+## Source Data
+
+| Field | Value |
+|-------|-------|
+| Repository URL | https://github.com/42dot/42dot-Sans |
+| Commit | `d23e87fe44d5b4f5afaa9dca9d5926d7c414d625` |
+| Config YAML | sources/config_variable.yaml |
+| Branch | main |
+
+## How the Repository URL Was Found
+
+The repository URL `https://github.com/42dot/42dot-Sans` was already present in the METADATA.pb source block. It is also referenced in the font's copyright string within METADATA.pb: `"Copyright 2024 The 42dot Sans Project Authors (https://github.com/42dot/42dot-Sans)."` The original onboarding commit (`d60948acd`) in google/fonts explicitly states: "Taken from the upstream repo https://github.com/42dot/42dot-Sans". The upstream repo is cached locally and confirmed accessible.
+
+## How the Commit Hash Was Identified
+
+The commit hash `d23e87fe44d5b4f5afaa9dca9d5926d7c414d625` is directly referenced in the original google/fonts onboarding commit (`d60948acd`, dated 2024-12-23). The onboarding commit message reads:
+
+> Taken from the upstream repo https://github.com/42dot/42dot-Sans at commit https://github.com/42dot/42dot-Sans/commit/d23e87fe44d5b4f5afaa9dca9d5926d7c414d625
+
+The upstream commit is dated 2024-12-23 05:50:28 (PST), and the google/fonts onboarding commit is dated 2024-12-23 05:51:32 (PST) -- just one minute later. This tight timing strongly confirms that `d23e87fe` was the exact commit used for onboarding.
+
+The upstream commit (by Aaron at sajatypeworks.com) is titled "Adding some metadata" and updated font binary files and fontinfo metadata. It was the most recent commit in the upstream repo at the time of onboarding.
+
+The source block (commit hash, config_yaml, branch) was added to METADATA.pb later by Felipe Sanches in commit `da0442cc` (2025-03-31), referencing PR #8772.
+
+## How Config YAML Was Resolved
+
+The config file `sources/config_variable.yaml` exists at the referenced commit `d23e87fe`. Its contents are:
+
+```yaml
+sources:
+ - 42dotSans.designspace
+familyName: 42dot Sans
+autohintTTF: False
+buildOTF: False
+buildStatic: False
+buildVariable: True
+buildWebfont: False
+removeOutlineOverlaps: False
+```
+
+This configuration builds a variable font from `42dotSans.designspace`, which aligns with the single variable font file `42dotSans[wght].ttf` found in google/fonts. No override config.yaml exists in the google/fonts family directory.
+
+## Notable History
+
+The font underwent a rename in google/fonts: commit `db2611132` (2025-04-30) renamed it from "42dotSans" to "AstaSans" (moving files from `ofl/42dotsans/` to `ofl/astasans/`). This corresponded to upstream commit `52c07071` ("name update 42dot Sans -> Asta Sans", 2025-04-22). However, this was subsequently reverted -- commit `572407623` (2025-05-02) re-added the `ofl/42dotsans/` directory from the main branch, restoring the original "42dot Sans" family. As a result, both `ofl/42dotsans/` and `ofl/astasans/` may coexist in the repository, but `42dotsans` is the canonical directory.
+
+## Conclusion
+
+The source metadata for 42dot Sans is **complete** with **HIGH confidence**. The commit hash is explicitly documented in the original onboarding commit message and the timestamps align precisely (1-minute gap). The config file exists at the specified path in the upstream repo at the referenced commit. All three key fields (repository_url, commit, config_yaml) are correct and verified.
--- /dev/null
+# ABeeZee
+
+**Date investigated**: 2026-02-26
+**Status**: complete
+**Designer**: Anja Meiners
+**METADATA.pb path**: `ofl/abeezee/METADATA.pb`
+
+## Source Data
+
+| Field | Value |
+|-------|-------|
+| Repository URL | https://github.com/googlefonts/abeezee |
+| Commit | `b9bd3f3522d91aca81eb668f56d40c2c62a90125` |
+| Config YAML | `sources/config.yaml` |
+| Branch | `main` |
+
+## How the Repository URL Was Found
+
+The repository URL was already present in the METADATA.pb `source { repository_url }` field, set to `https://github.com/googlefonts/abeezee`. This matches the copyright string in the font files ("Copyright 2011 The ABeeZee Project Authors (https://github.com/googlefonts/abeezee)"). The gftools-packager commit `a8bc01c6` in google/fonts also references this URL in its body.
+
+## How the Commit Hash Was Identified
+
+The current METADATA.pb commit hash is `b9bd3f3522d91aca81eb668f56d40c2c62a90125`. However, this does **not** match the original onboarding commit referenced by gftools-packager.
+
+The original font onboarding in google/fonts was done via PR #4265, with the gftools-packager commit `a8bc01c6` (2022-02-04) stating: "ABeeZee Version 1.003; ttfautohint (v1.8.3) taken from the upstream repo https://github.com/googlefonts/abeezee at commit https://github.com/googlefonts/abeezee/commit/a84aead1554a7adc09c6dd01161ac4a5a9f2c001."
+
+The original onboarding commit `a84aead1554a7adc09c6dd01161ac4a5a9f2c001` is **no longer present** in the upstream repository -- it appears the repository was force-pushed to a single commit. The current commit `b9bd3f35` (2022-02-04 16:00:44 +0100, message: "Merge pull request #4 from emmamarichal/main") is the only commit remaining in the repo. This commit was from the same day as the onboarding.
+
+The METADATA.pb source block was added by the batch commit `19cdcec59` ("[Batch 1/4] port info from fontc_crater targets list", 2025-03-31), which ported information from fontc_crater's target.json. The `b9bd3f35` commit hash was likely used as the latest available commit in the force-pushed repo.
+
+## How Config YAML Was Resolved
+
+The config file `sources/config.yaml` exists in the upstream repository at the recorded commit hash `b9bd3f35`. It contains gftools-builder configuration referencing two source files (`ABeeZee.glyphs` and `ABeeZee-Italic.glyphs`) with `buildVariable: false`. No override config.yaml exists in the google/fonts family directory (`ofl/abeezee/`).
+
+## Verification
+
+- Commit exists in upstream repo: Yes
+- Commit date: 2022-02-04 16:00:44 +0100
+- Commit message: "Merge pull request #4 from emmamarichal/main"
+- Source files at commit: `sources/ABeeZee-Italic.glyphs`, `sources/ABeeZee.glyphs`, `sources/config.yaml`
+
+## Confidence
+
+**Medium**: The repository URL is well-established and confirmed by multiple sources. However, the commit hash in METADATA.pb (`b9bd3f35`) does not match the original onboarding commit (`a84aead1`) cited by gftools-packager in PR #4265. The upstream repo appears to have been force-pushed, losing the original onboarding commit. The current commit `b9bd3f35` is the only commit remaining and is from the same day as the onboarding, so the source files are likely functionally equivalent. The config.yaml is present and valid. The discrepancy between the recorded and original onboarding commits is a known consequence of the repo being force-pushed.
+
+## Open Questions
+
+1. The original onboarding commit `a84aead1554a7adc09c6dd01161ac4a5a9f2c001` is no longer present in the upstream repo. Were source files modified between that commit and the current one (`b9bd3f35`)? Since both are from the same day (2022-02-04), the difference is likely minimal, but it cannot be verified.
--- /dev/null
+# Abhaya Libre
+
+**Date investigated**: 2026-03-03
+**Model**: Claude Opus 4.6
+**Status**: complete
+**Designer**: Mooniak
+**METADATA.pb path**: `ofl/abhayalibre/METADATA.pb`
+
+## Source Data
+
+| Field | Value |
+|-------|-------|
+| Repository URL | https://github.com/mooniak/abhaya-libre-font |
+| Commit | `f53da70786fe1dba6193bdbd45a2c4159e511079` |
+| Config YAML | `sources/config.yaml` (upstream) + local override `config.yaml` in google/fonts |
+| Branch | main |
+
+## How the Repository URL Was Found
+
+The repository URL `https://github.com/mooniak/abhaya-libre-font` was first added to METADATA.pb in commit `aec1b9f3e` (2023-12-20, "Add upstream repository URL"). The URL is consistent with the font's copyright notice, which lists "Mooniak (hello@mooniak.com)" as one of the copyright holders. The repo exists, is publicly accessible, and contains the source files for this font family.
+
+## How the Commit Hash Was Identified
+
+The commit hash has gone through three iterations in METADATA.pb:
+
+1. **`edaabf89`** (from fontc_crater targets, set in Batch 1/4 commit `19cdcec59` on 2025-03-31): This was "Adding fontpackage.toml" dated 2025-01-10. It does have `sources/config.yaml` because it's a descendant of the commit that introduced it. However, it's far newer than when the fonts were built.
+
+2. **`ade314aa`** (set in commit `04009b5bb` on 2025-03-31 by Felipe Sanches): This was "Adding description for Google Fonts" dated 2017-02-16. This is very close to when fonts were last updated in google/fonts via PR #665 (2017-02-17, "abhayalibre: v1.050 added"). This is the most historically accurate onboarding-era commit. However, `sources/config.yaml` does NOT exist at this commit (it was introduced in 2024).
+
+3. **`f53da707`** (current, set in commit `5862ed413` on 2025-05-22 by Felipe Sanches): This is "Update to GF repo tempalte and CI" dated 2024-05-31. The commit message says "Updated commit hash to the one that contains sources/config.yaml". This is the first commit on main where `sources/config.yaml` exists, since it was created by renaming `sources/builder.yaml` to `sources/config.yaml` in that commit.
+
+**Assessment**: The current commit `f53da707` was chosen pragmatically because it's the earliest commit where `sources/config.yaml` exists in the upstream repo. The historically accurate onboarding commit is `ade314aa` (2017-02-16), which is just one day before fonts were added to google/fonts via PR #665.
+
+**Important note**: The fonts currently in google/fonts are static TTFs from 2017 (v1.050). The upstream repo has undergone significant development since then (v2-dev branch merged in 2024, plus contributions from Yanone in 2025). The current upstream sources would produce different fonts than what is in google/fonts.
+
+## How Config YAML Was Resolved
+
+**Upstream config** at commit `f53da707`: `sources/config.yaml` exists and references:
+```yaml
+sources:
+ - AbhayaLibre.glyphs
+outputDir: "../fonts"
+buildStatic: false
+buildVariable: true
+```
+This config builds a **variable** font (not static), which does not match what's in google/fonts (static TTFs).
+
+**Local override** in `ofl/abhayalibre/config.yaml` (added in commit `04009b5bb`):
+```yaml
+sources:
+ - sources/glyphs/Abhaya-Masters.glyphs
+buildStatic: true
+buildVariable: false
+```
+This override builds **static** fonts, matching what's in google/fonts. However, the source path `sources/glyphs/Abhaya-Masters.glyphs` references the file at its old location and old name. This file:
+- Existed as `sources/glyphs/Abhaya-Masters.glyphs` up to commit `71089b83` (2017-10-22), when it was renamed to `sources/glyphs/AbhayaLibre.glyphs`
+- Was later moved to `sources/AbhayaLibre.glyphs` in commit `e6973a96` (2021-05-26)
+- At the currently referenced commit `f53da707`, the file is at `sources/AbhayaLibre.glyphs`
+
+**Discrepancy**: The local override config references `sources/glyphs/Abhaya-Masters.glyphs`, but at the referenced commit `f53da707`, this path does not exist. The file is at `sources/AbhayaLibre.glyphs`. The override config would only work if pointed at a commit before `71089b83` (pre-October 2017).
+
+The METADATA.pb currently sets `config_yaml: "sources/config.yaml"` pointing to the upstream config. Since a local override also exists, this creates potential confusion. Per project policy, when an override `config.yaml` exists in google/fonts, the `config_yaml` field can be omitted from METADATA.pb.
+
+## Conclusion
+
+The source block is technically complete but has internal inconsistencies:
+
+1. **Repository URL**: Correct and verified.
+2. **Commit hash**: `f53da707` was chosen because it's the earliest commit with `sources/config.yaml`, but it's from 2024 -- seven years after the fonts were built. The historically accurate commit is `ade314aa` (2017-02-16).
+3. **Config situation is confused**: Both an upstream `config_yaml` reference AND a local override exist. The upstream config at `f53da707` builds a variable font (not matching google/fonts). The local override references a source path (`sources/glyphs/Abhaya-Masters.glyphs`) that doesn't exist at the referenced commit.
+
+**Recommended corrections**:
+- Change commit to `ade314aa678ceb44f892ed58169c6b270c775d02` (the actual onboarding-era commit)
+- Remove `config_yaml` from METADATA.pb source block (since local override exists)
+- Fix the local override config to reference `sources/glyphs/Abhaya-Masters.glyphs` (which exists at `ade314aa`) -- this path is actually correct for the onboarding-era commit
+- These changes would make the data internally consistent: the commit hash matches the era when fonts were built, and the local override config references a source path that exists at that commit
--- /dev/null
+# Aboreto
+
+**Date investigated**: 2026-02-26
+**Status**: complete
+**Designer**: Dominik Jager
+**METADATA.pb path**: `ofl/aboreto/METADATA.pb`
+
+## Source Data
+
+| Field | Value |
+|-------|-------|
+| Repository URL | https://github.com/domija/Aboreto |
+| Commit | `6e64ee7e7ff1c53220d96b88a8d4bf2db9f76735` |
+| Config YAML | override in google/fonts |
+| Branch | `main` |
+
+## How the Repository URL Was Found
+
+The repository URL was already present in the METADATA.pb `source { repository_url }` field: `https://github.com/domija/Aboreto`. This URL is also referenced in the font copyright string: "Copyright 2022 The Aboreto Project Authors (https://github.com/domija/Aboreto)". The URL was merged into METADATA.pb via commit `66f91f10f` ("Merge upstream.yaml into METADATA.pb").
+
+## How the Commit Hash Was Identified
+
+The commit hash `6e64ee7e7ff1c53220d96b88a8d4bf2db9f76735` was pre-existing in the METADATA.pb `source { commit }` field. This commit is part of a chain related to PR #4832 in google/fonts.
+
+**Detailed commit chain analysis**:
+- The last font-modifying commit in google/fonts is `4aa5ca44f692` from 2022-07-01, with message "[gftools-packager] Aboreto: Version 1.001; ttfautohint (v1.8.4.7-5d5b) added (#4832)".
+- The merge commit body of `4aa5ca44` states: "taken from the upstream repo https://github.com/domija/Aboreto at commit https://github.com/domija/Aboreto/commit/07795db7fb5cf9029f1bac1ae0b130bbae6c5feb".
+- However, the PR #4832 body text references a different (earlier) commit: `1423a732a34d080e360e8771ae9aca3de47ced31`.
+- In the upstream repo, the commit history shows: `1423a73` ("Merge pull request #3") -> `6e64ee7` ("V-metrics updated") -> `07795db` ("Merge pull request #4"). So `6e64ee7` is the actual content commit that was part of upstream PR #4, and `07795db` is its merge commit.
+- The METADATA.pb references `6e64ee7`, which is the content commit within the merge. This is a reasonable and correct reference.
+
+## How Config YAML Was Resolved
+
+No `config.yaml` exists in the upstream repo at commit `6e64ee7`. An override `config.yaml` exists in the google/fonts family directory at `ofl/aboreto/config.yaml`. Its contents:
+
+```yaml
+buildVariable: false
+sources:
+ - sources/Aboreto.glyphs
+```
+
+The upstream repo at this commit has a `.glyphs` source file at `sources/Aboreto.glyphs`. The override config correctly points to this file and specifies a static-only build.
+
+## Verification
+
+- Commit exists in upstream repo: Yes
+- Commit date: 2022-06-24 15:30:44 +0200
+- Commit message: "V-metrics updated"
+- Source files at commit: `sources/Aboreto.glyphs`, `old/sources/Aboreto-Regular.ufo` (legacy)
+
+## Confidence
+
+**High**: The repository URL is confirmed by both METADATA.pb and the font copyright string. The commit hash is pre-existing in METADATA.pb and is corroborated by the google/fonts PR #4832 merge commit body, which references the merge commit (`07795db`) that includes this content commit (`6e64ee7`). The override config.yaml correctly references the upstream source file.
+
+## Open Questions
+
+None. This family is fully documented with consistent evidence across METADATA.pb, google/fonts commit history, and the upstream repository.
--- /dev/null
+# Abyssinica SIL
+
+**Date investigated**: 2026-03-03
+**Model**: Claude Opus 4.6
+**Status**: complete
+**Designer**: SIL International
+**METADATA.pb path**: `ofl/abyssinicasil/METADATA.pb`
+
+## Source Data
+
+| Field | Value |
+|-------|-------|
+| Repository URL | https://github.com/silnrsi/font-abyssinica |
+| Commit | `1f7e65b0e7367681198c980647b3049559ebefa0` |
+| Config YAML | override config.yaml in google/fonts |
+| Branch | master |
+
+## How the Repository URL Was Found
+
+The repository URL `https://github.com/silnrsi/font-abyssinica` is recorded in the METADATA.pb `source` block. It was explicitly referenced in the google/fonts commit `044faf160` (2024-10-30, authored by Emma Marichal) which states: "Taken from the upstream repo https://github.com/silnrsi/font-abyssinica at commit https://github.com/silnrsi/font-abyssinica/commit/1f7e65b0e7367681198c980647b3049559ebefa0."
+
+The upstream repo is cached at `upstream_repos/fontc_crater_cache/silnrsi/font-abyssinica` and confirmed accessible.
+
+## How the Commit Hash Was Identified
+
+The commit `1f7e65b0e7367681198c980647b3049559ebefa0` is explicitly referenced in:
+1. The METADATA.pb `source` block
+2. The google/fonts commit message for `044faf160`
+
+This commit was verified to exist in the upstream repo. It is dated 2024-10-29 15:33:26 -0500 with the message "Update font in references and in test files. [nobuild]" by Lorna Evans. It is 2 commits after the v2.300 tag (`037d134`, dated 2024-10-29 09:13:25 -0500) — both from the same day. The commit updates the reference binary font file in `references/AbyssinicaSIL-Regular.ttf` to match the v2.300 release build.
+
+The binary font at this commit (`references/AbyssinicaSIL-Regular.ttf`, 268,264 bytes) matches the file in google/fonts exactly (268,264 bytes), confirming this is the correct commit. The font was distributed via the `archive_url` pattern — the pre-built binary from the GitHub release `v2.300` was used directly rather than building from source.
+
+## How Config YAML Was Resolved
+
+The upstream repo does **not** have a `config.yaml` at the referenced commit (or at HEAD). The font was onboarded using the `archive_url` pattern: the pre-built binary from the GitHub release at `https://github.com/silnrsi/font-abyssinica/releases/download/v2.300/AbyssinicaSIL-2.300.zip` was extracted directly into google/fonts. The METADATA.pb `source` block includes `files` mappings that specify how to copy files from the archive.
+
+However, the upstream repo does contain gftools-builder-compatible sources:
+- `source/AbyssinicaSIL.designspace` (designspace format 3)
+- `source/AbyssinicaSIL-Regular.ufo`
+
+A local override `config.yaml` was added to the google/fonts family directory in commit `f6c68379a` (2026-02-16, by Felipe Sanches) as part of a batch adding override configs for 50 families. This override points to `source/AbyssinicaSIL.designspace` and configures static builds without OTF output:
+
+```yaml
+sources:
+ - source/AbyssinicaSIL.designspace
+familyName: Abyssinica SIL
+buildStatic: true
+buildOTF: false
+```
+
+Since the override config.yaml exists locally in google/fonts, the `config_yaml` field is correctly omitted from the METADATA.pb `source` block (google-fonts-sources auto-detects local overrides).
+
+## Conclusion
+
+Abyssinica SIL is fully documented. The repository URL, commit hash, and branch are all present in METADATA.pb and have been verified. The font was onboarded via the archive distribution pattern (pre-built binary from a GitHub release), but the upstream repo also contains designspace/UFO sources suitable for building with gftools-builder. A local override config.yaml has been added to the google/fonts family directory to enable source builds. All data is consistent and the binary sizes match exactly.
--- /dev/null
+# ADLaM Display
+
+**Date investigated**: 2026-03-03
+**Model**: Claude Opus 4.6
+**Status**: complete
+**Designer**: Mark Jamra, Neil Patel, Andrew Footit
+**METADATA.pb path**: `ofl/adlamdisplay/METADATA.pb`
+
+## Source Data
+
+| Field | Value |
+|-------|-------|
+| Repository URL | https://github.com/microsoft/ADLaM-Display |
+| Commit | `879176243e9f7161a8aefdab8c36a4a7318ebe15` |
+| Config YAML | `Sources/config.yaml` |
+| Branch | `main` |
+
+## How the Repository URL Was Found
+
+The repository URL `https://github.com/microsoft/ADLaM-Display` was already present in METADATA.pb. It was originally added by the gftools-packager onboarding commit `40699510e` (2023-07-10), which explicitly states in its commit body: "taken from the upstream repo https://github.com/microsoft/ADLaM-Display". The remote URL of the cached repo at `fontc_crater_cache/microsoft/ADLaM-Display` confirms this matches `https://github.com/microsoft/ADLaM-Display`.
+
+Note: The user's initial prompt mentioned `nicholasko/ADLaM-Display` as a possible alternative, but the METADATA.pb contains `microsoft/ADLaM-Display` and no `nicholasko` variant exists in the cache.
+
+## How the Commit Hash Was Identified
+
+The commit `879176243e9f7161a8aefdab8c36a4a7318ebe15` was verified through multiple sources:
+
+1. **gftools-packager commit body** (commit `40699510e` in google/fonts, dated 2023-07-10): Explicitly references this commit hash with a direct link.
+2. **Upstream repo verification**: The commit exists in the cached repo. It is the **only commit** in the entire repository, authored by "Aaron" on 2023-07-10, with message "Build". It is the initial commit creating the full repo contents (18 files, 76,624 insertions).
+3. **Merge PR**: google/fonts PR #6522 merged on 2023-07-21, confirming the onboarding was completed shortly after the upstream commit date.
+
+Since there is only one commit in the repo, there is no ambiguity about which commit was used for onboarding.
+
+## How Config YAML Was Resolved
+
+The file `Sources/config.yaml` exists at the referenced commit and contains:
+
+```yaml
+sources:
+ - ADLaM-Display.glyphs
+familyName: "ADLaM Display"
+buildOTF: false
+```
+
+This path was added to METADATA.pb in two steps:
+1. Commit `19cdcec59` (2025-03-31, Batch 1/4) added `config_yaml: "sources/config.yaml"` (lowercase "s") ported from fontc_crater targets.
+2. Commit `7190093b1` (2025-05-22) corrected the case to `config_yaml: "Sources/config.yaml"` (uppercase "S"), matching the actual directory name in the upstream repo.
+
+The upstream repo has `.glyphs` source files in the `Sources/` directory, confirming gftools-builder compatibility.
+
+## Conclusion
+
+ADLaM Display has a fully complete source block in METADATA.pb. The repository URL, commit hash, branch, config_yaml path, and file mappings are all present and verified. The repository is hosted under the Microsoft organization on GitHub and contains a single commit that was used for the original onboarding via gftools-packager (google/fonts PR #6522, merged 2023-07-21). No further action is needed.
--- /dev/null
+# Advent Pro
+
+**Date investigated**: 2026-03-03
+**Model**: Claude Opus 4.6
+**Status**: complete
+**Designer**: VivaRado
+**METADATA.pb path**: `ofl/adventpro/METADATA.pb`
+
+## Source Data
+| Field | Value |
+|-------|-------|
+| Repository URL | https://github.com/googlefonts/Advent |
+| Commit | `d206a139ee9045993fbd1e530b93f28f8bf4e3b1` |
+| Config YAML | `sources/config.yaml` |
+| Branch | `master` |
+
+## How the Repository URL Was Found
+
+The repository URL `https://github.com/googlefonts/Advent` was already present in the METADATA.pb source block. It was originally set via gftools-packager when PR #5522 onboarded Version 3.000 (commit `ce1042736` in google/fonts, authored by Yanone on 2022-12-01). The `config_yaml` field was later added in the "Batch 1/4" commit (`19cdcec59`, 2025-03-31), porting data from fontc_crater's targets.json.
+
+The cached upstream repo at `googlefonts/Advent` confirms the remote URL matches.
+
+## How the Commit Hash Was Identified
+
+The commit `d206a139ee9045993fbd1e530b93f28f8bf4e3b1` is explicitly referenced in the google/fonts PR #5522 commit message:
+
+> Advent Pro Version 3.000 taken from the upstream repo https://github.com/googlefonts/Advent at commit https://github.com/googlefonts/Advent/commit/d206a139ee9045993fbd1e530b93f28f8bf4e3b1.
+
+This commit is the only commit in the upstream repo (the entire repository history is a single commit titled "Latest binaries", authored by Yanone on 2022-11-25). Therefore there is no ambiguity about which commit was used.
+
+**Binary file verification**: The SHA256 hashes of both variable font files match exactly between the upstream repo at this commit and the google/fonts directory:
+- `AdventPro[wdth,wght].ttf`: `b60ab2920b89bdc4b7dadfb282cadac6e03833e7a80844f9eac096359b2b9766`
+- `AdventPro-Italic[wdth,wght].ttf`: `0917a5d65589025f2a752b1b0568f924dac49a065a25b4d60116b3c6d4d9ebae`
+
+This confirms the fonts in google/fonts were taken directly from the upstream repo's pre-built binaries at `fonts/variable/split/`, not built from source.
+
+## How Config YAML Was Resolved
+
+The upstream repo contains `sources/config.yaml` at the referenced commit, confirmed via `git ls-tree`. The config uses a `.designspace` source file (`sources/AdventPro.designspace`) which references UFO masters in `sources/advent_pro/`. The config is set to build variable TTF only (no OTF, no static, no webfont).
+
+The METADATA.pb correctly references this as `config_yaml: "sources/config.yaml"`. Note that the fonts currently in google/fonts were NOT built using this config -- they are pre-built binaries copied from the upstream repo's `fonts/variable/split/` directory. The config would be relevant for any future rebuild from source using fontc/gftools-builder.
+
+No override `config.yaml` exists in the google/fonts family directory.
+
+## Key Timeline
+
+| Date | Event |
+|------|-------|
+| 2022-11-25 | Upstream commit `d206a13` ("Latest binaries") by Yanone |
+| 2022-12-01 | google/fonts PR #5522 merged (Version 3.000 onboarded) |
+| 2024-04-03 | upstream.yaml merged into METADATA.pb source block |
+| 2025-03-31 | Batch 1/4 added `config_yaml` field to METADATA.pb |
+
+## Conclusion
+
+The source block for Advent Pro is **complete** and well-documented. The repository URL, commit hash, branch, and config_yaml are all correctly set in METADATA.pb. The commit hash is verified both by the explicit reference in PR #5522 and by identical SHA256 hashes of the binary font files. The upstream repo has only one commit, making verification trivial.
+
+**Confidence**: HIGH
--- /dev/null
+# Afacad
+
+**Date investigated**: 2026-02-26
+**Status**: complete
+**Designer**: Kristian Moller, Dicotype
+**METADATA.pb path**: `ofl/afacad/METADATA.pb`
+
+## Source Data
+
+| Field | Value |
+|-------|-------|
+| Repository URL | https://github.com/Dicotype/Afacad |
+| Commit | `b294b1f8610ff16a3846a255b1a6a2e6788a056e` |
+| Config YAML | `sources/config.yaml` |
+| Branch | `main` |
+
+## How the Repository URL Was Found
+
+The repository URL was already present in METADATA.pb in the `source { repository_url }` field: `https://github.com/Dicotype/Afacad`. This is consistent with the copyright notice in the font files: "Copyright 2023 The Afacad Project Authors (https://github.com/Dicotype/Afacad)".
+
+The `Dicotype` GitHub organization is the official home of typefaces designed by Kristian Moller / Dicotype.
+
+## How the Commit Hash Was Identified
+
+The commit hash situation is complex, involving **three different referenced commits**:
+
+1. **METADATA.pb current commit**: `b294b1f8610ff16a3846a255b1a6a2e6788a056e` -- This was added in commit `19cdcec59` (2025-03-31) as part of "[Batch 1/4] port info from fontc_crater targets list" by Felipe Sanches. This commit is from the fontc_crater targets.json data.
+
+2. **gftools-packager merge commit message** (`aa30c14f9`, 2023-10-20): References commit `d7e973f5d3f17f54662ed9a18b130dcbf7a0e709` with the message "Afacad Version 1.000 taken from the upstream repo https://github.com/Dicotype/Afacad at commit https://github.com/Dicotype/Afacad/commit/d7e973f5d3f17f54662ed9a18b130dcbf7a0e709."
+
+3. **PR #6881 initial body**: References yet another commit `39d4a8f1e6c5a64d4c31a639c251800ee4b65fa7`.
+
+**Critical finding**: The Dicotype/Afacad repository has been **force-pushed** and now contains only a **single commit** (`b294b1f8`, 2024-10-03: "Update README.md"). Both the original packager commit (`d7e973f5`) and the initial PR commit (`39d4a8f1`) no longer exist in the repository. The repository history has been completely rewritten.
+
+The commit `b294b1f8` currently in METADATA.pb is the only commit that exists in the repo, but it dates to **2024-10-03** -- nearly a year after the font was added to google/fonts (2023-10-20). This commit cannot be the one used for the original onboarding.
+
+## How Config YAML Was Resolved
+
+The `sources/config.yaml` file exists in the upstream repository at the current commit (`b294b1f8`). Its contents include:
+
+```yaml
+sources:
+ - Afacad.glyphs
+ - Afacad-Italic.glyphs
+axisOrder:
+ - wght
+ - ital
+familyName: Afacad
+outputDir: "../fonts/Afacad"
+```
+
+The repo also contains `sources/config_flux.yaml` for the related Afacad Flux family, and `sources/AfacadFlux.glyphs`.
+
+Note: Since the repo was force-pushed, we cannot verify that this config.yaml existed at the time of the original onboarding. However, the fontc_crater targets list references this path, and the config is valid for gftools-builder.
+
+## Verification
+
+- Commit exists in upstream repo: Yes (but it is the ONLY commit -- repo was force-pushed)
+- Commit date: 2024-10-03 10:40:24 +0200
+- Commit message: "Update README.md"
+- Source files at commit: `sources/Afacad.glyphs`, `sources/Afacad-Italic.glyphs`, `sources/config.yaml`, `sources/AfacadFlux.glyphs`, `sources/config_flux.yaml`, plus instance UFO JSON files
+
+## Confidence
+
+**Medium**: The repository URL is confirmed correct (matches copyright notice and PR references). The config.yaml path is valid and the file exists. However, the commit hash situation is problematic:
+
+- The original onboarding commit (`d7e973f5`) no longer exists in the repo due to force-pushing
+- The current METADATA.pb commit (`b294b1f8`) post-dates the font's addition to google/fonts by nearly a year
+- The repo has been completely rewritten to a single commit, destroying the original history
+
+The practical impact is limited since the config.yaml and source files are present at the current (and only) commit, but the commit hash does not represent the original onboarding state.
+
+## Open Questions
+
+1. The original onboarding commit `d7e973f5d3f17f54662ed9a18b130dcbf7a0e709` was lost due to a force-push of the Dicotype/Afacad repository. Should the commit field be updated to the current HEAD, or should this be flagged as needing investigation with the designer?
+2. Has the source content changed materially between the original onboarding and the current single commit? Without the original history, this cannot be verified from git alone.
+3. Should the METADATA.pb `source { commit }` field note that this is a post-force-push reference rather than the original onboarding commit?
--- /dev/null
+# Afacad Flux
+
+**Date investigated**: 2026-03-03
+**Model**: Claude Opus 4.6
+**Status**: needs_correction
+**Designer**: Kristian Möller, Dicotype
+**METADATA.pb path**: `ofl/afacadflux/METADATA.pb`
+
+## Source Data
+| Field | Value |
+|-------|-------|
+| Repository URL | https://github.com/Dicotype/Afacad |
+| Commit | `b294b1f8610ff16a3846a255b1a6a2e6788a056e` (current in METADATA.pb; likely incorrect — see below) |
+| Config YAML | `sources/config_flux.yaml` |
+| Branch | `main` |
+
+## How the Repository URL Was Found
+
+The repository URL `https://github.com/Dicotype/Afacad` was present in METADATA.pb from the initial onboarding. It is also referenced in the font copyright string: "Copyright 2023 The Afacad Project Authors (https://github.com/Dicotype/Afacad)". The upstream repo is cached at `Dicotype/Afacad` and is valid.
+
+## How the Commit Hash Was Identified
+
+Three different commit hashes appear in the history of this family, which is a concern:
+
+1. **`a3d77cea32b6f29801c5c1771fbad276d817c97a`** — referenced in the PR #7851 body by Emma Marichal: "Taken from the upstream repo ... at commit a3d77ce..."
+2. **`4655a472cef57467e1604ce80336ab87ea72facc`** — referenced in the google/fonts commit message (`ef30d6c39`) and in the original METADATA.pb at the time of onboarding
+3. **`b294b1f8610ff16a3846a255b1a6a2e6788a056e`** — the current HEAD of the upstream repo's `main` branch, introduced into METADATA.pb by commit `19cdcec59` ("Batch 1/4 port info from fontc_crater targets list")
+
+**Timeline analysis**:
+- The google/fonts merge of PR #7851 occurred on **2024-07-05**
+- Commit `b294b1f` in the upstream repo is dated **2024-10-03** (a README update), which is ~3 months AFTER the onboarding merge
+
+**Conclusion on commit hash**: The current METADATA.pb commit hash `b294b1f` is **incorrect** — it points to a commit made after the font was already onboarded. This was introduced by the "Batch 1/4" update which imported fontc_crater target data (which uses the latest HEAD, not the original onboarding commit).
+
+The original onboarding commit was `4655a47` (from the commit message / original METADATA.pb). The PR body referenced `a3d77ce`, which is a discrepancy typical of gftools-packager (the tool may have started with one commit and the final packaged result referenced another). Both `4655a47` and `a3d77ce` are inaccessible in the shallow clone but exist as objects in the pack file.
+
+The binary font in google/fonts (sha256: `28aa3569...`) does NOT match the binary at `b294b1f` (sha256: `89b1d45d...`), confirming the current commit hash is wrong.
+
+**Recommendation**: The commit hash should be reverted to `4655a472cef57467e1604ce80336ab87ea72facc` (the original onboarding value). Further investigation with a full (non-shallow) clone could determine whether `a3d77ce` or `4655a47` was the actual source commit, but `4655a47` was what the gftools-packager tool recorded in METADATA.pb.
+
+## How Config YAML Was Resolved
+
+The upstream repo contains two config files in the `sources/` directory:
+- `sources/config.yaml` — for the Afacad (non-Flux) family, references `Afacad.glyphs` and `Afacad-Italic.glyphs`
+- `sources/config_flux.yaml` — for Afacad Flux, references `AfacadFlux.glyphs`
+
+The "Batch 1/4" update initially set `config_yaml` to `sources/config.yaml` (wrong — that's for the non-Flux family). This was corrected to `sources/config_flux.yaml` in commit `187711d44` ("sources info for Afacad Flux: Version 1.100", PR #7851 by Felipe Sanches).
+
+The current value `sources/config_flux.yaml` is correct. The config builds from `AfacadFlux.glyphs` with axes `slnt` and `wght`, outputting to `fonts/Afacad_Flux/`, with TTF/OTF building disabled (pre-built binaries are used).
+
+No override `config.yaml` exists in the google/fonts family directory.
+
+## Conclusion
+
+**Confidence: HIGH** for repository URL and config_yaml.
+**Confidence: MEDIUM** for the commit hash correction.
+
+The repository URL and config_yaml path are correct as currently set. However, the commit hash `b294b1f` is demonstrably wrong — it postdates the onboarding by 3 months and the binary files don't match. The commit should be corrected back to `4655a472cef57467e1604ce80336ab87ea72facc` (the original gftools-packager value). A full clone would be needed to definitively determine which of `4655a47` or `a3d77ce` was the true source commit, but `4655a47` was the value recorded by the packaging tool in the original METADATA.pb.
--- /dev/null
+# Agbalumo
+
+**Date investigated**: 2026-02-26
+**Status**: complete
+**Designer**: Raphael Alegbeleleye, Sorkin Type, Eben Sorkin
+**METADATA.pb path**: `ofl/agbalumo/METADATA.pb`
+
+## Source Data
+
+| Field | Value |
+|-------|-------|
+| Repository URL | https://github.com/SorkinType/Agbalumo |
+| Commit | `261ad51ef2291821685c1bebf10cf0fb9f7e08f9` |
+| Config YAML | `sources/config.yaml` |
+| Branch | `main` |
+
+## How the Repository URL Was Found
+
+The repository URL was already present in the METADATA.pb source block. It was established during the initial onboarding (PR #6830, google/fonts commit `6a9a2d7b9`, 2023-10-06) which stated the font was "taken from the upstream repo https://github.com/SorkinType/Agbalumo.git". The copyright field also references this GitHub URL.
+
+## How the Commit Hash Was Identified
+
+The commit hash has gone through three distinct values as the font was updated:
+
+1. **Initial onboarding** (PR #6830, google/fonts commit `6a9a2d7b9`, 2023-10-06): Version 1.000 was taken from upstream commit `c6c381d3704ef794dde69b80489d0cde36fb6f9b`. The PR body initially referenced an even earlier commit `3e64aac2795e538846e6412d444d307f345108ec`.
+
+2. **Batch port from fontc_crater** (google/fonts commit `19cdcec59`, 2025-03-31): The commit was updated from `c6c381d3` to `9d9ec3e32c10533233c9e48835e436ff5e5aa451`, based on fontc_crater's target.json.
+
+3. **Version 2.000 update** (PR #9344, google/fonts commit `dc6afb493`, 2025-06-05): Emma Marichal updated the font to Version 2.000 with ttfautohint, changing the commit to `261ad51ef2291821685c1bebf10cf0fb9f7e08f9`. The commit body explicitly states: "Taken from the upstream repo https://github.com/SorkinType/Agbalumo at commit 261ad51ef2291821685c1bebf10cf0fb9f7e08f9." This added Ethiopic script support (new subset).
+
+The current METADATA.pb commit `261ad51e` is a proper onboarding commit that corresponds to the font binary update, making it the correct reference.
+
+## How Config YAML Was Resolved
+
+The `sources/config.yaml` path was added by the batch port commit `19cdcec59` (2025-03-31) and confirmed during the Version 2.000 update. The config file exists at the recorded commit and specifies:
+- Source: `Agbalumo.glyphspackage`
+- Family name: Agbalumo
+- `buildOTF: false`
+
+No override config.yaml exists in the google/fonts family directory.
+
+## Verification
+
+- Commit exists in upstream repo: Yes (it is HEAD of the shallow clone)
+- Commit date: 2025-06-04 11:24:44 -0400
+- Commit message: "Merge pull request #27 from emmamarichal/main"
+- Source files at commit:
+ - `sources/Agbalumo.glyphspackage/` (with fontinfo.plist, many glyph files)
+ - `sources/config.yaml`
+ - `.github/workflows/build.yaml`
+
+## Confidence
+
+**High**: The repository URL is well-established and confirmed across multiple onboarding events. The current commit hash `261ad51e` is the correct onboarding commit for Version 2.000, directly referenced in the google/fonts commit body by Emma Marichal (2025-06-05). The config.yaml file is verified to exist at this commit in the upstream repo. This is a properly documented, recent update with clear provenance.
+
+## Open Questions
+
+None. This family is well-documented with a clear chain of evidence from the latest font update.
--- /dev/null
+# Agdasima
+
+**Date investigated**: 2026-02-26
+**Status**: complete
+**Designer**: The DocRepair Project, Patric King
+**METADATA.pb path**: `ofl/agdasima/METADATA.pb`
+
+## Source Data
+
+| Field | Value |
+|-------|-------|
+| Repository URL | https://github.com/docrepair-fonts/agdasima-fonts |
+| Commit | `c971400d774dfd6d28e7a8e34aedc3b3dfdce6f9` |
+| Config YAML | `sources/config.yaml` |
+| Branch | `main` |
+
+## How the Repository URL Was Found
+
+The repository URL was already present in the METADATA.pb source block, established during the gftools-packager onboarding. The copyright field in the font binary references the same URL: "The Agdasima Project Authors (https://github.com/docrepair-fonts/agdasima-fonts)." Multiple google/fonts commits confirm this URL, including PR #6249 and the final font update commit `92ba10a48`.
+
+## How the Commit Hash Was Identified
+
+The commit hash `c971400d` was set during the font onboarding and has remained unchanged:
+
+1. **Font update** (google/fonts commit `92ba10a48`, 2023-06-14): The gftools-packager commit body states: "Agdasima Version 2.002 taken from the upstream repo https://github.com/docrepair-fonts/agdasima-fonts at commit c971400d774dfd6d28e7a8e34aedc3b3dfdce6f9."
+
+2. **PR #6249**: The PR body initially referenced a different commit `ccbf4bfc6fc6c99bd6086d5fc7eff951f88b1bdf`, but the final squashed commit used `c971400d`. This is consistent with the PR branch being updated after the initial push.
+
+3. **Batch port** (google/fonts commit `19cdcec59`, 2025-03-31): Only added `config_yaml: "sources/config.yaml"` -- did NOT change the commit hash, confirming the fontc_crater target also had the same commit.
+
+The commit hash is well-corroborated: the google/fonts commit body, the METADATA.pb, and the fontc_crater data all agree on `c971400d`.
+
+## How Config YAML Was Resolved
+
+The `sources/config.yaml` path was added by the batch port commit `19cdcec59` (2025-03-31). The config file exists at the recorded commit in the upstream repo and specifies:
+- Source: `Agdasima-Regular.designspace`
+- Family name: Agdasima
+- `buildOTF: false`, `buildVariable: false`, `buildWebfont: false`
+- Output directory: `../fonts`
+
+No override config.yaml exists in the google/fonts family directory.
+
+## Verification
+
+- Commit exists in upstream repo: Yes (it is HEAD of the shallow clone, matching the onboarding commit)
+- Commit date: 2023-06-14 17:07:16 +0200
+- Commit message: "New fonts"
+- Source files at commit:
+ - `sources/Agdasima-Regular.designspace`
+ - `sources/config.yaml`
+ - `sources/masters/Agdasima-Bold.ufo/` (with many .glif files)
+ - `sources/masters/Agdasima-Regular.ufo/` (implied by designspace)
+ - `.github/workflows/build.yaml`
+ - `packager.yaml`
+
+## Confidence
+
+**High**: All three data points are strongly corroborated. The commit hash `c971400d` is confirmed by the gftools-packager commit message in google/fonts, the METADATA.pb, and the fontc_crater data. The commit date (2023-06-14 17:07:16) is within seconds of the google/fonts onboarding commit (2023-06-14 17:07:44), providing strong temporal correlation that this is the correct onboarding commit. The config.yaml and source files are verified to exist at this commit.
+
+## Open Questions
+
+None. This is a straightforward, well-documented onboarding with consistent references across all sources.
--- /dev/null
+# Agu Display
+
+**Date investigated**: 2026-03-03
+**Model**: Claude Opus 4.6
+**Status**: complete
+**Designer**: Seun Badejo
+**METADATA.pb path**: `ofl/agudisplay/METADATA.pb`
+
+## Source Data
+| Field | Value |
+|-------|-------|
+| Repository URL | https://github.com/theseunbadejo/Agu-Display |
+| Commit | `d520ebead8de4091a82040fe3d8f94d84c38c66f` |
+| Config YAML | `sources/config.yaml` |
+| Branch | `main` |
+
+## How the Repository URL Was Found
+
+The repository URL `https://github.com/theseunbadejo/Agu-Display` was already present in the METADATA.pb source block from the original onboarding commit `6913b39` (2024-11-25), authored by Nathan Willis. The commit message explicitly states: "Taken from the upstream repo https://github.com/theseunbadejo/Agu-Display". The copyright string in METADATA.pb also references this same URL. The cached repo remote confirms the URL is correct.
+
+## How the Commit Hash Was Identified
+
+**Important discrepancy noted**: The original onboarding commit (`6913b39`, dated 2024-11-25) referenced commit `17a7ce91583f40d9e8f21eab6c57870a59c1b668` in both the commit message and the original METADATA.pb. However, this commit hash no longer exists in the upstream repo.
+
+The upstream repo currently contains only a single commit: `d520ebead8de4091a82040fe3d8f94d84c38c66f` (dated 2025-02-10), which is a merge of PR #35 ("Update build.yaml to restore actions"). This commit appears to be the result of a force-push that squashed all prior history into a single commit. Evidence:
+- The `--stat` of this commit shows 55 files added (entire repo contents), indicating it is an initial/squashed commit
+- No other commits exist in the repo (`git log --all` shows only this one commit)
+- The commit date (2025-02-10) is AFTER the google/fonts onboarding date (2024-11-25)
+
+The current commit hash `d520ebe` was set by the "[Batch 1/4] port info from fontc_crater targets list" commit (`19cdcec`, 2025-03-31), which imported data from fontc_crater's `target.json`. Since the original commit `17a7ce9` no longer exists in the repo, `d520ebe` (the only existing commit, containing the full repo contents) is the best available reference. The source files and config at this commit match what would have been used for the original build.
+
+## How Config YAML Was Resolved
+
+The file `sources/config.yaml` exists at commit `d520ebe` in the upstream repo and contains valid gftools-builder configuration:
+
+```yaml
+sources:
+ - AguDisplay.glyphs
+axisOrder:
+ - morf
+familyName: Agu Display
+autohintOTF: False
+stat:
+ - name: Morph
+ tag: MORF
+ values:
+ - name: Uzo
+ value: 0
+ - name: Ala
+ value: 30
+ - name: Osisi
+ value: 60
+```
+
+The source file `sources/AguDisplay.glyphs` (3.1 MB) is present at this commit. The `config_yaml` field was added to METADATA.pb by the Batch 1/4 commit. No override config.yaml exists in the google/fonts family directory.
+
+## Additional Notes
+
+- **Archive URL**: The `archive_url` points to a GitHub release: `https://github.com/theseunbadejo/Agu-Display/releases/download/1.05/Agu-Display-1.05.zip`. The `files` entries in the source block reference paths within this archive (e.g., `fonts/variable/AguDisplay[MORF].ttf`), not paths in the git repo (no `fonts/variable/` directory exists in the repo itself).
+- **Variable axis**: The font has a custom `MORF` (Morph) axis with range 0-60.
+- **Minisite**: The font has a dedicated minisite at https://www.agudisplay.com.
+- **Date added**: 2024-11-14.
+- **Onboarding engineer**: Nathan Willis (commit `6913b39`).
+- **Repository history anomaly**: The upstream repo was apparently force-pushed/rebased after onboarding, losing the original commit `17a7ce9`. The current single commit (`d520ebe`) contains the complete repo contents including all source files, so it is functionally equivalent for build purposes.
+
+## Conclusion
+
+The source block is **complete** with all required fields: repository URL, commit hash, branch, config_yaml path, archive_url, and file mappings. While the original onboarding commit `17a7ce9` no longer exists in the repo due to a force-push, the current commit `d520ebe` contains the same source files and config needed for building. The config.yaml in the upstream repo is valid and correctly referenced. **Confidence: HIGH** for repository URL and config; **MEDIUM** for commit hash (original hash lost due to force-push, current hash is the only available reference but post-dates the onboarding).
--- /dev/null
+# Akatab
+
+**Status**: `complete`
+**Date**: 2026-02-25
+**Designer**: SIL International
+**License**: OFL
+**METADATA.pb**: `ofl/akatab/METADATA.pb`
+
+## Data
+
+| Field | Value |
+|-------|-------|
+| Repository URL | https://github.com/silnrsi/font-akatab |
+| Commit | `54e989b80bf4c99a2b16dc40710083b2b80ebaef` |
+| Config YAML | Override in google/fonts family directory |
+| Branch | `master` |
+
+## Methodology
+
+### Repository URL
+Pre-existing in METADATA.pb `source { repository_url }` field.
+
+### Commit Hash
+Pre-existing in METADATA.pb `source { commit }` field.
+- Commit date: 2025-02-25 11:41:50 -0700
+- Commit message: "Fixed makedocs, committing the resulting PDFs [nobuild]"
+
+### Config YAML
+Override `config.yaml` exists in the google/fonts family directory. Per policy, `config_yaml` field is omitted from METADATA.pb.
+
+## Evidence
+
+### METADATA.pb source block
+- `repository_url`: `https://github.com/silnrsi/font-akatab`
+- `commit`: `54e989b80bf4c99a2b16dc40710083b2b80ebaef`
+- `config_yaml`: `—`
+
+### google/fonts history
+- Last font modification: `5ae22a94169c`
+- Date: 2025-04-02 16:11:35 +0200
+- Subject: "Akatab: Version 4.000 added"
+
+### Upstream repo cache
+- Cached at: `silnrsi/font-akatab`
+- Commit `54e989b80bf4` verified ✓
+
+### Override config
+Override `config.yaml` exists in `ofl/akatab/config.yaml`.
+
+## Confidence
+
+**High**: URL pre-existing in METADATA.pb; commit pre-existing in METADATA.pb
--- /dev/null
+# Akaya Kanadaka
+
+**Date investigated**: 2026-03-03
+**Model**: Claude Opus 4.6
+**Status**: complete
+**Designer**: Vaishnavi Murthy, Juan Luis Blanco
+**METADATA.pb path**: `ofl/akayakanadaka/METADATA.pb`
+
+## Source Data
+| Field | Value |
+|-------|-------|
+| Repository URL | https://github.com/vaishnavimurthy/Akaya-Kanadaka |
+| Commit | `24f25461789ee8642e184b43dd6d5d04ea7f49d1` |
+| Config YAML | override config.yaml in google/fonts |
+| Branch | master |
+
+## How the Repository URL Was Found
+
+The repository URL `https://github.com/vaishnavimurthy/Akaya-Kanadaka` was already present in the METADATA.pb `source` block. It is also referenced in the font's copyright string and in the onboarding PR (#2970) commit message, which explicitly states:
+
+> "taken from the upstream repo https://github.com/vaishnavimurthy/Akaya-Kanadaka.git"
+
+The cached clone at `fontc_crater_cache/vaishnavimurthy/Akaya-Kanadaka` has its remote set to the same URL, confirming consistency.
+
+## How the Commit Hash Was Identified
+
+The METADATA.pb records commit `24f2546`. The onboarding PR #2970 (merged 2021-01-27) references a different commit: `72bdbc541ee3311e0eadafc80d7f097d1d8080a9`. Investigation reveals these are closely related:
+
+- **`24f2546`** (2021-01-21): "Enabled fsSelection bit 7 (Use Typo Metrics)" - authored by Yanone, modifying `Source/AkayaKanadaka.glyphs` and `TTF/AkayaKanadaka-Regular.ttf`
+- **`72bdbc5`** (2021-01-21): Merge commit of PR #14 from yanone/master, which merges `24f2546` into the main line
+
+The merge commit `72bdbc5` is the merge of the branch containing `24f2546`. Both commits contain the exact same TTF binary (MD5: `4dab5a2b9cad2a474cf065e04f74fb44`), and this matches the TTF in google/fonts.
+
+Using `24f2546` (the actual content commit) instead of `72bdbc5` (the merge commit) is a reasonable choice -- both point to the same file state. The gftools-packager referenced the merge commit, but the METADATA.pb was later enriched (commit `68d9071a3`, 2025-10-24) with the content commit hash `24f2546`.
+
+**Timeline**:
+1. PR #2956 (first attempt, 2021-01-15) referenced upstream commit `7f161bd` (merge of PR #13)
+2. PR #2970 (final onboarding, 2021-01-27) referenced upstream commit `72bdbc5` (merge of PR #14, which includes `24f2546`)
+3. After onboarding, only one upstream commit followed: `fef8598` (2021-04-29, "Update README.md") -- a non-font change
+
+The commit hash `24f2546` correctly identifies the state of the source files used for onboarding. Confidence is HIGH.
+
+## How Config YAML Was Resolved
+
+The upstream repository has never contained a `config.yaml` file (verified across all commits and branches). The source file is a Glyphs file at `Source/AkayaKanadaka.glyphs`, which is gftools-builder compatible.
+
+An override `config.yaml` was created in the google/fonts family directory at `ofl/akayakanadaka/config.yaml` (added in commit `68d9071a3`, 2025-10-24) with content:
+
+```yaml
+buildVariable: false
+sources:
+ - Source/AkayaKanadaka.glyphs
+```
+
+This correctly references the Glyphs source file in the upstream repo. Since the override exists locally, the `config_yaml` field is correctly omitted from the METADATA.pb `source` block (google-fonts-sources auto-detects local overrides).
+
+## Conclusion
+
+The source metadata for Akaya Kanadaka is **complete**. The repository URL is confirmed, the commit hash `24f2546` correctly identifies the source state used for onboarding (identical binary at both the content commit and the merge commit referenced by gftools-packager), and the override config.yaml properly points to the Glyphs source. No further action needed.
+
+**Confidence**: HIGH
--- /dev/null
+# Akaya Telivigala
+
+**Date investigated**: 2026-03-03
+**Model**: Claude Opus 4.6
+**Status**: complete
+**Designer**: Vaishnavi Murthy, Juan Luis Blanco
+**METADATA.pb path**: `ofl/akayatelivigala/METADATA.pb`
+
+## Source Data
+| Field | Value |
+|-------|-------|
+| Repository URL | https://github.com/vaishnavimurthy/Akaya-Telivigala |
+| Commit | `93b31e45b69178ecfdb48981a5aa8a8b33bb0340` |
+| Config YAML | override config.yaml in google/fonts |
+| Branch | master |
+
+## How the Repository URL Was Found
+
+The repository URL `https://github.com/vaishnavimurthy/Akaya-Telivigala` is recorded in the METADATA.pb `source {}` block and matches the copyright string in the font metadata. The cached upstream repo at `fontc_crater_cache/vaishnavimurthy/Akaya-Telivigala` has this URL as its git remote origin, confirming it is valid and accessible.
+
+## How the Commit Hash Was Identified
+
+The commit `93b31e45b69178ecfdb48981a5aa8a8b33bb0340` is explicitly referenced in the google/fonts onboarding commit `7b4021c0a` (PR #3355, merged 2021-04-30), which states:
+
+> Akaya Telivigala Version 1.002; ttfautohint (v1.8.3) taken from the upstream repo https://github.com/vaishnavimurthy/Akaya-Telivigala.git at commit https://github.com/vaishnavimurthy/Akaya-Telivigala/commit/93b31e45b69178ecfdb48981a5aa8a8b33bb0340.
+
+This was a gftools-packager automated onboarding. The commit exists in the upstream repo and is the HEAD of the `master` branch. It is a merge commit dated 2021-04-29 ("Merge pull request #5 from yanone/master — Akaya-Telivigala v1.002 ready for Google Fonts"), which aligns with the google/fonts PR #3355 merge date of 2021-04-30. The binary file `TTF/AkayaTelivigala-Regular.ttf` produced by this commit (561,640 bytes) matches the file size in the google/fonts directory (561,640 bytes), further confirming this is the correct onboarding commit.
+
+No subsequent commits exist in the upstream repo, so this is also the latest commit.
+
+## How Config YAML Was Resolved
+
+The upstream repository does not contain a `config.yaml` file. However, the source file `Source/AkayaTelivigala.glyphs` exists at the referenced commit, which is a gftools-builder-compatible source format.
+
+An override `config.yaml` was created in the google/fonts family directory at `ofl/akayatelivigala/config.yaml` (added in commit `fa4a17cbf`, 2025-10-24). Its contents:
+
+```yaml
+buildVariable: false
+sources:
+ - Source/AkayaTelivigala.glyphs
+```
+
+This references the `.glyphs` source file relative to the upstream repo root. Since the override config exists locally in google/fonts, the `config_yaml` field is correctly omitted from the METADATA.pb `source {}` block (google-fonts-sources auto-detects local overrides).
+
+## Conclusion
+
+The source metadata for Akaya Telivigala is **complete**. The repository URL is valid and confirmed by the gftools-packager onboarding message. The commit hash `93b31e4` is verified as the exact commit used during onboarding (PR #3355), with matching binary file sizes as corroborating evidence. The override `config.yaml` correctly points to the `.glyphs` source in the upstream repo. **Confidence: HIGH**.
--- /dev/null
+# Akronim
+
+**Status**: `no_upstream_repo`
+**Date**: 2026-02-25
+**Designer**: Grzegorz Klimczewski
+**License**: OFL
+**METADATA.pb**: `ofl/akronim/METADATA.pb`
+
+## Data
+
+| Field | Value |
+|-------|-------|
+| Repository URL | — |
+| Commit | unknown |
+| Config YAML | — |
+
+## Methodology
+
+### Repository URL
+No upstream repository URL found.
+
+### Commit Hash
+Commit hash unknown — could not be determined.
+
+### Config YAML
+Not applicable — no upstream repository exists.
+
+## Evidence
+
+### METADATA.pb source block
+No source block present in METADATA.pb.
+
+### google/fonts history
+- Last font modification: `347b8a4d15b6`
+- Date: 2017-05-01 18:20:28 +0100
+- Subject: "hotfix-akronim: v1.002 added (#746)"
+
+## Confidence
+
+**High**: No upstream repository exists for this family.
--- /dev/null
+# Aksara Bali Galang
+
+**Date investigated**: 2026-03-03
+**Model**: Claude Opus 4.6
+**Status**: needs_investigation
+**Designer**: Bemby Bantara Narendra, I Made Suatjana
+**METADATA.pb path**: `ofl/aksarabaligalang/METADATA.pb` (does not exist)
+
+## Source Data
+| Field | Value |
+|-------|-------|
+| Repository URL | `https://github.com/librefonts/aksarabaligalang` (secondary; see notes) |
+| Commit | `unknown` |
+| Config YAML | -- |
+| Branch | -- |
+
+## How the Repository URL Was Found
+
+The font directory `ofl/aksarabaligalang/` in google/fonts has **no METADATA.pb file** and never had one. The font was added in the initial commit of the google/fonts repository (`90abd17b4`, 2015-03-07 by Dave Crossland) and has only been modified twice since, both for technical fixes (nbspace/fsType corrections in commits `06d9851e7` and `bacec3651`, both by Dave Crossland in 2015).
+
+The font binary's name table includes two URLs:
+- `http://www.babadbali.com/` -- Yayasan Bali Galang foundation cultural heritage site
+- `http://aksarabali.wordpress.com/` -- A blog about Balinese script computerization
+
+Neither of these is a source code repository.
+
+A GitHub search found `librefonts/aksarabaligalang` (created 2014-07-16), which contains the font's TTX decomposition and was created by Vitaly Volkov (vitalyvolkov) as part of the librefonts organization's effort to extract individual fonts from the google/fonts monorepo into separate repositories. The initial commit message is "Move aksarabaligalang font files to separate repository." This is **not the original upstream** -- it is a derivative that extracts the font tables into TTX format for the Font Library project.
+
+No original source repository by the font authors (Bemby Bantara Narendra and I Made Suatjana) was found on GitHub or anywhere else.
+
+## How the Commit Hash Was Identified
+
+No commit hash could be identified. The font was part of the initial monorepo commit of google/fonts, which predates structured onboarding with upstream commit tracking. The `librefonts/aksarabaligalang` repo was created later (July 2014) by extracting from google/fonts, so its commits are not original upstream commits.
+
+## How Config YAML Was Resolved
+
+No config.yaml is possible for this font. The only source files that exist are TTX decompositions (XML representations of font tables). There are no gftools-builder compatible sources (.glyphs, .ufo, .designspace) in any known repository. The font was created using specialized tools for Graphite smart font technology and requires Graphite-enabled applications (e.g., Firefox with Graphite support) to render correctly.
+
+## Additional Context
+
+- **Not on Google Fonts catalog**: This font is present in the google/fonts repository but is NOT served through the Google Fonts API or listed on fonts.google.com (returns 404). Issue [#1102](https://github.com/google/fonts/issues/1102) from 2017 explicitly lists AksaraBaliGalang-Regular among fonts in the repo but absent from the API. Issue [#1590](https://github.com/google/fonts/issues/1590) lists it among fonts with no METADATA.pb.
+- **Graphite dependency**: The DESCRIPTION.en_us.html warns that "This font requires a web browser with Graphite support enabled, such as Firefox 11+, to display correctly." This likely explains why it was never fully onboarded to the Google Fonts catalog.
+- **Font version**: Version 1.001, 2012 web release
+- **Copyright**: 2008-2012, Bemby Bantara Narendra and I Made Suatjana
+- **Script**: Balinese (Aksara Bali), an abugida derived from Old Kawi script
+- **Designer websites**: babadbali.com (Yayasan Bali Galang foundation), aksarabali.wordpress.com
+
+## Conclusion
+
+**Confidence: LOW**
+
+Aksara Bali Galang is an edge case: it exists in the google/fonts repository but was never fully onboarded to the Google Fonts catalog (no METADATA.pb, not served via the API). The font uses Graphite smart font technology for complex Balinese script rendering, which is not supported by the standard Google Fonts serving infrastructure.
+
+The `librefonts/aksarabaligalang` repository is a secondary extraction, not an original upstream. No original source repository from the font authors exists on GitHub. The only available "sources" are TTX decompositions, which are not gftools-builder compatible.
+
+This font likely needs a decision from the Google Fonts team about whether to:
+1. Create a METADATA.pb and formally include it in the catalog (would require Graphite rendering support)
+2. Remove it from the repository entirely
+3. Leave it as-is in its current limbo state
+
+No source block can be meaningfully added to METADATA.pb at this time due to the absence of both the METADATA.pb file itself and any gftools-builder compatible upstream source.
--- /dev/null
+# Akshar
+
+**Status**: `complete`
+**Date**: 2026-02-25
+**Designer**: Tall Chai
+**License**: OFL
+**METADATA.pb**: `ofl/akshar/METADATA.pb`
+
+## Data
+
+| Field | Value |
+|-------|-------|
+| Repository URL | https://github.com/tallchai/akshar-type |
+| Commit | `0c6de5ef9cef264b3b3f958e772b3a371f92d083` |
+| Config YAML | `sources/builder.yaml` |
+| Branch | `main` |
+
+## Methodology
+
+### Repository URL
+Pre-existing in METADATA.pb `source { repository_url }` field.
+
+### Commit Hash
+Pre-existing in METADATA.pb `source { commit }` field.
+- Commit date: 2022-05-26 09:15:30 -0400
+- Commit message: "Merge pull request #5 from yanone/main"
+
+### Config YAML
+Found `sources/builder.yaml` in upstream repository at the recorded commit hash.
+
+## Evidence
+
+### METADATA.pb source block
+- `repository_url`: `https://github.com/tallchai/akshar-type`
+- `commit`: `0c6de5ef9cef264b3b3f958e772b3a371f92d083`
+- `config_yaml`: `sources/builder.yaml`
+
+### google/fonts history
+- Last font modification: `ee638854e6c5`
+- Date: 2022-06-01 15:56:18 +0200
+- Subject: "[gftools-packager] Akshar: Version 1.100 added (#4723)"
+
+### Upstream repo cache
+- Cached at: `tallchai/akshar-type`
+- Commit `0c6de5ef9cef` verified ✓
+
+## Confidence
+
+**High**: URL pre-existing in METADATA.pb; commit pre-existing in METADATA.pb
--- /dev/null
+# Alan Sans
+
+**Date investigated**: 2026-03-03
+**Model**: Claude Opus 4.6
+**Status**: complete
+**Designer**: Raphael Ronot
+**METADATA.pb path**: `ofl/alansans/METADATA.pb`
+
+## Source Data
+| Field | Value |
+|-------|-------|
+| Repository URL | https://github.com/alan-eu/Alan-Sans |
+| Commit | `425d3a0674a49f0ad6bc6ceef5ca0c557b520838` |
+| Config YAML | `sources/config.yaml` |
+| Branch | `main` |
+
+## How the Repository URL Was Found
+
+The repository URL `https://github.com/alan-eu/Alan-Sans` was present in the original onboarding METADATA.pb from commit `1b91df7f5` (Sep 5, 2025), authored by Emma Marichal via gftools-packager. The URL is also referenced in the copyright string within the font metadata. The repository exists and is accessible at this URL.
+
+## How the Commit Hash Was Identified
+
+The commit hash `425d3a0674a49f0ad6bc6ceef5ca0c557b520838` was set by the onboarding engineer Emma Marichal in the original METADATA.pb. The onboarding commit message in google/fonts (`1b91df7f5`) explicitly states:
+
+> Taken from the upstream repo https://github.com/alan-eu/Alan-Sans at commit https://github.com/alan-eu/Alan-Sans/commit/425d3a0674a49f0ad6bc6ceef5ca0c557b520838.
+
+This was part of PR #9796, merged on Sep 11, 2025 by Marc Foley. The PR was created by gftools-packager, which automatically records the upstream commit hash.
+
+The commit hash could not be verified locally because the cached upstream repo at `upstream_repos/fontc_crater_cache/alan-eu/Alan-Sans` is a shallow clone with only 1 commit (`11bb823`, from Jan 20, 2026). However, cross-verification supports the hash being correct:
+
+- The font file in google/fonts (134888 bytes) differs from the current upstream HEAD (134900 bytes), confirming the upstream has changed since onboarding.
+- The upstream HEAD commit `11bb823` ("Update AlanSans.glyphs") dates from Jan 2026, well after the Sep 2025 onboarding.
+- The commit hash was recorded automatically by gftools-packager at onboarding time, making it a reliable source.
+
+## How Config YAML Was Resolved
+
+The upstream repo has a `sources/config.yaml` file containing gftools-builder configuration. This file specifies `AlanSans.glyphs` as the source, family name "Alan Sans", with weight axis instances from Light (300) to Black (900).
+
+The `config_yaml: "sources/config.yaml"` field was NOT part of the original onboarding METADATA.pb. It was added later by commit `5ddf312e6` (Feb 20, 2026) as part of a batch enrichment of 82 font families. Because the upstream repo does contain this config file, the `config_yaml` field correctly points to it.
+
+Note: Since this is a shallow clone, we cannot confirm that `sources/config.yaml` existed at the exact commit `425d3a0`. However, it is highly likely given that gftools-packager was used for onboarding (which requires a buildable config), and the enrichment commit verified its presence.
+
+There is no local override `config.yaml` in the google/fonts family directory.
+
+## Conclusion
+
+Alan Sans has a complete source block in METADATA.pb with all required fields: repository URL, commit hash, branch, and config_yaml path. The data was established during original onboarding by Emma Marichal (PR #9796, merged Sep 2025), with the config_yaml field added later during batch enrichment (Feb 2026). The repository URL is valid, the commit hash was recorded by gftools-packager, and the upstream repo contains a proper gftools-builder config.yaml. The upstream repo has received updates since onboarding (Jan 2026 commit), but the referenced commit correctly reflects the version used for the initial catalog addition.
+
+**Confidence**: HIGH
--- /dev/null
+# Alata
+
+**Status**: `complete`
+**Date**: 2026-02-25
+**Designer**: Spyros Zevelakis, Eben Sorkin
+**License**: OFL
+**METADATA.pb**: `ofl/alata/METADATA.pb`
+
+## Data
+
+| Field | Value |
+|-------|-------|
+| Repository URL | https://github.com/SorkinType/Alata |
+| Commit | `3b051d2a6181deba154717cfd6be409effe32ffa` |
+| Config YAML | `sources/config.yaml` |
+| Branch | `master` |
+
+## Methodology
+
+### Repository URL
+Pre-existing in METADATA.pb `source { repository_url }` field.
+
+### Commit Hash
+Pre-existing in METADATA.pb `source { commit }` field.
+- Commit date: 2024-04-19 10:53:52 -0400
+- Commit message: "Merge pull request #11 from emmamarichal/master"
+
+### Config YAML
+Found `sources/config.yaml` in upstream repository at the recorded commit hash.
+
+## Evidence
+
+### METADATA.pb source block
+- `repository_url`: `https://github.com/SorkinType/Alata`
+- `commit`: `3b051d2a6181deba154717cfd6be409effe32ffa`
+- `config_yaml`: `—`
+
+### google/fonts history
+- Last font modification: `953c38e61356`
+- Date: 2024-04-24 10:32:39 +0200
+- Subject: "Alata: Version 1.005; ttfautohint (v1.8.4.7-5d5b) added"
+
+### Upstream repo cache
+- Cached at: `SorkinType/Alata`
+- Commit `3b051d2a6181` verified ✓
+
+## Confidence
+
+**High**: URL pre-existing in METADATA.pb; commit pre-existing in METADATA.pb
--- /dev/null
+# Alatsi
+
+**Status**: `complete`
+**Date**: 2026-02-25
+**Designer**: Spyros Zevelakis, Eben Sorkin
+**License**: OFL
+**METADATA.pb**: `ofl/alatsi/METADATA.pb`
+
+## Data
+
+| Field | Value |
+|-------|-------|
+| Repository URL | https://github.com/SorkinType/Alatsi/ |
+| Commit | `92b5663a41d41e2912ec46cb4e523303e33f9723` |
+| Config YAML | `sources/config.yaml` |
+| Branch | `main` |
+
+## Methodology
+
+### Repository URL
+Pre-existing in METADATA.pb `source { repository_url }` field.
+
+### Commit Hash
+Pre-existing in METADATA.pb `source { commit }` field.
+- Commit date: 2024-05-02 12:48:22 -0400
+- Commit message: "Merge pull request #7 from yanone/main"
+
+### Config YAML
+Found `sources/config.yaml` in upstream repository at the recorded commit hash.
+
+## Evidence
+
+### METADATA.pb source block
+- `repository_url`: `https://github.com/SorkinType/Alatsi/`
+- `commit`: `92b5663a41d41e2912ec46cb4e523303e33f9723`
+- `config_yaml`: `sources/config.yaml`
+
+### google/fonts history
+- Last font modification: `196ccfe85a16`
+- Date: 2024-05-03 09:26:46 +0200
+- Subject: "Alatsi: Version 1.008; ttfautohint (v1.8.4.7-5d5b) added"
+
+### Upstream repo cache
+- Cached at: `SorkinType/Alatsi`
+- Commit `92b5663a41d4` verified ✓
+
+## Confidence
+
+**High**: URL pre-existing in METADATA.pb; commit pre-existing in METADATA.pb
--- /dev/null
+# Albert Sans
+
+**Date investigated**: 2026-03-03
+**Model**: Claude Opus 4.6
+**Status**: needs_correction
+**Designer**: Andreas Rasmussen
+**METADATA.pb path**: `ofl/albertsans/METADATA.pb`
+
+## Source Data
+
+| Field | Value |
+|-------|-------|
+| Repository URL | https://github.com/usted/Albert-Sans |
+| Commit (current in METADATA.pb) | `f7f46082233f5a29cb71d6ae1d8d0ef9c7962d6c` |
+| Commit (correct for onboarding) | `929c7d5058afd06870d1dd4ebc3a0ee98bb77420` |
+| Config YAML | `sources/config.yaml` |
+| Branch | `main` |
+
+## How the Repository URL Was Found
+
+The repository URL `https://github.com/usted/Albert-Sans` was present in METADATA.pb since the original onboarding commit. It was also referenced in the copyright string of the font files and in the PR #4756 commit message. The cached upstream repo at `usted/Albert-Sans` confirms the remote matches.
+
+## How the Commit Hash Was Identified
+
+### Original onboarding commit: `929c7d5`
+
+The font was onboarded in google/fonts via PR #4756 (commit `6b612533`, merged 2022-06-16) by Emma Marichal. The commit message explicitly states:
+
+> Albert Sans Version 1.025 taken from the upstream repo https://github.com/usted/Albert-Sans at commit https://github.com/usted/Albert-Sans/commit/929c7d5058afd06870d1dd4ebc3a0ee98bb77420.
+
+This commit was dated 2022-06-03 in the upstream repo with message "fonts folder". Binary file verification confirms this is the correct onboarding commit: the SHA-256 hash of `fonts/variable/AlbertSans[wght].ttf` at commit `929c7d5` matches the file currently in `ofl/albertsans/AlbertSans[wght].ttf` exactly (`8fe5d4cf5822d7096d4d17ad781c90f97c745ac13a22be619db74966fba45fda`).
+
+### Current (incorrect) commit: `f7f4608`
+
+The commit hash was changed from `929c7d5` to `f7f4608` by the "[Batch 1/4] port info from fontc_crater targets list" commit (`19cdcec5`, 2025-03-31). This batch operation ported commit hashes from fontc_crater's `targets.json`, which tracks the latest upstream HEAD for building/testing purposes, not the original onboarding commits.
+
+Commit `f7f4608` is dated 2024-07-30, over two years after the onboarding. At this commit, the `fonts/variable/` directory no longer exists (it was removed in commit `8ec0279` on 2024-03-29), which means the `files` block in METADATA.pb (which references `fonts/variable/AlbertSans[wght].ttf`) is now inconsistent with the referenced commit.
+
+### Recommendation
+
+The commit hash should be reverted to `929c7d5058afd06870d1dd4ebc3a0ee98bb77420`, which is the verified original onboarding commit. This restores consistency between the commit hash, the file mappings, and the actual font binaries in google/fonts.
+
+## How Config YAML Was Resolved
+
+The upstream repo has `sources/config.yaml` present at both commits, but with different content:
+
+- **At `929c7d5` (onboarding)**: A more detailed config with source file references (`AlbertSans.glyphs`, `AlbertSans-Italic.glyphs`), axis order (`wght`, `ital`), family name, and full STAT table definitions.
+- **At `f7f4608` (current HEAD)**: A simpler config referencing renamed source files (`AlbertSans-Roman.glyphs`, `AlbertSans-Italic.glyphs`) with axis order (`wght`, `wdth`) and no STAT table.
+
+The `config_yaml: "sources/config.yaml"` field in METADATA.pb is valid for either commit. No override config.yaml is needed since the upstream repo provides one.
+
+## Detailed Timeline
+
+| Date | Event |
+|------|-------|
+| 2022-06-03 | Upstream commit `929c7d5` ("fonts folder") - adds compiled variable fonts |
+| 2022-06-16 | PR #4756 merged in google/fonts by Emma Marichal, onboarding Albert Sans v1.025 from commit `929c7d5` |
+| 2024-04-03 | Commit `66f91f1` by Simon Cozens merges upstream.yaml into METADATA.pb, adding `files`, `branch` fields (commit hash unchanged at `929c7d5`) |
+| 2024-03-29 | Upstream commit `8ec0279` removes the `fonts/` directory entirely |
+| 2024-07-30 | Upstream commit `f7f4608` (current HEAD) - source file updates |
+| 2025-03-31 | Batch 1/4 commit `19cdcec5` changes commit hash from `929c7d5` to `f7f4608` and adds `config_yaml` field |
+
+## Conclusion
+
+**Status**: needs_correction
+**Confidence**: HIGH
+
+The repository URL is correct. The `config_yaml` path (`sources/config.yaml`) is valid. However, the commit hash `f7f4608` currently in METADATA.pb is incorrect -- it was introduced by a batch import from fontc_crater targets and represents the latest upstream HEAD, not the original onboarding commit.
+
+The correct onboarding commit is `929c7d5058afd06870d1dd4ebc3a0ee98bb77420`, confirmed by:
+1. The explicit reference in the PR #4756 commit message
+2. Binary file hash verification (exact SHA-256 match)
+3. The `fonts/variable/` directory existing at `929c7d5` but not at `f7f4608`, making the current `files` block inconsistent
+
+The commit hash should be reverted to `929c7d5`. Note that the `config_yaml` field is valid at both commits, so it can remain as-is.
--- /dev/null
+# Alef
+
+**Status**: `no_upstream_repo`
+**Date**: 2026-02-25
+**Designer**: Hagilda, Mushon Zer-Aviv
+**License**: OFL
+**METADATA.pb**: `ofl/alef/METADATA.pb`
+
+## Data
+
+| Field | Value |
+|-------|-------|
+| Repository URL | — |
+| Commit | unknown |
+| Config YAML | — |
+
+## Methodology
+
+### Repository URL
+No upstream repository URL found.
+
+### Commit Hash
+Commit hash unknown — could not be determined.
+
+### Config YAML
+Not applicable — no upstream repository exists.
+
+## Evidence
+
+### METADATA.pb source block
+No source block present in METADATA.pb.
+
+### google/fonts history
+- Last font modification: `351666924b11`
+- Date: 2017-05-01 18:18:17 +0100
+- Subject: "hotfix-alef: v1.002 added (#748)"
+
+## Confidence
+
+**High**: No upstream repository exists for this family.
--- /dev/null
+# Alegreya
+
+**Status**: `complete`
+**Date**: 2026-02-25
+**Designer**: Juan Pablo del Peral, Huerta Tipográfica
+**License**: OFL
+**METADATA.pb**: `ofl/alegreya/METADATA.pb`
+
+## Data
+
+| Field | Value |
+|-------|-------|
+| Repository URL | https://github.com/huertatipografica/Alegreya |
+| Commit | `1dd6b28b57c50e3168db1cbbb8086e7978abcfbf` |
+| Config YAML | Override in google/fonts family directory |
+| Branch | `master` |
+
+## Methodology
+
+### Repository URL
+Pre-existing in METADATA.pb `source { repository_url }` field.
+
+### Commit Hash
+Pre-existing in METADATA.pb `source { commit }` field.
+- Commit date: 2020-10-07 12:22:29 +0200
+- Commit message: "build details"
+
+### Config YAML
+Override `config.yaml` exists in the google/fonts family directory. Per policy, `config_yaml` field is omitted from METADATA.pb.
+
+## Evidence
+
+### METADATA.pb source block
+- `repository_url`: `https://github.com/huertatipografica/Alegreya`
+- `commit`: `1dd6b28b57c50e3168db1cbbb8086e7978abcfbf`
+- `config_yaml`: `—`
+
+### google/fonts history
+- Last font modification: `40478177239c`
+- Date: 2021-01-08 11:38:32 +0000
+- Subject: "Alegreya: Version 2.009 added (#2927)"
+
+### Upstream repo cache
+- Cached at: `huertatipografica/Alegreya`
+- Commit `1dd6b28b57c5` verified ✓
+
+### Override config
+Override `config.yaml` exists in `ofl/alegreya/config.yaml`.
+
+## Confidence
+
+**High**: URL pre-existing in METADATA.pb; commit pre-existing in METADATA.pb
--- /dev/null
+# Alegreya Sans
+
+**Date investigated**: 2026-03-03
+**Model**: Claude Opus 4.6
+**Status**: complete
+**Designer**: Juan Pablo del Peral, Huerta Tipografica
+**METADATA.pb path**: `ofl/alegreyasans/METADATA.pb`
+
+## Source Data
+| Field | Value |
+|-------|-------|
+| Repository URL | https://github.com/huertatipografica/Alegreya-Sans |
+| Commit | `030b9ac01fd9bcaccac0ebc8010283175f9ced4e` |
+| Config YAML | override config.yaml in google/fonts |
+| Branch | master |
+
+## How the Repository URL Was Found
+
+The repository URL `https://github.com/huertatipografica/Alegreya-Sans` is already present in the METADATA.pb source block. It was first added by Simon Cozens in commit `5f2b22f48` ("Update upstreams", 2023-12-14). The URL is also referenced in:
+
+- The font copyright strings in METADATA.pb: "Copyright 2013 The Alegreya Sans Project Authors (https://github.com/huertatipografica/Alegreya-Sans)"
+- The PR #1312 commit message by Marc Foley: "Taken from the upstream repo https://github.com/huertatipografica/Alegreya-Sans"
+- The PR #1312 body, which references the upstream issue https://github.com/huertatipografica/Alegreya-Sans/issues/11
+
+The cached clone at `huertatipografica/Alegreya-Sans` confirms the remote URL matches.
+
+## How the Commit Hash Was Identified
+
+The commit `030b9ac01fd9bcaccac0ebc8010283175f9ced4e` ("restored new characters", 2017-11-09 12:26:22 -0300) was already recorded in METADATA.pb. It was added by Felipe Sanches in commit `d8104312f` (2025-10-24) as part of the source metadata enrichment project.
+
+**Verification**: PR #1312 in google/fonts was authored by Marc Foley and merged on 2017-11-09T17:09:16Z. The commit message states "alegreyasans: v2.004 added." and "Taken from the upstream repo". The upstream commit `030b9ac` was the latest commit in the upstream repo at that time (authored at 15:26:22 UTC, about 1.7 hours before the PR merge at 17:09:16 UTC). There are 13 additional upstream commits after `030b9ac` (the next one, `8fe9ef8`, is from 2017-11-10, after the merge date).
+
+**Binary file comparison**: The TTF files in google/fonts match those in the upstream repo's `fonts/ttf/` directory at commit `030b9ac`. For example, `AlegreyaSans-Bold.ttf` is exactly 266,856 bytes in both locations. `AlegreyaSans-Regular.ttf` differs by only 8 bytes (263,796 upstream vs 263,804 in google/fonts), likely due to minor post-processing. This confirms the fonts were taken from this commit.
+
+## How Config YAML Was Resolved
+
+The upstream repository does **not** have a `config.yaml` file at any commit. The source files are Glyphs format:
+- `sources/Alegreya_Sans.glyphs`
+- `sources/Alegreya_Sans-Italic.glyphs`
+
+An override `config.yaml` was created in the google/fonts family directory at `ofl/alegreyasans/config.yaml` (added in commit `d8104312f`, 2025-10-24). The override contains:
+
+```yaml
+buildVariable: false
+sources:
+ - sources/Alegreya_Sans.glyphs
+ - sources/Alegreya_Sans-Italic.glyphs
+```
+
+This correctly references the two Glyphs source files in the upstream repo at the referenced commit, with `buildVariable: false` since the family is static (14 individual weight/style TTF files). The `config_yaml` field is intentionally omitted from the METADATA.pb source block because google-fonts-sources auto-detects local override config files.
+
+## Conclusion
+
+**Confidence: HIGH**
+
+The source metadata for Alegreya Sans is complete and verified. The repository URL is confirmed through multiple sources (copyright strings, PR references, commit messages). The commit hash `030b9ac` is the correct onboarding commit for v2.004, verified by timeline analysis (it was the latest upstream commit before PR #1312 was merged) and binary file size comparison. The override config.yaml in google/fonts correctly references the Glyphs sources. The family has 14 static instances (7 weights x 2 styles: Thin through Black, each with Roman and Italic).
--- /dev/null
+# Aleo
+
+**Status**: `complete`
+**Date**: 2026-02-25
+**Designer**: Alessio Laiso
+**License**: OFL
+**METADATA.pb**: `ofl/aleo/METADATA.pb`
+
+## Data
+
+| Field | Value |
+|-------|-------|
+| Repository URL | https://github.com/AlessioLaiso/aleo |
+| Commit | `ce875e48d9983031648e87f38b7a269f4fbf5eb5` |
+| Config YAML | `sources/config.yaml` |
+| Branch | `master` |
+
+## Methodology
+
+### Repository URL
+Pre-existing in METADATA.pb `source { repository_url }` field.
+
+### Commit Hash
+Pre-existing in METADATA.pb `source { commit }` field.
+- Commit date: 2023-06-03 10:18:27 +0200
+- Commit message: "Merge pull request #4 from emmamarichal/master"
+
+### Config YAML
+Found `sources/config.yaml` in upstream repository at the recorded commit hash.
+
+## Evidence
+
+### METADATA.pb source block
+- `repository_url`: `https://github.com/AlessioLaiso/aleo`
+- `commit`: `ce875e48d9983031648e87f38b7a269f4fbf5eb5`
+- `config_yaml`: `—`
+
+### google/fonts history
+- Last font modification: `630dd51f0b28`
+- Date: 2023-06-06 17:51:27 +0200
+- Subject: "[gftools-packager] Aleo: Version 2.001;gftools[0.9.29] added"
+
+### Upstream repo cache
+- Cached at: `AlessioLaiso/aleo`
+- Commit `ce875e48d998` verified ✓
+
+## Confidence
+
+**High**: URL pre-existing in METADATA.pb; commit pre-existing in METADATA.pb
--- /dev/null
+# Alexandria
+
+**Status**: `complete`
+**Date**: 2026-02-25
+**Designer**: Mohamed Gaber, Julieta Ulanovsky
+**License**: OFL
+**METADATA.pb**: `ofl/alexandria/METADATA.pb`
+
+## Data
+
+| Field | Value |
+|-------|-------|
+| Repository URL | https://github.com/Gue3bara/Alexandria |
+| Commit | `4fd1422be3488837c41fbdb84a77350f0f56a734` |
+| Config YAML | `sources/config.yaml` |
+| Branch | `master` |
+
+## Methodology
+
+### Repository URL
+Pre-existing in METADATA.pb `source { repository_url }` field.
+
+### Commit Hash
+Pre-existing in METADATA.pb `source { commit }` field.
+- Commit date: 2022-12-05 10:05:29 +0200
+- Commit message: "updated hamza below mark"
+
+### Config YAML
+Found `sources/config.yaml` in upstream repository at the recorded commit hash.
+
+## Evidence
+
+### METADATA.pb source block
+- `repository_url`: `https://github.com/Gue3bara/Alexandria`
+- `commit`: `4fd1422be3488837c41fbdb84a77350f0f56a734`
+- `config_yaml`: `—`
+
+### google/fonts history
+- Last font modification: `31738c3f5965`
+- Date: 2022-11-04 15:00:20 +0100
+- Subject: "Alexandria: Version 5.100 added (#5506)"
+
+### Upstream repo cache
+- Cached at: `Gue3bara/Alexandria`
+- Commit `4fd1422be348` verified ✓
+
+## Confidence
+
+**High**: URL pre-existing in METADATA.pb; commit pre-existing in METADATA.pb
--- /dev/null
+# Alex Brush
+
+**Date investigated**: 2026-03-03
+**Model**: Claude Opus 4.6
+**Status**: complete
+**Designer**: Robert Leuschke
+**METADATA.pb path**: `ofl/alexbrush/METADATA.pb`
+
+## Source Data
+| Field | Value |
+|-------|-------|
+| Repository URL | https://github.com/googlefonts/alex-brush |
+| Commit | `1a50bd10383f6c5416f5b4806a9368fd2009ea8c` |
+| Config YAML | `sources/config.yml` |
+| Branch | `main` |
+
+## How the Repository URL Was Found
+
+The repository URL `https://github.com/googlefonts/alex-brush` is already recorded in the METADATA.pb `source` block. It was originally added via the gftools-packager commit `3f9fd6d69` (PR #5686), which explicitly references the upstream repo in its commit message:
+
+> "Alex Brush Version 1.111; ttfautohint (v1.8.4.7-5d5b) taken from the upstream repo https://github.com/googlefonts/alex-brush at commit https://github.com/googlefonts/alex-brush/commit/1a50bd10383f6c5416f5b4806a9368fd2009ea8c"
+
+The cached clone at `upstream_repos/fontc_crater_cache/googlefonts/alex-brush` confirms the remote URL matches: `https://github.com/googlefonts/alex-brush`.
+
+## How the Commit Hash Was Identified
+
+The commit `1a50bd10383f6c5416f5b4806a9368fd2009ea8c` ("winDescent small fix" by Viviana Monsalve, 2022-12-08) is verified through multiple lines of evidence:
+
+1. **gftools-packager commit message**: The google/fonts commit `3f9fd6d69` (PR #5686, 2022-12-09) explicitly states the font was taken from this exact commit hash.
+2. **Temporal consistency**: The upstream commit is dated 2022-12-08 and the google/fonts onboarding is dated 2022-12-09 -- the very next day.
+3. **Only commit in the repo**: The upstream repository contains a single squashed commit (`1a50bd1`), which is also HEAD of `main`. There are no other commits that could be confused with it.
+4. **Binary file identity**: The TTF file at this commit (`fonts/ttf/AlexBrush-Regular.ttf`, 116,244 bytes) has an identical SHA-256 hash (`df702038d8e27797230c77959c139eeea38cac0caf53e19ea5b513d3b0d3362d`) to the file in `ofl/alexbrush/AlexBrush-Regular.ttf` in google/fonts.
+
+## How Config YAML Was Resolved
+
+The config file `sources/config.yml` exists at the referenced commit and contains:
+
+```yaml
+sources:
+ - AlexBrush.glyphs
+familyName: "Alex Brush"
+buildVariable: false
+# autohintTTF: false
+```
+
+This is a valid gftools-builder configuration pointing to the Glyphs source file `sources/AlexBrush.glyphs`, which also exists in the repository at the referenced commit. The `config_yaml` field in METADATA.pb correctly points to `sources/config.yml`.
+
+## Conclusion
+
+**Confidence: HIGH**
+
+All source metadata for Alex Brush is complete and verified. The repository URL, commit hash, config YAML path, and branch are all correctly recorded in METADATA.pb. The binary font file in google/fonts is an exact byte-for-byte match with the file from the referenced upstream commit. The upstream repo is a single-commit repository, making verification straightforward. No changes are needed.
--- /dev/null
+# Alice
+
+**Status**: `complete`
+**Date**: 2026-02-25
+**Designer**: Ksenya Erulevich, Cyreal
+**License**: OFL
+**METADATA.pb**: `ofl/alice/METADATA.pb`
+
+## Data
+
+| Field | Value |
+|-------|-------|
+| Repository URL | https://github.com/cyrealtype/Alice |
+| Commit | `13be04734d33464e627bd201d35aa9697feed289` |
+| Config YAML | `sources/config.yaml` |
+| Branch | `master` |
+
+## Methodology
+
+### Repository URL
+Pre-existing in METADATA.pb `source { repository_url }` field.
+
+### Commit Hash
+Pre-existing in METADATA.pb `source { commit }` field.
+- Commit date: 2021-11-26 14:50:55 +0100
+- Commit message: "Version number updated in source file / Font re-exported"
+
+### Config YAML
+Found `sources/config.yaml` in upstream repository at the recorded commit hash.
+
+## Evidence
+
+### METADATA.pb source block
+- `repository_url`: `https://github.com/cyrealtype/Alice`
+- `commit`: `13be04734d33464e627bd201d35aa9697feed289`
+- `config_yaml`: `—`
+
+### google/fonts history
+- Last font modification: `edfdc270a7be`
+- Date: 2021-12-08 12:19:13 +0100
+- Subject: "Alice: Version 2.003; ttfautohint (v1.8.3) added (#4145)"
+
+### Upstream repo cache
+- Cached at: `cyrealtype/Alice`
+- Commit `13be04734d33` verified ✓
+
+## Confidence
+
+**High**: URL pre-existing in METADATA.pb; commit pre-existing in METADATA.pb
--- /dev/null
+# Alike
+
+**Status**: `complete`
+**Date**: 2026-02-25
+**Designer**: Sveta Sebyakina, Cyreal
+**License**: OFL
+**METADATA.pb**: `ofl/alike/METADATA.pb`
+
+## Data
+
+| Field | Value |
+|-------|-------|
+| Repository URL | https://github.com/cyrealtype/Alike |
+| Commit | `2de9216949bad46e02460fcb9e455be87d75462d` |
+| Config YAML | `sources/config.yaml` |
+| Branch | `main` |
+
+## Methodology
+
+### Repository URL
+Pre-existing in METADATA.pb `source { repository_url }` field.
+
+### Commit Hash
+Pre-existing in METADATA.pb `source { commit }` field.
+- Commit date: 2023-11-02 10:08:34 +0100
+- Commit message: "Merge pull request #6 from emmamarichal/main"
+
+### Config YAML
+Found `sources/config.yaml` in upstream repository at the recorded commit hash.
+
+## Evidence
+
+### METADATA.pb source block
+- `repository_url`: `https://github.com/cyrealtype/Alike`
+- `commit`: `2de9216949bad46e02460fcb9e455be87d75462d`
+- `config_yaml`: `—`
+
+### google/fonts history
+- Last font modification: `f86569dbc328`
+- Date: 2023-11-02 10:27:27 +0100
+- Subject: "[gftools-packager] Alike: Version 1.301; ttfautohint (v1.8.4.7-5d5b) added"
+
+### Upstream repo cache
+- Cached at: `cyrealtype/Alike`
+- Commit `2de9216949ba` verified ✓
+
+## Confidence
+
+**High**: URL pre-existing in METADATA.pb; commit pre-existing in METADATA.pb
--- /dev/null
+# Alike Angular
+
+**Date investigated**: 2026-03-03
+**Model**: Claude Opus 4.6
+**Status**: complete
+**Designer**: Sveta Sebyakina, Cyreal
+**METADATA.pb path**: `ofl/alikeangular/METADATA.pb`
+
+## Source Data
+| Field | Value |
+|-------|-------|
+| Repository URL | https://github.com/cyrealtype/Alike-Angular |
+| Commit | `20765691758ef999907b9a20950d4f57f62de1d1` |
+| Config YAML | `sources/config.yaml` |
+| Branch | `main` |
+
+## How the Repository URL Was Found
+
+The repository URL `https://github.com/cyrealtype/Alike-Angular` was already present in the METADATA.pb `source` block. It was originally added by Emma Marichal in commit `ba0196b6` on 2023-11-02 via gftools-packager, which explicitly referenced the upstream repo in its commit message. The URL matches the copyright notice in the font metadata.
+
+## How the Commit Hash Was Identified
+
+The commit hash `20765691758ef999907b9a20950d4f57f62de1d1` was set by the gftools-packager commit `ba0196b6` in google/fonts, which states:
+
+> Alike Angular Version 1.300; ttfautohint (v1.8.4.7-5d5b) taken from the upstream repo https://github.com/cyrealtype/Alike-Angular at commit https://github.com/cyrealtype/Alike-Angular/commit/20765691758ef999907b9a20950d4f57f62de1d1.
+
+**Verification**:
+- The upstream repo has only one commit on the `main` branch (this merge commit), so there is no ambiguity about which commit was used.
+- The `main` branch HEAD points directly to `2076569`.
+- The binary TTF at `fonts/ttf/AlikeAngular-Regular.ttf` in the upstream repo at this commit has SHA256 `3706438e11bb219d6dbbb19958b637dc19470638da28fd97a620f7d7069bf448`, which matches the file in google/fonts exactly.
+- The upstream commit is dated 2023-11-02, and the google/fonts packager commit is also dated 2023-11-02, consistent with same-day onboarding.
+
+## How Config YAML Was Resolved
+
+The `config_yaml` field is set to `sources/config.yaml` in METADATA.pb. This file exists in the upstream repo at the referenced commit and contains:
+
+```yaml
+sources:
+ - AlikeAngular.glyphs
+familyName: Alike Angular
+```
+
+This is a valid gftools-builder configuration pointing to the `.glyphs` source file at `sources/AlikeAngular.glyphs`. The `config_yaml` field was added by the "Batch 1/4" commit (`19cdcec5`) which ported info from the fontc_crater targets list. No override config.yaml exists in the google/fonts family directory.
+
+## Conclusion
+
+This family's source metadata is fully complete and verified with HIGH confidence. The repository URL, commit hash, branch, and config_yaml are all correct. The binary font file in google/fonts is an exact byte-for-byte match with the file from the upstream repo at the referenced commit. The upstream repo contains gftools-builder compatible sources (`.glyphs` file) with a proper `config.yaml`.
--- /dev/null
+# Alkatra
+
+**Status**: `complete`
+**Date**: 2026-02-25
+**Designer**: Suman Bhandary
+**License**: OFL
+**METADATA.pb**: `ofl/alkatra/METADATA.pb`
+
+## Data
+
+| Field | Value |
+|-------|-------|
+| Repository URL | https://github.com/suman51284/Alkatra |
+| Commit | `0192cbf706f1dc560534c73153fd0e566323b31e` |
+| Config YAML | `Sources/config.yaml` |
+| Branch | `master` |
+
+## Methodology
+
+### Repository URL
+Pre-existing in METADATA.pb `source { repository_url }` field.
+
+### Commit Hash
+Pre-existing in METADATA.pb `source { commit }` field.
+- Commit date: 2023-01-26 20:38:24 +0530
+- Commit message: "Merge pull request #8 from yanone/master"
+
+### Config YAML
+Found `Sources/config.yaml` in upstream repository at the recorded commit hash.
+
+## Evidence
+
+### METADATA.pb source block
+- `repository_url`: `https://github.com/suman51284/Alkatra`
+- `commit`: `0192cbf706f1dc560534c73153fd0e566323b31e`
+- `config_yaml`: `—`
+
+### google/fonts history
+- Last font modification: `f3ea1c2b8aa1`
+- Date: 2023-01-27 13:47:09 +0100
+- Subject: "[gftools-packager] Alkatra: Version 1.100;gftools[0.9.22] added"
+
+### Upstream repo cache
+- Cached at: `suman51284/Alkatra`
+- Commit `0192cbf706f1` verified ✓
+
+## Confidence
+
+**High**: URL pre-existing in METADATA.pb; commit pre-existing in METADATA.pb
--- /dev/null
+# Allison
+
+**Status**: `complete`
+**Date**: 2026-02-25
+**Designer**: Robert Leuschke
+**License**: OFL
+**METADATA.pb**: `ofl/allison/METADATA.pb`
+
+## Data
+
+| Field | Value |
+|-------|-------|
+| Repository URL | https://github.com/googlefonts/allison |
+| Commit | `fe224232fbcf0a6db60877e835df7219a99784f3` |
+| Config YAML | `sources/config.yml` |
+| Branch | `master` |
+
+## Methodology
+
+### Repository URL
+Pre-existing in METADATA.pb `source { repository_url }` field.
+
+### Commit Hash
+Pre-existing in METADATA.pb `source { commit }` field.
+- Commit date: 2021-08-06 17:48:52 -0500
+- Commit message: "Nhung added to Contributors"
+
+### Config YAML
+Found `sources/config.yml` in upstream repository at the recorded commit hash.
+
+## Evidence
+
+### METADATA.pb source block
+- `repository_url`: `https://github.com/googlefonts/allison`
+- `commit`: `fe224232fbcf0a6db60877e835df7219a99784f3`
+- `config_yaml`: `—`
+
+### google/fonts history
+- Last font modification: `3e7d7585d218`
+- Date: 2021-07-15 04:57:07 -0500
+- Subject: "Allison: Version 1.010; ttfautohint (v1.8.3) added (#3574)"
+
+### Upstream repo cache
+- Cached at: `googlefonts/allison`
+- Commit `fe224232fbcf` verified ✓
+
+## Confidence
+
+**High**: URL pre-existing in METADATA.pb; commit pre-existing in METADATA.pb
--- /dev/null
+# Allura
+
+**Status**: `complete`
+**Date**: 2026-02-25
+**Designer**: Robert Leuschke
+**License**: OFL
+**METADATA.pb**: `ofl/allura/METADATA.pb`
+
+## Data
+
+| Field | Value |
+|-------|-------|
+| Repository URL | https://github.com/googlefonts/allura |
+| Commit | `38a78b41510a10b1129c50fa5177b642bd2b4a19` |
+| Config YAML | `sources/config.yml` |
+| Branch | `main` |
+
+## Methodology
+
+### Repository URL
+Pre-existing in METADATA.pb `source { repository_url }` field.
+
+### Commit Hash
+Pre-existing in METADATA.pb `source { commit }` field.
+- Commit date: 2022-12-14 19:49:15 -0500
+- Commit message: "Readme sample path fix"
+
+### Config YAML
+Found `sources/config.yml` in upstream repository at the recorded commit hash.
+
+## Evidence
+
+### METADATA.pb source block
+- `repository_url`: `https://github.com/googlefonts/allura`
+- `commit`: `38a78b41510a10b1129c50fa5177b642bd2b4a19`
+- `config_yaml`: `—`
+
+### google/fonts history
+- Last font modification: `df7361c02f95`
+- Date: 2022-12-15 06:14:17 -0500
+- Subject: "[gftools-packager] Allura: Version 1.110 added (#5716)"
+
+### Upstream repo cache
+- Cached at: `googlefonts/allura`
+- Commit `38a78b41510a` verified ✓
+
+## Confidence
+
+**High**: URL pre-existing in METADATA.pb; commit pre-existing in METADATA.pb
--- /dev/null
+# Alumni Sans Collegiate One
+
+**Date investigated**: 2026-03-03
+**Model**: Claude Opus 4.6
+**Status**: complete
+**Designer**: Robert Leuschke
+**METADATA.pb path**: `ofl/alumnisanscollegiateone/METADATA.pb`
+
+## Source Data
+| Field | Value |
+|-------|-------|
+| Repository URL | https://github.com/googlefonts/alumni-sans-collegiate |
+| Commit | `9dc96be1ead732fb1677c88632665e0bbf2e4ee2` |
+| Config YAML | `sources/config.yml` |
+| Branch | `main` |
+
+## How the Repository URL Was Found
+
+The repository URL was already present in the METADATA.pb `source {}` block, set to `https://github.com/googlefonts/alumni-sans-collegiate`. This was confirmed by:
+
+1. The google/fonts commit `0df02275b` (initial onboarding, PR #4489, April 2022) explicitly references the same upstream repo URL in its gftools-packager message.
+2. The google/fonts commit `87033c631` (version 1.100 update, PR #4855, July 2022) also references the same repo URL.
+3. The cached repo at `googlefonts/alumni-sans-collegiate` has its remote set to `https://github.com/googlefonts/alumni-sans-collegiate`.
+4. The copyright string in METADATA.pb references the same GitHub URL.
+
+## How the Commit Hash Was Identified
+
+The commit hash `9dc96be1ead732fb1677c88632665e0bbf2e4ee2` was already recorded in the METADATA.pb source block. Verification:
+
+1. **Commit exists in upstream repo**: Confirmed. The commit is authored by Viviana Monsalve on 2022-06-30 with message "sample image updated". This is the only commit in the repository -- it is the initial commit that added all files.
+2. **Referenced in google/fonts**: The gftools-packager commit `87033c631` (PR #4855) explicitly states: "Alumni Sans Collegiate One Version 1.100 taken from the upstream repo ... at commit 9dc96be1ead732fb1677c88632665e0bbf2e4ee2".
+3. **Binary file size match**: The TTF files at commit `9dc96be` in the upstream repo exactly match the files in google/fonts:
+ - `AlumniSansCollegiateOne-Regular.ttf`: 163,484 bytes (both locations)
+ - `AlumniSansCollegiateOne-Italic.ttf`: 173,756 bytes (both locations)
+4. **Only commit in repo**: Since this is the sole commit in the upstream repository, there is no ambiguity about which commit was used.
+
+## How Config YAML Was Resolved
+
+The config file exists in the upstream repo at `sources/config.yml` and is referenced in METADATA.pb via `config_yaml: "sources/config.yml"`. The config was present at commit `9dc96be` (the only commit) and contains:
+
+```yaml
+sources:
+ - AlumniSansCollegiate.glyphs
+ - AlumniSansCollegiate-Italic.glyphs
+familyName: "Alumni Sans Collegiate One"
+buildVariable: false
+autohintTTF: false
+```
+
+The source files referenced in the config (`AlumniSansCollegiate.glyphs` and `AlumniSansCollegiate-Italic.glyphs`) are present in the `sources/` directory. No override config.yaml exists in the google/fonts family directory.
+
+**Note**: This config specifies `familyName: "Alumni Sans Collegiate One"`, which means it only builds the non-SC variant. The sibling family "Alumni Sans Collegiate One SC" shares the same upstream repository but would need a separate config to build the small caps variant (the SC fonts are likely produced from the same `.glyphs` sources using a different family name filter or separate build step).
+
+## Sibling Family
+
+This upstream repo also hosts **Alumni Sans Collegiate One SC**, which shares the same repository URL and commit hash. The SC variant was onboarded in a separate google/fonts commit (`9b0b4fda4`).
+
+## Conclusion
+
+This family is **fully documented** with high confidence. The repository URL, commit hash, branch, and config.yaml path are all correctly recorded in METADATA.pb. The commit hash is verified both by explicit reference in the gftools-packager commit message (PR #4855) and by exact binary file size matching. The upstream repo contains only a single commit, eliminating any ambiguity.
+
+**Confidence: HIGH**
--- /dev/null
+# Alumni Sans Collegiate One SC
+
+**Date investigated**: 2026-03-03
+**Model**: Claude Opus 4.6
+**Status**: missing_config
+**Designer**: Robert Leuschke
+**METADATA.pb path**: `ofl/alumnisanscollegiateonesc/METADATA.pb`
+
+## Source Data
+
+| Field | Value |
+|-------|-------|
+| Repository URL | https://github.com/googlefonts/alumni-sans-collegiate |
+| Commit | `9dc96be1ead732fb1677c88632665e0bbf2e4ee2` |
+| Config YAML | `sources/config.yml` (set in METADATA.pb, but see notes below) |
+| Branch | main |
+
+## How the Repository URL Was Found
+
+The repository URL `https://github.com/googlefonts/alumni-sans-collegiate` is already recorded in the METADATA.pb `source {}` block. It was confirmed by the onboarding commit in google/fonts (`9b0b4fda4`, 2024-05-27) and PR #7769, both of which explicitly reference this upstream repository. The repo is cached at `googlefonts/alumni-sans-collegiate` and is accessible.
+
+## How the Commit Hash Was Identified
+
+The commit hash `9dc96be1ead732fb1677c88632665e0bbf2e4ee2` was explicitly stated in:
+
+1. The google/fonts onboarding commit message (`9b0b4fda4`): "Taken from the upstream repo https://github.com/googlefonts/alumni-sans-collegiate at commit https://github.com/googlefonts/alumni-sans-collegiate/commit/9dc96be1ead732fb1677c88632665e0bbf2e4ee2."
+2. PR #7769 body, authored by Simon Cozens (`simoncozens`), merged 2024-05-30.
+3. The METADATA.pb `source {}` block.
+
+The upstream repository has only a single commit (`9dc96be`, dated 2022-06-30), which is also HEAD. This means there is no ambiguity about the commit -- it is the only one in the repository, and it was correctly referenced during onboarding.
+
+## How Config YAML Was Resolved
+
+The METADATA.pb `source {}` block sets `config_yaml: "sources/config.yml"`. This file exists at the referenced commit and contains:
+
+```yaml
+sources:
+ - AlumniSansCollegiate.glyphs
+ - AlumniSansCollegiate-Italic.glyphs
+familyName: "Alumni Sans Collegiate One"
+buildVariable: false
+autohintTTF: false
+```
+
+**Critical issue**: This config builds the **non-SC** family "Alumni Sans Collegiate One", not the SC variant. The `familyName` is set to "Alumni Sans Collegiate One", and building with this config produces `AlumniSansCollegiateOne-Regular.ttf` and `AlumniSansCollegiateOne-Italic.ttf` -- the non-SC fonts.
+
+The SC variant ("Alumni Sans Collegiate One SC") is derived from the same Glyphs sources, which contain extensive `.sc` (small caps) glyphs and OpenType `smcp`/`c2sc` features. However, the SC fonts were not pre-built in the upstream repository. At commit `9dc96be`, the only TTF files present are the non-SC variants under `fonts/ttf/`.
+
+The METADATA.pb `source.files` mapping references `fonts/ttf/AlumniSansCollegiateOneSC-Regular.ttf` and `fonts/ttf/AlumniSansCollegiateOneSC-Italic.ttf`, but these files **do not exist** at the referenced commit in the upstream repo. The SC fonts were produced during the onboarding process (likely by gftools-packager with a custom build configuration), not pulled directly from the upstream repo.
+
+There is no override `config.yaml` in the google/fonts family directory (`ofl/alumnisanscollegiateonesc/`).
+
+### What would be needed
+
+To rebuild the SC variant from sources, a separate config.yaml would be needed that:
+- References the same Glyphs sources (`AlumniSansCollegiate.glyphs` and `AlumniSansCollegiate-Italic.glyphs`)
+- Sets `familyName: "Alumni Sans Collegiate One SC"` or uses appropriate small-caps extraction settings
+- Configures the build to produce only the small-caps subset of glyphs
+
+## Additional Notes
+
+- **Sibling family**: This repo also hosts "Alumni Sans Collegiate One" (non-SC), which lives at `ofl/alumnisanscollegiateone/`. The non-SC family was onboarded earlier (2022-04-09) via PR #4855, while the SC variant was added later (2024-05-27) via PR #7769.
+- **Same commit**: Both families reference the same upstream commit `9dc96be`, which is the only commit in the repository.
+- **Source file mapping issue**: The `source.files` entries for the SC TTFs point to paths that don't exist in the upstream repo. The fonts were generated during onboarding, not extracted from pre-built files.
+- **Designer**: Robert Leuschke (Robert E. Leuschke), with contributions from Viviana Monsalve who made the single upstream commit.
+- The `config_yaml` field in METADATA.pb points to a config that builds the wrong family (non-SC). This needs correction -- either an override config.yaml for the SC build, or the `config_yaml` field should be removed/corrected.
+
+## Conclusion
+
+**Confidence: HIGH** for repository URL and commit hash. The upstream repo URL and commit are well-documented and unambiguous (single-commit repo, explicitly referenced in onboarding).
+
+**Status: missing_config** -- The `config_yaml` field in METADATA.pb (`sources/config.yml`) points to a config that builds the non-SC family "Alumni Sans Collegiate One", not the SC variant. An override `config.yaml` specific to the SC build would need to be created in the google/fonts family directory to properly rebuild this family from sources. The `source.files` TTF paths also don't exist in the upstream repo at the referenced commit.
--- /dev/null
+# Alumni Sans Inline One
+
+**Date investigated**: 2026-03-03
+**Model**: Claude Opus 4.6
+**Status**: complete
+**Designer**: Robert Leuschke
+**METADATA.pb path**: `ofl/alumnisansinlineone/METADATA.pb`
+
+## Source Data
+| Field | Value |
+|-------|-------|
+| Repository URL | https://github.com/googlefonts/alumni-sans-inline |
+| Commit | `81ea544e0ce487475c75df9545cd3df946c7ba26` |
+| Config YAML | `sources/config.yml` |
+| Branch | `main` |
+
+## How the Repository URL Was Found
+
+The repository URL `https://github.com/googlefonts/alumni-sans-inline` is recorded in the METADATA.pb `source` block. It was also referenced in the original onboarding commit message in google/fonts (`d2ed457c9`, PR #4331, 2022-02-25), which explicitly states the fonts were "taken from the upstream repo https://github.com/googlefonts/alumni-sans-inline". The copyright strings in METADATA.pb also reference this repository. The upstream repo is cached at `googlefonts/alumni-sans-inline` and its remote URL matches.
+
+## How the Commit Hash Was Identified
+
+The commit hash `81ea544e0ce487475c75df9545cd3df946c7ba26` is recorded in the METADATA.pb `source` block. It was explicitly referenced in the onboarding commit message (google/fonts commit `d2ed457c9`, PR #4331): "at commit https://github.com/googlefonts/alumni-sans-inline/commit/81ea544e0ce487475c75df9545cd3df946c7ba26".
+
+Verification confirms this is correct:
+- The upstream repo has only a single commit (`81ea544`), so there is no ambiguity.
+- The binary TTF files in google/fonts are byte-identical (matching MD5 hashes) to those at this commit in the upstream repo:
+ - `AlumniSansInlineOne-Regular.ttf`: `abc90e65e2f85dda81124fa349d12f95`
+ - `AlumniSansInlineOne-Italic.ttf`: `ac82364c08ebed38f107259b968f840a`
+- The onboarding date (2022-02-25) and commit date (2022-02-24) are consistent.
+
+## How Config YAML Was Resolved
+
+The config file `sources/config.yml` exists at the referenced commit in the upstream repo. It contains a valid gftools-builder configuration:
+
+```yaml
+sources:
+ - AlumniSansInline.glyphs
+ - AlumniSansInline-Italic.glyphs
+familyName: "Alumni Sans Inline One"
+buildVariable: false
+```
+
+The `config_yaml: "sources/config.yml"` field in METADATA.pb correctly points to this file. No override config.yaml exists in the google/fonts family directory.
+
+## Conclusion
+
+This family's source metadata is fully complete and verified. The upstream repository has a single commit which matches the referenced hash. Binary files are byte-identical between google/fonts and the upstream repo. The config.yml is present in the upstream repo at the documented path. No changes are needed.
--- /dev/null
+# Alumni Sans Pinstripe
+
+**Date investigated**: 2026-03-03
+**Model**: Claude Opus 4.6
+**Status**: complete
+**Designer**: Robert Leuschke
+**METADATA.pb path**: `ofl/alumnisanspinstripe/METADATA.pb`
+
+## Source Data
+
+| Field | Value |
+|-------|-------|
+| Repository URL | https://github.com/googlefonts/alumni-sans-pinstripe |
+| Commit | `26cf834f2eca219b017478be9ea1387c78756e78` |
+| Config YAML | `sources/config.yml` |
+| Branch | `main` |
+
+## How the Repository URL Was Found
+
+The repository URL `https://github.com/googlefonts/alumni-sans-pinstripe` was already present in the METADATA.pb `source {}` block. It matches the copyright notice in the font files ("Copyright 2014 The Alumni Sans Pinstripe Project Authors (https://github.com/googlefonts/alumni-sans-pinstripe)") and the remote URL of the cached upstream repo. The repository exists and is accessible.
+
+## How the Commit Hash Was Identified
+
+The commit hash `26cf834f2eca219b017478be9ea1387c78756e78` was already recorded in METADATA.pb and is confirmed by multiple sources:
+
+1. **google/fonts commit message**: The onboarding commit `9d68dcf8e` (PR #4759, merged 2022-06-17) explicitly states: "Alumni Sans Pinstripe Version 1.010; ttfautohint (v1.8.4.7-5d5b) taken from the upstream repo https://github.com/googlefonts/alumni-sans-pinstripe at commit https://github.com/googlefonts/alumni-sans-pinstripe/commit/26cf834f2eca219b017478be9ea1387c78756e78."
+2. **Single-commit repo**: The upstream repository contains only one commit (`26cf834`), authored by Viviana Monsalve on 2022-06-09 with message "v1.010 fonts added". There are no subsequent commits that could cause ambiguity.
+3. **Timeline**: The upstream commit (2022-06-09) predates the google/fonts merge (2022-06-17) by 8 days, consistent with the onboarding workflow.
+4. **Binary file sizes match**: The TTF files at this commit are 110,624 bytes (Italic) and 104,716 bytes (Regular), matching the files in `ofl/alumnisanspinstripe/`.
+
+## How Config YAML Was Resolved
+
+The config file `sources/config.yml` exists in the upstream repository at the referenced commit. Its contents:
+
+```yaml
+sources:
+ - AlumniSansPinstripe.glyphs
+ - AlumniSansPinstripe-Italic.glyphs
+familyName: "Alumni Sans Pinstripe"
+buildVariable: false
+```
+
+The METADATA.pb correctly references this as `config_yaml: "sources/config.yml"`. The source files (`.glyphs`) are relative to the `sources/` directory and are present at the commit. No override config.yaml exists in the google/fonts family directory, and none is needed since the upstream config is complete.
+
+## Conclusion
+
+This family's source metadata is fully complete and verified. The repository URL, commit hash, branch, and config_yaml path are all correctly recorded in METADATA.pb. The upstream repository is a single-commit repo created by Viviana Monsalve, onboarded via gftools-packager in PR #4759, with the commit hash explicitly confirmed in the google/fonts commit message. No corrections are needed.
--- /dev/null
+# Alumni Sans SC
+
+**Date investigated**: 2026-03-03
+**Model**: Claude Opus 4.6
+**Status**: needs_correction
+**Designer**: Robert Leuschke
+**METADATA.pb path**: `ofl/alumnisanssc/METADATA.pb`
+
+## Source Data
+
+| Field | Value |
+|-------|-------|
+| Repository URL | https://github.com/googlefonts/alumni |
+| Commit | `44a7998fa2bfa1b3e119983cdc565dd7f0f03bda` |
+| Config YAML | `sources/config.yml` (INCORRECT for SC variant -- see below) |
+| Branch | master |
+
+## How the Repository URL Was Found
+
+The repository URL `https://github.com/googlefonts/alumni` was set in the METADATA.pb since the original onboarding commit `521d1cdf` by Simon Cozens on 2024-05-27. The google/fonts commit message explicitly states: "Taken from the upstream repo https://github.com/googlefonts/alumni at commit https://github.com/googlefonts/alumni/commit/44a7998fa2bfa1b3e119983cdc565dd7f0f03bda." The repo is verified and cached at `googlefonts/alumni`.
+
+This repository is shared with the non-SC "Alumni Sans" family (`ofl/alumnisans/`), which uses the same repo URL and commit hash.
+
+## How the Commit Hash Was Identified
+
+The commit hash `44a7998fa2bfa1b3e119983cdc565dd7f0f03bda` was recorded in the onboarding commit message and in the METADATA.pb source block since the initial onboarding (PR #7768, merged 2024-06-19). The commit exists in the upstream repo and is the HEAD (and only) commit on the master branch, authored by Viviana Monsalve on 2021-12-18 with message "one blank line added to the OFL."
+
+The commit hash is correct -- it represents the state of the upstream repo from which the SC fonts were built.
+
+## How Config YAML Was Resolved
+
+**The `config_yaml: "sources/config.yml"` field is INCORRECT for the Alumni Sans SC family.**
+
+The upstream `sources/config.yml` at the referenced commit defines:
+- `familyName: "Alumni Sans"` (NOT "Alumni Sans SC")
+- Output files: `AlumniSans[wght].ttf` and `AlumniSans-Italic[wght].ttf` (NOT AlumniSansSC)
+- Sources: `AlumniSans.glyphs` and `AlumniSans-Italic.glyphs`
+
+This config correctly builds the non-SC "Alumni Sans" family, but does NOT produce the "Alumni Sans SC" variant.
+
+The `config_yaml` field was added by the "Batch 1/4" commit (`19cdcec5`, 2025-03-31) which ported data from fontc_crater's targets.json. The fontc_crater targets list has this config_yaml for the alumni repo, but it is only valid for building the non-SC "Alumni Sans" family. The same config_yaml was applied to the SC variant in error.
+
+### How the SC Fonts Were Actually Built
+
+PR #7768 includes a comment from Simon Cozens stating: "This is a serious PR, but it is also a test of the **small caps builder** and the `gftools-packager --build-from-source` option."
+
+This confirms the AlumniSansSC binaries were generated using gftools-packager's `--build-from-source` flag with its built-in small caps builder feature. The small caps builder takes the regular Alumni Sans sources (which contain `.sc` glyphs and `smcp`/`c2sc` OpenType features) and produces a separate "Small Caps" font family where the small caps glyphs replace the default lowercase forms.
+
+### Incorrect source_file Paths
+
+The METADATA.pb source block references:
+- `source_file: "fonts/variable/AlumniSansSC[wght].ttf"`
+- `source_file: "fonts/variable/AlumniSansSC-Italic[wght].ttf"`
+
+These file paths **do not exist** in the upstream repository at the referenced commit (or at any commit). The upstream repo only contains `fonts/variable/AlumniSans[wght].ttf` and `fonts/variable/AlumniSans-Italic[wght].ttf`. The SC binaries were built at packaging time by gftools-packager, not pulled from pre-existing files in the upstream repo.
+
+## Issues Found
+
+1. **`config_yaml` is incorrect**: `sources/config.yml` builds "Alumni Sans", not "Alumni Sans SC". This config cannot be used to reproduce the SC fonts. The SC fonts require a separate build configuration that invokes the small caps builder.
+
+2. **`source_file` paths are invalid**: The referenced paths (`fonts/variable/AlumniSansSC[wght].ttf` and `AlumniSansSC-Italic[wght].ttf`) do not exist in the upstream repository. The fonts were built from source at packaging time, not copied from pre-built binaries.
+
+3. **No override config.yaml exists** in the google/fonts family directory to build the SC variant.
+
+## Conclusion
+
+The repository URL and commit hash are correct -- the SC fonts were built from the same upstream sources as the non-SC "Alumni Sans" at commit `44a7998`. However, the current METADATA.pb has two problems:
+
+1. The `config_yaml: "sources/config.yml"` field (added by the Batch 1/4 commit) is incorrect for this family. That config only builds the non-SC variant. It should either be removed or replaced with a config that produces the SC variant.
+
+2. The `source_file` paths reference files that do not exist in the upstream repo.
+
+To properly fix this, an override `config.yaml` would need to be created in the google/fonts family directory that uses gftools-builder's small caps builder to produce `AlumniSansSC[wght].ttf` and `AlumniSansSC-Italic[wght].ttf` from the upstream `.glyphs` sources. The `config_yaml` field would then be removed from METADATA.pb (since google-fonts-sources auto-detects local overrides).
+
+This family needs correction. The status is **needs_correction** due to the incorrect config_yaml and invalid source_file paths.
--- /dev/null
+# Amarna
+
+**Status**: `complete`
+**Date**: 2026-02-25
+**Designer**: Ishtār van Looy
+**License**: OFL
+**METADATA.pb**: `ofl/amarna/METADATA.pb`
+
+## Data
+
+| Field | Value |
+|-------|-------|
+| Repository URL | https://github.com/ijvanl/Amarna |
+| Commit | `22819bafba78c7f3e4644b6f68683773180a5965` |
+| Config YAML | `sources/config.yaml` |
+| Branch | `main` |
+
+## Methodology
+
+### Repository URL
+Pre-existing in METADATA.pb `source { repository_url }` field.
+
+### Commit Hash
+Pre-existing in METADATA.pb `source { commit }` field.
+- Commit date: 2025-11-20 03:54:11 +1100
+- Commit message: "Merge pull request #1 from emmamarichal/main"
+
+### Config YAML
+Found `sources/config.yaml` in upstream repository at the recorded commit hash.
+
+## Evidence
+
+### METADATA.pb source block
+- `repository_url`: `https://github.com/ijvanl/Amarna`
+- `commit`: `22819bafba78c7f3e4644b6f68683773180a5965`
+- `config_yaml`: `sources/config.yaml`
+
+### google/fonts history
+- Last font modification: `bde8256aca40`
+- Date: 2025-11-20 10:32:09 +0100
+- Subject: "Amarna: Version 1.003 added"
+
+### Upstream repo cache
+- Cached at: `ijvanl/Amarna`
+- Commit `22819bafba78` verified ✓
+
+## Confidence
+
+**High**: URL pre-existing in METADATA.pb; commit pre-existing in METADATA.pb
--- /dev/null
+# Amatic SC
+
+**Date investigated**: 2026-03-03
+**Model**: Claude Opus 4.6
+**Status**: complete
+**Designer**: Vernon Adams, Ben Nathan, Thomas Jockin
+**METADATA.pb path**: `ofl/amaticsc/METADATA.pb`
+
+## Source Data
+| Field | Value |
+|-------|-------|
+| Repository URL | https://github.com/googlefonts/AmaticSC |
+| Commit | `308846136d2dcfb6aef2160d7e927698cdaf9c05` |
+| Config YAML | `sources/config.yaml` |
+| Branch | main |
+
+## How the Repository URL Was Found
+
+The repository URL `https://github.com/googlefonts/AmaticSC` was already present in METADATA.pb. It was added by Simon Cozens in commit `5f2b22f48` ("Update upstreams", 2023-12-14) as part of a bulk update of upstream source blocks. The URL is also referenced in the original google/fonts onboarding commit `81e5d4b23` (PR #1271, by Marc Foley, 2017-10-31): "Taken from the upstream repo, https://github.com/googlefonts/AmaticSC". The copyright string in the font files confirms this URL. The remote URL of the cached repo matches.
+
+## How the Commit Hash Was Identified
+
+The commit `308846136d2dcfb6aef2160d7e927698cdaf9c05` was ported from the fontc_crater targets list in the Batch 1/4 commit (`19cdcec59`, 2025-03-31) by @felipesanches.
+
+This commit is the HEAD of the upstream repo's main branch. It is a merge commit for PR #18 ("add sources/config.yaml"), authored by @felipesanches on 2025-02-24. This is NOT the original onboarding commit -- the original onboarding into google/fonts was done in 2017 (PR #1271) without recording a specific upstream commit hash.
+
+However, this commit is the correct reference for fontc_crater purposes because:
+1. The binary font files (`fonts/ttf/AmaticSC-Bold.ttf` and `fonts/ttf/AmaticSC-Regular.ttf`) at this commit are byte-identical to the files currently in `ofl/amaticsc/` in google/fonts (both Bold at 156,180 bytes and Regular at 151,624 bytes).
+2. The `sources/config.yaml` file (needed for gftools-builder / fontc_crater) was added in this commit.
+3. The repo is a shallow clone with only this commit available, which is the latest state of the repo.
+
+Since the repo had no commits between the original onboarding (2017) and the config.yaml addition (2025), this commit correctly represents the source state.
+
+## How Config YAML Was Resolved
+
+The `sources/config.yaml` file exists in the upstream repo at the referenced commit. It was added by @felipesanches in PR #18 (merged 2025-02-24). The config is minimal:
+
+```yaml
+sources:
+ - AmaticSC.glyphs
+```
+
+This references the Glyphs source file at `sources/AmaticSC.glyphs`, which exists at the referenced commit. The `config_yaml` field in METADATA.pb correctly points to `sources/config.yaml`. No override config.yaml exists in the google/fonts family directory.
+
+## Conclusion
+
+The source metadata for Amatic SC is complete and correct. The repository URL is confirmed through multiple sources (copyright string, PR history, commit messages). The commit hash points to the latest state of the upstream repo, which includes both the original source files and the config.yaml needed for fontc_crater. The binary fonts at this commit match those in google/fonts byte-for-byte. Status: **complete**.
--- /dev/null
+# Amiri
+
+**Status**: `complete`
+**Date**: 2026-02-25
+**Designer**: Khaled Hosny, Sebastian Kosch
+**License**: OFL
+**METADATA.pb**: `ofl/amiri/METADATA.pb`
+
+## Data
+
+| Field | Value |
+|-------|-------|
+| Repository URL | https://github.com/aliftype/amiri.git |
+| Commit | `04d40ee68cc6b8cb6870eca81a8a7451165aa95a` |
+| Config YAML | Override in google/fonts family directory |
+| Branch | `main` |
+
+## Methodology
+
+### Repository URL
+Pre-existing in METADATA.pb `source { repository_url }` field.
+
+### Commit Hash
+Pre-existing in METADATA.pb `source { commit }` field.
+
+### Config YAML
+Override `config.yaml` exists in the google/fonts family directory. Per policy, `config_yaml` field is omitted from METADATA.pb.
+
+## Evidence
+
+### METADATA.pb source block
+- `repository_url`: `https://github.com/aliftype/amiri.git`
+- `commit`: `04d40ee68cc6b8cb6870eca81a8a7451165aa95a`
+- `config_yaml`: `—`
+
+### google/fonts history
+- Last font modification: `39d11bc31303`
+- Date: 2025-05-16 13:47:05 +0200
+- Subject: "Amiri: Version 1.002 added"
+
+### Override config
+Override `config.yaml` exists in `ofl/amiri/config.yaml`.
+
+## Confidence
+
+**High**: URL pre-existing in METADATA.pb; commit pre-existing in METADATA.pb
--- /dev/null
+# Amiri Quran
+
+**Date investigated**: 2026-03-03
+**Model**: Claude Opus 4.6
+**Status**: complete
+**Designer**: Khaled Hosny, Sebastian Kosch
+**METADATA.pb path**: `ofl/amiriquran/METADATA.pb`
+
+## Source Data
+
+| Field | Value |
+|-------|-------|
+| Repository URL | https://github.com/aliftype/amiri |
+| Commit | `480bb746e99ea700bb0d6b4dbf96302d58192103` |
+| Config YAML | override config.yaml in google/fonts |
+| Branch | main |
+
+## How the Repository URL Was Found
+
+The repository URL `https://github.com/aliftype/amiri` is recorded in the METADATA.pb `source {}` block. The copyright notice in METADATA.pb also references this URL: "Copyright 2010-2022 The Amiri Project Authors (https://github.com/aliftype/amiri)." The cached upstream repo at `aliftype/amiri` confirms the remote matches this URL.
+
+Note: Amiri Quran is part of the broader Amiri font family project. It shares the same upstream repository with the Amiri font family. The font is built from the same `.glyphspackage` source but uses a custom build process involving `scripts/mkquran.py` to produce the Quran-specific variant.
+
+## How the Commit Hash Was Identified
+
+The commit `480bb746e99ea700bb0d6b4dbf96302d58192103` is already recorded in METADATA.pb. Verification confirms:
+
+1. **Commit exists in upstream repo**: Yes, authored by Khaled Hosny on 2025-06-13, with message "1.003". It updated `NEWS.md` for the 1.003 release.
+2. **Tag alignment**: This commit is the target of the annotated tag `1.003` in the upstream repo (`git rev-parse "1.003^{commit}"` returns the same hash).
+3. **Archive URL consistency**: The archive URL points to `Amiri-1.003.zip`, consistent with the 1.003 release.
+4. **google/fonts history**: The font was initially added at this commit via commit `4088c1fa7` by Emma Marichal (2025-07-16), with commit message "Amiri Quran: Version 1.002 added" -- the title says "1.002" but the body explicitly references the 1.003 commit hash. This was a minor error in the commit message title. A follow-up commit `3c5672f8a` ("push version 1.003") corrected the archive_url from 1.002 to 1.003 and fixed the filename. A further commit `087c433c9` corrected the `files {}` paths to use the `Amiri-1.003/` prefix matching the archive structure.
+5. **Pre-built binary**: The binary `fonts/AmiriQuran.ttf` exists at this commit in the upstream repo. The METADATA.pb uses `archive_url` to pull the pre-built binary from the GitHub release zip rather than building from source.
+
+The commit hash is correct and matches the 1.003 release tag.
+
+## How Config YAML Was Resolved
+
+The upstream repository does **not** have a `config.yaml` file at the referenced commit (or at HEAD). The Amiri project uses a custom build system via `Makefile` and `scripts/build.py` (using `ufo2ft` directly) rather than gftools-builder.
+
+A local override `config.yaml` was added to `ofl/amiriquran/` in the google/fonts repository by commit `f6c68379a` (2026-02-16, "Add override config.yaml for 50 font families"). The override contains:
+
+```yaml
+sources:
+ - sources/Amiri.glyphspackage
+familyName: Amiri Quran
+buildStatic: true
+buildOTF: false
+```
+
+This override points to the `.glyphspackage` source file that exists in the upstream repo at the referenced commit. Since the override config.yaml exists locally in google/fonts, no `config_yaml` field is needed in METADATA.pb (google-fonts-sources auto-detects local overrides).
+
+**Important caveat**: The override config may not produce an identical binary to the original. The upstream project uses a highly customized build pipeline (`scripts/build.py` for initial compilation + `scripts/mkquran.py` for Quran-specific processing). The override config.yaml points gftools-builder at the `.glyphspackage` source, but gftools-builder will not replicate the custom Quran-specific processing steps (e.g., the color glyph removal, Quran-specific mark positioning, etc.). The binary currently served from google/fonts was taken from the pre-built release archive, not built from source via gftools-builder.
+
+## Conclusion
+
+The source metadata for Amiri Quran is **complete**. The repository URL is correct, the commit hash matches the 1.003 release tag, and a local override config.yaml exists in google/fonts. The font binary was sourced from the upstream GitHub release archive (pre-built), not compiled via gftools-builder. The override config.yaml enables fontc_crater discovery but may not reproduce the exact same binary due to the project's custom build pipeline.
--- /dev/null
+# Amita
+
+**Status**: `complete`
+**Date**: 2026-02-25
+**Designer**: Eduardo Tunni, Brian Bonislawsky
+**License**: OFL
+**METADATA.pb**: `ofl/amita/METADATA.pb`
+
+## Data
+
+| Field | Value |
+|-------|-------|
+| Repository URL | https://github.com/etunni/Amita |
+| Commit | `92680c07f01285a23744cda1190690c5c7f3f73c` |
+| Config YAML | `sources/config.yaml` |
+
+## Methodology
+
+### Repository URL
+Pre-existing in METADATA.pb `source { repository_url }` field.
+
+### Commit Hash
+Pre-existing in METADATA.pb `source { commit }` field.
+- Commit date: 2023-02-01 13:08:50 -0300
+- Commit message: "Merge pull request #7 from emmamarichal/master"
+
+### Config YAML
+Found `sources/config.yaml` in upstream repository at the recorded commit hash.
+
+## Evidence
+
+### METADATA.pb source block
+- `repository_url`: `https://github.com/etunni/Amita`
+- `commit`: `92680c07f01285a23744cda1190690c5c7f3f73c`
+- `config_yaml`: `sources/config.yaml`
+
+### google/fonts history
+- Last font modification: `c7beb6552615`
+- Date: 2017-08-07 21:45:27 +0100
+- Subject: "hotfix-amita: v1.004 added (#762)"
+
+### Upstream repo cache
+- Cached at: `etunni/Amita`
+- Commit `92680c07f012` verified ✓
+
+## Confidence
+
+**High**: URL pre-existing in METADATA.pb; commit pre-existing in METADATA.pb
--- /dev/null
+# Amstelvar Alpha
+
+**Date investigated**: 2026-03-03
+**Model**: Claude Opus 4.6
+**Status**: needs_investigation
+**Designer**: David Berlow
+**METADATA.pb path**: `ofl/amstelvaralpha/METADATA.pb` (does not exist)
+
+## Source Data
+| Field | Value |
+|-------|-------|
+| Repository URL | `https://github.com/googlefonts/amstelvar` |
+| Commit | `b490f475bb83` (last font update before google/fonts PR #1184 merge) |
+| Config YAML | -- |
+| Branch | main |
+
+## Context
+
+Amstelvar Alpha is an **Early Access** family in google/fonts. It has an `EARLY_ACCESS.category` file but **no METADATA.pb** file at all. The family was never fully promoted to the Google Fonts catalog. The directory contains only:
+
+- `AmstelvarAlpha-VF.ttf` (128,312 bytes)
+- `DESCRIPTION.en_us.html`
+- `EARLY_ACCESS.category` (content: "Serif")
+- `OFL.txt`
+
+The upstream repo is archived and the font project has evolved significantly beyond the "Alpha" version that was served through Early Access.
+
+## How the Repository URL Was Found
+
+The `DESCRIPTION.en_us.html` file explicitly links to `https://github.com/TypeNetwork/fb-Amstelvar`. Using the GitHub API, this URL now redirects to `https://github.com/googlefonts/amstelvar` (the repo was transferred from the TypeNetwork organization to googlefonts). The repo is currently **archived**.
+
+The upstream repo's `METADATA.yml` also confirms: `repository url: https://github.com/typenetwork/Amstelvar`.
+
+## How the Commit Hash Was Identified
+
+The google/fonts history for `ofl/amstelvaralpha/` shows exactly 4 commits:
+
+1. `d95e5ec65` -- "Add Amstelvar to Early Access (#655)" -- merged 2017-03-28 by davelab6
+2. `c0899f11c` -- "ofl/amstelvaralpha/AmstelvarAlpha-VF.ttf Updated" (squash of PR #1184)
+3. `0eb39d391` -- "ofl/amstelvaralpha/AmstelvarAlpha-VF.ttf Updated (#1184)" -- merged 2017-08-30 by davelab6
+4. `6bda16478` -- "Format HTML with new html formatter" (only touched DESCRIPTION.en_us.html)
+
+**Initial onboarding (PR #655)**: The font binary had git blob SHA `fec678154d` and size 106,184 bytes. This exactly matches the `fonts/AmstelvarAlpha-VF.ttf` file at upstream commit `2357d7bf4d51` (2017-03-27, "Delete AmstelvarAlpha-VF-2017-01-23.ttf"). The font file was a pre-compiled binary checked into the upstream repo, not built via any CI/config pipeline.
+
+**Update (PR #1184)**: The font binary was updated to blob SHA `11da618ab4` and size 128,312 bytes. This exactly matches `fonts/AmstelvarAlpha-VF.ttf` at upstream commit `b490f475bb83` (2017-08-10, "build default version without dollar point jump"). This was the last commit to touch the font file before the google/fonts merge on 2017-08-30.
+
+Both blob SHA and file size matches are exact, providing high confidence in the commit identification.
+
+## How Config YAML Was Resolved
+
+There is **no `config.yaml`** anywhere in the upstream repository (neither at the onboarding-era commits nor at the current HEAD). The font was built using a custom `fontmake` + `fonttools varLib` pipeline via a shell script (`scripts/build.sh`):
+
+```bash
+fontmake -o ttf-interpolatable -m AmstelvarAlpha.designspace --no-production-names
+fonttools varLib AmstelvarAlpha.designspace
+mv AmstelvarAlpha-VF.ttf ../fonts/AmstelvarAlpha-VF.ttf
+```
+
+The sources at the onboarding commit (`2357d7bf4d51`) were UFO files organized in two directories:
+- `sources/1-drawing/` -- 26 `.ufo` masters plus `AmstelvarAlpha.designspace` and `AmstelvarAlpha.fea`
+- `sources/2-build/` -- 29 `.ufo` masters plus `AmstelvarAlpha.fea`
+
+At the update commit (`b490f475bb83`), the structure had evolved to include a `sources/BETA/` directory with additional axis combinations.
+
+The project uses `.designspace` + `.ufo` sources, which are theoretically compatible with gftools-builder, but the build process was custom and predates gftools-builder entirely (2017). An override `config.yaml` could potentially be created, but given the complexity of the designspace (many parametric axes) and the fact that the project has evolved far beyond this alpha version, it may not be practical.
+
+## Conclusion
+
+Amstelvar Alpha is an **Early Access** family with no METADATA.pb. The upstream repository is `https://github.com/googlefonts/amstelvar` (archived, formerly `TypeNetwork/fb-Amstelvar`). The font binary currently in google/fonts was taken from upstream commit `b490f475bb83` (2017-08-10), confirmed by exact blob SHA match.
+
+Key considerations:
+- **No METADATA.pb exists** -- this is an Early Access family that was never fully onboarded to the catalog
+- **No config.yaml** -- the font was built with custom fontmake scripts, not gftools-builder
+- **Repo is archived** -- the upstream repository has been archived and is no longer actively developed
+- **Pre-compiled binary** -- the font was checked into the upstream repo as a pre-built binary, not generated through a reproducible build pipeline
+- The repo has since evolved to a non-Alpha version ("Amstelvar" proper) with significantly different sources and more refined designspaces, but this newer version has not been pushed to google/fonts
+
+Creating a source block would require first creating a METADATA.pb for this family. Given the Early Access status and archived upstream, this family may be a candidate for delisting rather than full metadata enrichment.
--- /dev/null
+# Anaheim
+
+**Status**: `complete`
+**Date**: 2026-02-25
+**Designer**: Vernon Adams
+**License**: OFL
+**METADATA.pb**: `ofl/anaheim/METADATA.pb`
+
+## Data
+
+| Field | Value |
+|-------|-------|
+| Repository URL | https://github.com/googlefonts/anaheimFont |
+| Commit | `2b346ea7993c2e4eee6224d4bd2c143cc65b54d9` |
+| Config YAML | `sources/config.yaml` |
+| Branch | `main` |
+
+## Methodology
+
+### Repository URL
+Pre-existing in METADATA.pb `source { repository_url }` field.
+
+### Commit Hash
+Pre-existing in METADATA.pb `source { commit }` field.
+- Commit date: 2024-04-18 11:02:14 +0200
+- Commit message: "Merge pull request #6 from Fonthausen/master"
+
+### Config YAML
+Found `sources/config.yaml` in upstream repository at the recorded commit hash.
+
+## Evidence
+
+### METADATA.pb source block
+- `repository_url`: `https://github.com/googlefonts/anaheimFont`
+- `commit`: `2b346ea7993c2e4eee6224d4bd2c143cc65b54d9`
+- `config_yaml`: `—`
+
+### google/fonts history
+- Last font modification: `d22fe91bdad0`
+- Date: 2024-04-24 14:14:13 +0200
+- Subject: "remove statics"
+
+### Upstream repo cache
+- Cached at: `googlefonts/anaheimFont`
+- Commit `2b346ea7993c` verified ✓
+
+## Confidence
+
+**High**: URL pre-existing in METADATA.pb; commit pre-existing in METADATA.pb
--- /dev/null
+# Ancizar Sans
+
+**Date investigated**: 2026-03-03
+**Model**: Claude Opus 4.6
+**Status**: complete
+**Designer**: Universidad Nacional de Colombia (UNAL), Cesar Puertas, Viviana Monsalve, Julian Moncada
+**METADATA.pb path**: `ofl/ancizarsans/METADATA.pb`
+
+## Source Data
+
+| Field | Value |
+|-------|-------|
+| Repository URL | https://github.com/UNAL-OMD/UNAL-Ancizar |
+| Commit | `54a5aa2153b4485ff2710612d47183c346e6b842` |
+| Config YAML | `sources/config-sans.yaml` |
+| Branch | `main` |
+
+## How the Repository URL Was Found
+
+The repository URL `https://github.com/UNAL-OMD/UNAL-Ancizar` was already recorded in the METADATA.pb source block. It is also referenced in the copyright string of the font files and in the google/fonts commit message (`544bd4e`) that initially added the family:
+
+> Taken from the upstream repo https://github.com/UNAL-OMD/UNAL-Ancizar at commit https://github.com/UNAL-OMD/UNAL-Ancizar/commit/54a5aa2153b4485ff2710612d47183c346e6b842.
+
+The repository is cached locally at `upstream_repos/fontc_crater_cache/UNAL-OMD/UNAL-Ancizar` and is accessible.
+
+Note: This is a shared repository with the sibling family "Ancizar Serif", which uses a separate config (`sources/config-serif.yaml`).
+
+## How the Commit Hash Was Identified
+
+The commit `54a5aa2153b4485ff2710612d47183c346e6b842` was explicitly referenced in the google/fonts onboarding commit (`544bd4e`, authored by Yanone on 2025-04-16). This commit message states the fonts were taken from the upstream repo at that exact commit.
+
+**Verification**: The git blob hashes of the binary files are identical between google/fonts and the upstream repo at this commit:
+
+- `AncizarSans[wght].ttf`: blob `ddfd6550ee6f9980d4945384a03ed5fee68d02a7` (172,192 bytes)
+- `AncizarSans-Italic[wght].ttf`: blob `d226c7a1fae1fe37d35c1a41975dc3f3bfbb56e7` (178,372 bytes)
+
+The upstream commit message is "New Sans binaries" (2025-04-16) by Yanone, and the google/fonts commit was made the same day, confirming the onboarder (Yanone) updated the upstream binaries and then immediately onboarded them.
+
+The upstream `main` branch has since progressed past this commit (current HEAD: `c4303cb`, "Added RFN"), but the subsequent commits are related to Serif fixes and an RFN addition, not Sans changes.
+
+## How Config YAML Was Resolved
+
+The file `sources/config-sans.yaml` exists in the upstream repository at the referenced commit. Its contents:
+
+```yaml
+sources:
+ - AncizarSans.glyphs
+ - AncizarSans-Italic.glyphs
+buildVariable: true
+buildStatic: true
+buildTTF: false
+buildOTF: false
+buildWebfont: false
+buildSmallCap: false
+```
+
+This is a valid gftools-builder configuration referencing the `.glyphs` source files for the Sans variant. The `config_yaml` field in METADATA.pb correctly points to this file. No local override config.yaml exists in the google/fonts family directory.
+
+The `config_yaml: "sources/config-sans.yaml"` field was added in a subsequent commit (`6a0d06b`, 2025-05-22) by Felipe Sanches as part of PR #9350 to enrich source metadata.
+
+## google/fonts Commit History
+
+1. `544bd4e` (2025-04-16, Yanone): Initial onboarding - "Ancizar Sans: Version 8.100 added" (resolves #9095)
+2. `cdcc68c`: Update OFL.txt
+3. `6a0d06b` (2025-05-22, Felipe Sanches): Added `config_yaml` field to source block (PR #9350)
+4. `264e439` (2025-05-22, Dave Crossland): Added `display_name: "UNAL Ancizar Sans"` to METADATA.pb
+
+## Conclusion
+
+The source metadata for Ancizar Sans is **complete**. The repository URL, commit hash, config YAML path, and branch are all correctly recorded in METADATA.pb. The commit hash has been verified by comparing binary blob hashes between google/fonts and the upstream repo at the referenced commit -- they are identical. The config file exists at the specified path and contains a valid gftools-builder configuration for the Sans sources. No action is required.
--- /dev/null
+# Ancizar Serif
+
+**Date investigated**: 2026-03-03
+**Model**: Claude Opus 4.6
+**Status**: complete
+**Designer**: Universidad Nacional de Colombia (UNAL), César Puertas, Viviana Monsalve, Julián Moncada
+**METADATA.pb path**: `ofl/ancizarserif/METADATA.pb`
+
+## Source Data
+
+| Field | Value |
+|-------|-------|
+| Repository URL | https://github.com/UNAL-OMD/UNAL-Ancizar |
+| Commit | `063bdd3121fef76289b035226acdc1b4e885f31a` |
+| Config YAML | `sources/config-serif.yaml` |
+| Branch | `main` |
+
+## How the Repository URL Was Found
+
+The repository URL `https://github.com/UNAL-OMD/UNAL-Ancizar` is already recorded in the METADATA.pb `source {}` block. It is also referenced in the onboarding commit message (`599dc5827` in google/fonts), which states: "Taken from the upstream repo https://github.com/UNAL-OMD/UNAL-Ancizar". The copyright string in METADATA.pb also points to this same URL. The cached clone at `UNAL-OMD/UNAL-Ancizar` has `origin` set to this URL. The repository is valid and accessible.
+
+## How the Commit Hash Was Identified
+
+The commit `063bdd3121fef76289b035226acdc1b4e885f31a` is already recorded in the METADATA.pb `source {}` block. It was explicitly referenced in the google/fonts onboarding commit (`599dc5827`, authored by Yanone on 2025-04-16), which states it was taken at this exact commit.
+
+**Binary verification**: SHA-256 hashes of both `AncizarSerif[wght].ttf` and `AncizarSerif-Italic[wght].ttf` in google/fonts match exactly with the files at this commit in the upstream repo:
+- `AncizarSerif[wght].ttf`: `fcc35d7fe2780846344d7187515d483bb69f3d9bcc49c4833a219e4d9109db98`
+- `AncizarSerif-Italic[wght].ttf`: `b30f075790e14795508a42dda7b8f6269509e15a13a4c653b3665662bdfbf45c`
+
+The commit message in the upstream repo is "New Serif binaries" (2025-04-16), authored by Yanone. This is the same author and same date as the google/fonts onboarding commit, confirming the font engineer (Yanone) built the binaries upstream and immediately onboarded them to google/fonts.
+
+One subsequent commit exists in the upstream repo (`c4303cb`, "Added RFN", 2025-04-24), which modifies the Serif binary files (sizes changed slightly). This commit was made after the google/fonts merge (PR #9355 merged 2025-04-17) and was not included in the onboarding.
+
+## How Config YAML Was Resolved
+
+The config file `sources/config-serif.yaml` exists at the referenced commit and is already recorded in METADATA.pb. Its contents:
+
+```yaml
+sources:
+ - AncizarSerif.glyphs
+ - AncizarSerif-Italic.glyphs
+buildVariable: true
+buildStatic: true
+buildTTF: false
+buildOTF: false
+buildWebfont: false
+buildSmallCap: false
+```
+
+The source files (`AncizarSerif.glyphs`, `AncizarSerif-Italic.glyphs`) are confirmed to exist under `sources/` at the referenced commit. No local override config.yaml exists in the google/fonts family directory.
+
+Note: The upstream repo also contains `sources/config-sans.yaml` for the sibling family Ancizar Sans.
+
+## Sibling Family Note
+
+This upstream repo (`UNAL-OMD/UNAL-Ancizar`) serves both **Ancizar Serif** and **Ancizar Sans**. They share the same repo but use different config files (`config-serif.yaml` vs `config-sans.yaml`) and may reference different commits in their respective METADATA.pb files.
+
+## Onboarding Timeline
+
+| Date | Event |
+|------|-------|
+| 2025-04-16 | Yanone committed "New Serif binaries" to upstream (`063bdd3`) |
+| 2025-04-16 | Yanone created onboarding commit in google/fonts (`599dc58`) via gftools-packager |
+| 2025-04-17 | Emma Marichal merged PR #9355 into google/fonts |
+| 2025-04-24 | Upstream commit `c4303cb` ("Added RFN") -- after onboarding, not included |
+| 2025-05-22 | Source block added to METADATA.pb in google/fonts (`e258478`, PR #9355) |
+
+## Conclusion
+
+The source metadata for Ancizar Serif is **complete and correct**. All fields in the METADATA.pb `source {}` block are verified:
+
+- **Repository URL**: Valid, accessible, confirmed by onboarding commit message and copyright string.
+- **Commit hash**: Verified via binary SHA-256 hash comparison -- files match exactly.
+- **Config YAML**: `sources/config-serif.yaml` exists at the referenced commit with valid gftools-builder configuration referencing `.glyphs` sources.
+- **Branch**: `main` (confirmed; the commit is on the main branch).
+
+No corrections needed. Status: **complete**.
--- /dev/null
+# Andada Pro
+
+**Date investigated**: 2026-03-03
+**Model**: Claude Opus 4.6
+**Status**: complete
+**Designer**: Huerta Tipografica, Carolina Giovagnoli
+**METADATA.pb path**: `ofl/andadapro/METADATA.pb`
+
+## Source Data
+| Field | Value |
+|-------|-------|
+| Repository URL | https://github.com/huertatipografica/Andada-Pro |
+| Commit | `a0b87b947003dee6c615809d3eebc8c1334dc575` |
+| Config YAML | `sources/build.yaml` |
+| Branch | `master` |
+
+## How the Repository URL Was Found
+
+The repository URL `https://github.com/huertatipografica/Andada-Pro` was already present in the METADATA.pb source block. It is confirmed by:
+
+1. The gftools-packager commit messages in google/fonts PR #3430 and PR #3693, which both explicitly reference `https://github.com/huertatipografica/Andada-Pro`.
+2. The cached clone at `huertatipografica/Andada-Pro` has its remote origin set to the same URL.
+3. The copyright string in METADATA.pb references `https://github.com/huertatipografica/Andada` (an older repo name), while the actual upstream repo is `Andada-Pro` -- a separate repository for the "Pro" variant.
+
+## How the Commit Hash Was Identified
+
+The commit hash `a0b87b947003dee6c615809d3eebc8c1334dc575` is confirmed through multiple lines of evidence:
+
+1. **gftools-packager message**: The google/fonts commit `4898fbdc` (PR #3693, merged 2021-08-12) explicitly states: "Andada Pro Version 3.003 taken from the upstream repo ... at commit a0b87b947003dee6c615809d3eebc8c1334dc575."
+
+2. **Binary file verification**: The git blob hashes of the variable font files match exactly between the upstream repo at this commit and google/fonts:
+ - `AndadaPro[wght].ttf`: blob `3b23defde4760dcca210a24b2fbc7d4216b83e48` (271,784 bytes) -- matches in both repos
+ - `AndadaPro-Italic[wght].ttf`: blob `3cf0761c5edf9f7169fda099dee0829c33a853bf` (268,388 bytes) -- matches in both repos
+
+3. **Timeline consistency**: The upstream commit is dated 2021-08-05, which is 7 days before the google/fonts merge on 2021-08-12. This is a reasonable gap for review and merging.
+
+4. **Commit is HEAD of master**: This commit (`a0b87b9`) is the latest commit on the master branch at the time it was used. The HEAD is currently detached at this commit in the cached repo, and there are no subsequent commits on master (though there are later commits on the branch after this point, totaling 27+ additional commits since then for version 3.005 and beyond).
+
+### Prior onboarding (PR #3430)
+
+An earlier onboarding attempt in PR #3430 (merged 2021-05-21) used commit `129785ebf91d19507bb77f321d20c0c3114cbea5`. That version was later superseded by PR #3693 with the current commit, which updated the font binaries to reflect ligature fixes and other refinements made by Carolina Giovagnoli between May and August 2021.
+
+## How Config YAML Was Resolved
+
+The `sources/build.yaml` file exists at the referenced commit. Its contents at commit `a0b87b9` are:
+
+```yaml
+sources:
+ - AndadaPro.glyphs
+ - AndadaPro-Italic.glyphs
+axisOrder:
+ - wght
+ - ital
+familyName: Andada Pro
+```
+
+This is a valid gftools-builder configuration referencing two `.glyphs` source files (both present in the `sources/` directory at the same commit). No override config.yaml is needed in google/fonts since the upstream config is present and correct.
+
+## Conclusion
+
+The METADATA.pb source block for Andada Pro is **complete and verified**. All fields are correct:
+
+- The repository URL points to a valid, accessible upstream repo.
+- The commit hash `a0b87b9` matches exactly -- binary font files have identical git blob hashes between upstream and google/fonts.
+- The `sources/build.yaml` config file exists at the referenced commit with valid gftools-builder configuration.
+- The branch is correctly set to `master`.
+- The file mappings (`fonts/variable/AndadaPro[wght].ttf` and `fonts/variable/AndadaPro-Italic[wght].ttf`) are correct.
+
+No changes are needed. Note that there have been 27+ upstream commits since this onboarding (version 3.005 work), which would need separate review if an update is desired.
--- /dev/null
+# Andika
+
+**Status**: `complete`
+**Date**: 2026-02-25
+**Designer**: SIL International
+**License**: OFL
+**METADATA.pb**: `ofl/andika/METADATA.pb`
+
+## Data
+
+| Field | Value |
+|-------|-------|
+| Repository URL | https://github.com/silnrsi/font-andika |
+| Commit | `ca568520c61193de89a795ca676b6978fb435759` |
+| Config YAML | Override in google/fonts family directory |
+| Branch | `master` |
+
+## Methodology
+
+### Repository URL
+Pre-existing in METADATA.pb `source { repository_url }` field.
+
+### Commit Hash
+Pre-existing in METADATA.pb `source { commit }` field.
+- Commit date: 2022-02-09 13:24:22 +0000
+- Commit message: "Set version to 6.101"
+
+### Config YAML
+Override `config.yaml` exists in the google/fonts family directory. Per policy, `config_yaml` field is omitted from METADATA.pb.
+
+## Evidence
+
+### METADATA.pb source block
+- `repository_url`: `https://github.com/silnrsi/font-andika`
+- `commit`: `ca568520c61193de89a795ca676b6978fb435759`
+- `config_yaml`: `—`
+
+### google/fonts history
+- Last font modification: `f5c0a9e31917`
+- Date: 2022-04-21 12:44:00 +0200
+- Subject: "Andika: Version 6.101 added (#4535)"
+
+### Upstream repo cache
+- Cached at: `silnrsi/font-andika`
+- Commit `ca568520c611` verified ✓
+
+### Override config
+Override `config.yaml` exists in `ofl/andika/config.yaml`.
+
+## Confidence
+
+**High**: URL pre-existing in METADATA.pb; commit pre-existing in METADATA.pb
projects / thirdparty / google / fonts.git / commitdiff
