google · felipesanches · May 1, 2026 · Apr 24, 2026 · Apr 24, 2026 · Apr 24, 2026
diff --git a/ofl/abel/config.yaml b/ofl/abel/config.yaml
@@ -0,0 +1,10 @@
+# Legacy upstream sources (.sfd and/or .vfb).
+#
+# gftools-builder does not currently consume these formats. This config
+# is intentional -- it records which source files exist at the pinned
+# upstream commit so a future compatibility layer can pick them up.
+sources:
+  - src/Abel-Regular-TTF.sfd
+  - src/Abel-Regular-TTF.vfb
+  - src/Abel-Regular.vfb
+familyName: Abel
diff --git a/ofl/abel/upstream_info.md b/ofl/abel/upstream_info.md
@@ -51,3 +51,9 @@ The font was likely compiled from the `.sfd` or `.vfb` sources using FontForge o
 1. Can the .sfd sources in the upstream repo be used to reproduce the current font binary in google/fonts? The font was modified directly in google/fonts after onboarding (kerning fix PR #2352, version hotfix PR #741), so the upstream sources likely do not match the current binary.
 2. Should an override config.yaml be created for this family? Given that the sources are in .sfd format (not supported by gftools-builder), this would require conversion to .glyphs or .ufo format first.
 3. The copyright field lists "Matthew Desmond (http://www.madtype.com)" -- the designer credit says "MADType" which is Matthew Desmond's studio. The HTTP URL in the copyright may or may not still be valid.
+
+## Update (2026-04-24) -- Legacy source documentation
+
+**Model**: Claude Opus 4.7 (1M context)
+
+Added an override `config.yaml` in `ofl/abel/` listing the legacy source files (`.sfd`/`.vfb`) present in the upstream repo at the pinned commit `adf2c7e74e`. These formats are not yet supported by gftools-builder; the config serves as documentation for future compatibility work and to distinguish legacy-sourced families from families genuinely missing a build recipe.
diff --git a/ofl/abrilfatface/config.yaml b/ofl/abrilfatface/config.yaml
@@ -0,0 +1,9 @@
+# Legacy upstream sources (.sfd and/or .vfb).
+#
+# gftools-builder does not currently consume these formats. This config
+# is intentional -- it records which source files exist at the pinned
+# upstream commit so a future compatibility layer can pick them up.
+sources:
+  - src/AbrilFatface-Regular-TTF.sfd
+  - src/AbrilFatface-Regular.vfb
+familyName: "Abril Fatface"
diff --git a/ofl/abrilfatface/upstream_info.md b/ofl/abrilfatface/upstream_info.md
@@ -55,3 +55,9 @@ These source formats are not compatible with gftools-builder, which requires `.g
 - Since the source formats (SFD/VFB) are not gftools-builder compatible, is there a plan to convert the sources to a modern format?
 - Should METADATA.pb be updated to include a `source { }` block pointing to this repo, even though it cannot be built with gftools-builder?
 - The font has been in Google Fonts since 2011 and has not been updated since the initial commit. Is an update planned?
+
+## Update (2026-04-24) -- Legacy source documentation
+
+**Model**: Claude Opus 4.7 (1M context)
+
+Added an override `config.yaml` in `ofl/abrilfatface/` listing the legacy source files (`.sfd`/`.vfb`) present in the upstream repo at the pinned commit `5e899bfd99`. These formats are not yet supported by gftools-builder; the config serves as documentation for future compatibility work and to distinguish legacy-sourced families from families genuinely missing a build recipe.
diff --git a/ofl/acme/config.yaml b/ofl/acme/config.yaml
@@ -0,0 +1,10 @@
+# Legacy upstream sources (.sfd and/or .vfb).
+#
+# gftools-builder does not currently consume these formats. This config
+# is intentional -- it records which source files exist at the pinned
+# upstream commit so a future compatibility layer can pick them up.
+sources:
+  - src/Acme-Regular-OTF.vfb
+  - src/Acme-Regular-TTF.sfd
+  - src/Acme-Regular.vfb
+familyName: Acme
diff --git a/ofl/acme/upstream_info.md b/ofl/acme/upstream_info.md
@@ -57,3 +57,9 @@ These source formats are not compatible with gftools-builder. A config.yaml cann
 - Since the source formats (SFD/VFB) are not gftools-builder compatible, is there a plan to convert the sources to a modern format?
 - Should METADATA.pb be updated to include a `source { }` block pointing to this repo, even though it cannot be built with gftools-builder?
 - PR #743 was a hotfix in 2017. Has the font had any substantive updates since its original release?
+
+## Update (2026-04-24) -- Legacy source documentation
+
+**Model**: Claude Opus 4.7 (1M context)
+
+Added an override `config.yaml` in `ofl/acme/` listing the legacy source files (`.sfd`/`.vfb`) present in the upstream repo at the pinned commit `fa0a4445fe`. These formats are not yet supported by gftools-builder; the config serves as documentation for future compatibility work and to distinguish legacy-sourced families from families genuinely missing a build recipe.
diff --git a/ofl/actor/config.yaml b/ofl/actor/config.yaml
@@ -0,0 +1,9 @@
+# Legacy upstream sources (.sfd and/or .vfb).
+#
+# gftools-builder does not currently consume these formats. This config
+# is intentional -- it records which source files exist at the pinned
+# upstream commit so a future compatibility layer can pick them up.
+sources:
+  - src/Actor-Regular-TTF.vfb
+  - src/Actor-Regular.vfb
+familyName: Actor
diff --git a/ofl/actor/upstream_info.md b/ofl/actor/upstream_info.md
@@ -59,3 +59,9 @@ The font would need to be converted from VFB to a modern format (e.g., `.glyphs`
 1. Should the METADATA.pb be updated to include a `source { repository_url }` block pointing to `https://github.com/librefonts/actor`?
 2. Is there a plan to convert the VFB sources to `.glyphs` or `.ufo` format to enable modern builds?
 3. Does Thomas Junold have the original editable sources in a more modern format?
+
+## Update (2026-04-24) -- Legacy source documentation
+
+**Model**: Claude Opus 4.7 (1M context)
+
+Added an override `config.yaml` in `ofl/actor/` listing the legacy source files (`.sfd`/`.vfb`) present in the upstream repo at the pinned commit `b1617e5929`. These formats are not yet supported by gftools-builder; the config serves as documentation for future compatibility work and to distinguish legacy-sourced families from families genuinely missing a build recipe.
diff --git a/ofl/aguafinascript/config.yaml b/ofl/aguafinascript/config.yaml
@@ -0,0 +1,9 @@
+# Legacy upstream sources (.sfd and/or .vfb).
+#
+# gftools-builder does not currently consume these formats. This config
+# is intentional -- it records which source files exist at the pinned
+# upstream commit so a future compatibility layer can pick them up.
+sources:
+  - src/Aguafina-Regular-OTF.vfb
+  - src/AguafinaScript-Regular-TTF.sfd
+familyName: "Aguafina Script"
diff --git a/ofl/aguafinascript/upstream_info.md b/ofl/aguafinascript/upstream_info.md
@@ -54,3 +54,9 @@ The repo also contains TTX table dumps of the font, METADATA.json, and a DESCRIP
 2. Should a source block be added to METADATA.pb pointing to the librefonts repo, even though there is no config.yaml and the sources are in legacy formats?
 3. Could the SFD source be converted to a modern format (e.g., UFO) to enable gftools-builder compatibility, or is this font effectively in a "legacy binary only" state?
 4. The copyright lists reserved font name "Aguafina Script" -- does this affect any potential source modifications?
+
+## Update (2026-04-24) -- Legacy source documentation
+
+**Model**: Claude Opus 4.7 (1M context)
+
+Added an override `config.yaml` in `ofl/aguafinascript/` listing the legacy source files (`.sfd`/`.vfb`) present in the upstream repo at the pinned commit `45a8ce768b`. These formats are not yet supported by gftools-builder; the config serves as documentation for future compatibility work and to distinguish legacy-sourced families from families genuinely missing a build recipe.
diff --git a/ofl/aladin/config.yaml b/ofl/aladin/config.yaml
@@ -0,0 +1,9 @@
+# Legacy upstream sources (.sfd and/or .vfb).
+#
+# gftools-builder does not currently consume these formats. This config
+# is intentional -- it records which source files exist at the pinned
+# upstream commit so a future compatibility layer can pick them up.
+sources:
+  - src/Aladin-OTF.vfb
+  - src/Aladin-Regular-TTF.sfd
+familyName: Aladin
diff --git a/ofl/aladin/upstream_info.md b/ofl/aladin/upstream_info.md
@@ -50,3 +50,9 @@ No source block present in METADATA.pb.
 ## Notes
 
 SFD-only sources (FontForge format), not gftools-builder compatible
+
+## Update (2026-04-24) -- Legacy source documentation
+
+**Model**: Claude Opus 4.7 (1M context)
+
+Added an override `config.yaml` in `ofl/aladin/` listing the legacy source files (`.sfd`/`.vfb`) present in the upstream repo at the pinned commit `0f5d0578e5`. These formats are not yet supported by gftools-builder; the config serves as documentation for future compatibility work and to distinguish legacy-sourced families from families genuinely missing a build recipe.
diff --git a/ofl/aldrich/config.yaml b/ofl/aldrich/config.yaml
@@ -0,0 +1,9 @@
+# Legacy upstream sources (.sfd and/or .vfb).
+#
+# gftools-builder does not currently consume these formats. This config
+# is intentional -- it records which source files exist at the pinned
+# upstream commit so a future compatibility layer can pick them up.
+sources:
+  - src/Aldrich-Regular-TTF.vfb
+  - src/Aldrich-Regular.vfb
+familyName: Aldrich
diff --git a/ofl/aldrich/upstream_info.md b/ofl/aldrich/upstream_info.md
@@ -49,3 +49,9 @@ No source block present in METADATA.pb.
 ## Notes
 
 No buildable source files at recorded commit
+
+## Update (2026-04-24) -- Legacy source documentation
+
+**Model**: Claude Opus 4.7 (1M context)
+
+Added an override `config.yaml` in `ofl/aldrich/` listing the legacy source files (`.sfd`/`.vfb`) present in the upstream repo at the pinned commit `ec28a1d125`. These formats are not yet supported by gftools-builder; the config serves as documentation for future compatibility work and to distinguish legacy-sourced families from families genuinely missing a build recipe.
diff --git a/ofl/alfaslabone/config.yaml b/ofl/alfaslabone/config.yaml
@@ -0,0 +1,10 @@
+# Legacy upstream sources (.sfd and/or .vfb).
+#
+# gftools-builder does not currently consume these formats. This config
+# is intentional -- it records which source files exist at the pinned
+# upstream commit so a future compatibility layer can pick them up.
+sources:
+  - src/AlfaSlabOne-Regular-OTF.vfb
+  - src/AlfaSlabOne-Regular-TTF.vfb
+  - src/AlfaSlabOne-Regular.vfb
+familyName: "Alfa Slab One"
diff --git a/ofl/alfaslabone/upstream_info.md b/ofl/alfaslabone/upstream_info.md
@@ -49,3 +49,9 @@ No source block present in METADATA.pb.
 ## Notes
 
 No buildable source files at recorded commit
+
+## Update (2026-04-24) -- Legacy source documentation
+
+**Model**: Claude Opus 4.7 (1M context)
+
+Added an override `config.yaml` in `ofl/alfaslabone/` listing the legacy source files (`.sfd`/`.vfb`) present in the upstream repo at the pinned commit `84a903ffba`. These formats are not yet supported by gftools-builder; the config serves as documentation for future compatibility work and to distinguish legacy-sourced families from families genuinely missing a build recipe.
diff --git a/ofl/allan/config.yaml b/ofl/allan/config.yaml
@@ -0,0 +1,9 @@
+# Legacy upstream sources (.sfd and/or .vfb).
+#
+# gftools-builder does not currently consume these formats. This config
+# is intentional -- it records which source files exist at the pinned
+# upstream commit so a future compatibility layer can pick them up.
+sources:
+  - src/Allan-Bold-TTF.sfd
+  - src/Allan-Regular-TTF.sfd
+familyName: Allan
diff --git a/ofl/allan/upstream_info.md b/ofl/allan/upstream_info.md
@@ -50,3 +50,9 @@ No source block present in METADATA.pb.
 ## Notes
 
 SFD-only sources (FontForge format), not gftools-builder compatible
+
+## Update (2026-04-24) -- Legacy source documentation
+
+**Model**: Claude Opus 4.7 (1M context)
+
+Added an override `config.yaml` in `ofl/allan/` listing the legacy source files (`.sfd`/`.vfb`) present in the upstream repo at the pinned commit `91202d58a3`. These formats are not yet supported by gftools-builder; the config serves as documentation for future compatibility work and to distinguish legacy-sourced families from families genuinely missing a build recipe.
diff --git a/ofl/allerta/config.yaml b/ofl/allerta/config.yaml
@@ -0,0 +1,13 @@
+# Legacy upstream sources (.sfd and/or .vfb).
+#
+# gftools-builder does not currently consume these formats. This config
+# is intentional -- it records which source files exist at the pinned
+# upstream commit so a future compatibility layer can pick them up.
+sources:
+  - src/Allerta-Regular-TTF.sfd
+  - src/Allerta-Regular.sfd
+  - src/Allerta-Regular.vfb
+  - src/AllertaStencil-Regular-TTF.sfd
+  - src/AllertaStencil-Regular.sfd
+  - src/AllertaStencil-Regular.vfb
+familyName: Allerta
diff --git a/ofl/allerta/upstream_info.md b/ofl/allerta/upstream_info.md
@@ -50,3 +50,9 @@ No source block present in METADATA.pb.
 ## Notes
 
 SFD-only sources (FontForge format), not gftools-builder compatible
+
+## Update (2026-04-24) -- Legacy source documentation
+
+**Model**: Claude Opus 4.7 (1M context)
+
+Added an override `config.yaml` in `ofl/allerta/` listing the legacy source files (`.sfd`/`.vfb`) present in the upstream repo at the pinned commit `88a8c57b94`. These formats are not yet supported by gftools-builder; the config serves as documentation for future compatibility work and to distinguish legacy-sourced families from families genuinely missing a build recipe.
diff --git a/ofl/allertastencil/config.yaml b/ofl/allertastencil/config.yaml
@@ -0,0 +1,13 @@
+# Legacy upstream sources (.sfd and/or .vfb).
+#
+# gftools-builder does not currently consume these formats. This config
+# is intentional -- it records which source files exist at the pinned
+# upstream commit so a future compatibility layer can pick them up.
+sources:
+  - src/Allerta-Regular-TTF.sfd
+  - src/Allerta-Regular.sfd
+  - src/Allerta-Regular.vfb
+  - src/AllertaStencil-Regular-TTF.sfd
+  - src/AllertaStencil-Regular.sfd
+  - src/AllertaStencil-Regular.vfb
+familyName: "Allerta Stencil"
diff --git a/ofl/allertastencil/upstream_info.md b/ofl/allertastencil/upstream_info.md
@@ -49,3 +49,9 @@ No source block present in METADATA.pb.
 ## Notes
 
 SFD-only sources (FontForge format), not gftools-builder compatible
+
+## Update (2026-04-24) -- Legacy source documentation
+
+**Model**: Claude Opus 4.7 (1M context)
+
+Added an override `config.yaml` in `ofl/allertastencil/` listing the legacy source files (`.sfd`/`.vfb`) present in the upstream repo at the pinned commit `88a8c57b94`. These formats are not yet supported by gftools-builder; the config serves as documentation for future compatibility work and to distinguish legacy-sourced families from families genuinely missing a build recipe.
diff --git a/ofl/almendra/config.yaml b/ofl/almendra/config.yaml
@@ -0,0 +1,15 @@
+# Legacy upstream sources (.sfd and/or .vfb).
+#
+# gftools-builder does not currently consume these formats. This config
+# is intentional -- it records which source files exist at the pinned
+# upstream commit so a future compatibility layer can pick them up.
+sources:
+  - src/Almendra-Bold-OTF.vfb
+  - src/Almendra-Bold-TTF.sfd
+  - src/Almendra-BoldItalic-OTF.vfb
+  - src/Almendra-BoldItalic-TTF.sfd
+  - src/Almendra-Italic-OTF.vfb
+  - src/Almendra-Italic-TTF.sfd
+  - src/Almendra-Regular-OTF.vfb
+  - src/Almendra-Regular-TTF.sfd
+familyName: Almendra
diff --git a/ofl/almendra/upstream_info.md b/ofl/almendra/upstream_info.md
@@ -50,3 +50,9 @@ No source block present in METADATA.pb.
 ## Notes
 
 SFD-only sources (FontForge format), not gftools-builder compatible
+
+## Update (2026-04-24) -- Legacy source documentation
+
+**Model**: Claude Opus 4.7 (1M context)
+
+Added an override `config.yaml` in `ofl/almendra/` listing the legacy source files (`.sfd`/`.vfb`) present in the upstream repo at the pinned commit `4050b694e0`. These formats are not yet supported by gftools-builder; the config serves as documentation for future compatibility work and to distinguish legacy-sourced families from families genuinely missing a build recipe.
diff --git a/ofl/almendradisplay/config.yaml b/ofl/almendradisplay/config.yaml
@@ -0,0 +1,9 @@
+# Legacy upstream sources (.sfd and/or .vfb).
+#
+# gftools-builder does not currently consume these formats. This config
+# is intentional -- it records which source files exist at the pinned
+# upstream commit so a future compatibility layer can pick them up.
+sources:
+  - src/AlmendraDisplay-Regular-OTF.vfb
+  - src/AlmendraDisplay-Regular-TTF.sfd
+familyName: "Almendra Display"
diff --git a/ofl/almendradisplay/upstream_info.md b/ofl/almendradisplay/upstream_info.md
@@ -50,3 +50,9 @@ No source block present in METADATA.pb.
 ## Notes
 
 SFD-only sources (FontForge format), not gftools-builder compatible
+
+## Update (2026-04-24) -- Legacy source documentation
+
+**Model**: Claude Opus 4.7 (1M context)
+
+Added an override `config.yaml` in `ofl/almendradisplay/` listing the legacy source files (`.sfd`/`.vfb`) present in the upstream repo at the pinned commit `b252e05aad`. These formats are not yet supported by gftools-builder; the config serves as documentation for future compatibility work and to distinguish legacy-sourced families from families genuinely missing a build recipe.
diff --git a/ofl/almendrasc/config.yaml b/ofl/almendrasc/config.yaml
@@ -0,0 +1,14 @@
+# Legacy upstream sources (.sfd and/or .vfb).
+#
+# gftools-builder does not currently consume these formats. This config
+# is intentional -- it records which source files exist at the pinned
+# upstream commit so a future compatibility layer can pick them up.
+sources:
+  - src/AlmendraSC-Bold-OTF.vfb
+  - src/AlmendraSC-Bold-TTF.sfd
+  - src/AlmendraSC-BoldItalic-OTF.vfb
+  - src/AlmendraSC-BoldItalic-TTF.sfd
+  - src/AlmendraSC-Italic-OTF.vfb
+  - src/AlmendraSC-Regular-OTF.vfb
+  - src/AlmendraSC-Regular-TTF.sfd
+familyName: "Almendra SC"
diff --git a/ofl/almendrasc/upstream_info.md b/ofl/almendrasc/upstream_info.md
@@ -50,3 +50,9 @@ No source block present in METADATA.pb.
 ## Notes
 
 SFD-only sources (FontForge format), not gftools-builder compatible
+
+## Update (2026-04-24) -- Legacy source documentation
+
+**Model**: Claude Opus 4.7 (1M context)
+
+Added an override `config.yaml` in `ofl/almendrasc/` listing the legacy source files (`.sfd`/`.vfb`) present in the upstream repo at the pinned commit `35906cd6a2`. These formats are not yet supported by gftools-builder; the config serves as documentation for future compatibility work and to distinguish legacy-sourced families from families genuinely missing a build recipe.
diff --git a/ofl/amarante/config.yaml b/ofl/amarante/config.yaml
@@ -0,0 +1,10 @@
+# Legacy upstream sources (.sfd and/or .vfb).
+#
+# gftools-builder does not currently consume these formats. This config
+# is intentional -- it records which source files exist at the pinned
+# upstream commit so a future compatibility layer can pick them up.
+sources:
+  - src/Amarante-Regular-OTF.sfd
+  - src/Amarante-Regular-TTF.sfd
+  - src/Amarante-Regular.vfb
+familyName: Amarante
diff --git a/ofl/amarante/upstream_info.md b/ofl/amarante/upstream_info.md
@@ -50,3 +50,9 @@ No source block present in METADATA.pb.
 ## Notes
 
 SFD-only sources (FontForge format), not gftools-builder compatible
+
+## Update (2026-04-24) -- Legacy source documentation
+
+**Model**: Claude Opus 4.7 (1M context)
+
+Added an override `config.yaml` in `ofl/amarante/` listing the legacy source files (`.sfd`/`.vfb`) present in the upstream repo at the pinned commit `e5bd4a9524`. These formats are not yet supported by gftools-builder; the config serves as documentation for future compatibility work and to distinguish legacy-sourced families from families genuinely missing a build recipe.
diff --git a/ofl/annieuseyourtelescope/config.yaml b/ofl/annieuseyourtelescope/config.yaml
@@ -0,0 +1,8 @@
+# Legacy upstream sources (.sfd and/or .vfb).
+#
+# gftools-builder does not currently consume these formats. This config
+# is intentional -- it records which source files exist at the pinned
+# upstream commit so a future compatibility layer can pick them up.
+sources:
+  - src/AnnieUseYourTelescope.vfb
+familyName: "Annie Use Your Telescope"
diff --git a/ofl/annieuseyourtelescope/upstream_info.md b/ofl/annieuseyourtelescope/upstream_info.md
@@ -49,3 +49,9 @@ No source block present in METADATA.pb.
 ## Notes
 
 No buildable source files at recorded commit
+
+## Update (2026-04-24) -- Legacy source documentation
+
+**Model**: Claude Opus 4.7 (1M context)
+
+Added an override `config.yaml` in `ofl/annieuseyourtelescope/` listing the legacy source files (`.sfd`/`.vfb`) present in the upstream repo at the pinned commit `0895f3f4e7`. These formats are not yet supported by gftools-builder; the config serves as documentation for future compatibility work and to distinguish legacy-sourced families from families genuinely missing a build recipe.
diff --git a/ofl/antic/config.yaml b/ofl/antic/config.yaml
@@ -0,0 +1,8 @@
+# Legacy upstream sources (.sfd and/or .vfb).
+#
+# gftools-builder does not currently consume these formats. This config
+# is intentional -- it records which source files exist at the pinned
+# upstream commit so a future compatibility layer can pick them up.
+sources:
+  - src/Antic-Regular-TTF.sfd
+familyName: Antic
diff --git a/ofl/antic/upstream_info.md b/ofl/antic/upstream_info.md
@@ -50,3 +50,9 @@ No source block present in METADATA.pb.
 ## Notes
 
 SFD-only sources (FontForge format), not gftools-builder compatible
+
+## Update (2026-04-24) -- Legacy source documentation
+
+**Model**: Claude Opus 4.7 (1M context)
+
+Added an override `config.yaml` in `ofl/antic/` listing the legacy source files (`.sfd`/`.vfb`) present in the upstream repo at the pinned commit `928c13650d`. These formats are not yet supported by gftools-builder; the config serves as documentation for future compatibility work and to distinguish legacy-sourced families from families genuinely missing a build recipe.
diff --git a/ofl/anticdidone/config.yaml b/ofl/anticdidone/config.yaml
@@ -0,0 +1,10 @@
+# Legacy upstream sources (.sfd and/or .vfb).
+#
+# gftools-builder does not currently consume these formats. This config
+# is intentional -- it records which source files exist at the pinned
+# upstream commit so a future compatibility layer can pick them up.
+sources:
+  - src/AnticDidone-Regular-OTF.vfb
+  - src/AnticDidone-Regular-TTF.sfd
+  - src/AnticDidone-Regular.vfb
+familyName: "Antic Didone"