Bitcount Single Ink: remove non-buildable config_yaml field

METADATA.pb's config_yaml pointed at the upstream sources/config.yaml,
which contains only "familyName: Bitcount" with no sources: field — not a
gftools-builder config. Bitcount is built by a custom Python/COLRv1
pipeline that gftools-builder cannot reproduce.

Removed the non-functional config_yaml field, addressing the
inconsistency noted in upstream_info.md. Repository URL, commit, branch
and file mappings are unchanged.

Assisted by an AI agent (Claude Opus 4.7)

diff --git a/ofl/bitcountsingleink/METADATA.pb b/ofl/bitcountsingleink/METADATA.pb
index 4808f8e5daa18bfbca8dfa575fbda87f6a8983f2..2b69058a42f7a7305d31194338958b2c92d5fb44 100644 (file)
--- a/ofl/bitcountsingleink/METADATA.pb
+++ b/ofl/bitcountsingleink/METADATA.pb
@@ -82,5 +82,4 @@ source {
     dest_file: "BitcountSingleInk[CRSV,ELSH,ELXP,SZP1,SZP2,XPN1,XPN2,YPN1,YPN2,slnt,wght].ttf"
   }
   branch: "main"
-  config_yaml: "sources/config.yaml"
 }

diff --git a/ofl/bitcountsingleink/upstream_info.md b/ofl/bitcountsingleink/upstream_info.md
index f636cddaca263cd1e9ea9d2ccecc94d85fad5c66..6b432092537241b4ac689fe3d95407448b31e047 100644 (file)
--- a/ofl/bitcountsingleink/upstream_info.md
+++ b/ofl/bitcountsingleink/upstream_info.md
@@ -57,3 +57,19 @@ The commit hash is correct. However, `config_yaml: "sources/config.yaml"` points
 ### Earlier (2025-09-11)
 
 - **2025-09-11** — Emma Marichal, commit [`711bcf6c1`](https://github.com/google/fonts/commit/711bcf6c1) ("bump version"): same-day binary update following the v1.001 onboarding (binary-only, file size unchanged at 430912 bytes — internal version-string bump).
+
+## fontc_crater Build Fix (2026-05-21)
+
+**Model**: Claude Opus 4.7
+
+### Initial state
+METADATA.pb pointed `config_yaml` at the upstream `sources/config.yaml`. The shared upstream repo's fontc_crater build failed with the error `missing field \`sources\``.
+
+### Investigation
+The upstream `sources/config.yaml` contains only `familyName: Bitcount`, with no `sources:` field — it is not a gftools-builder config. Bitcount is built by a custom Python/COLRv1 pipeline (`Makefile` → `scripts/build.py`) that cannot be expressed as a gftools-builder `config.yaml`. The recorded commit `89e7994f` is correct (v1.001).
+
+### Actions taken
+The misleading `config_yaml: "sources/config.yaml"` field was removed from the METADATA.pb `source` block, addressing the inconsistency identified above. No override `config.yaml` was created: the family's build is a bespoke pipeline that gftools-builder cannot reproduce, so it is recorded as not reproducible rather than given a placeholder config.
+
+### Final state
+METADATA.pb retains the correct repository URL and commit; the misleading `config_yaml` reference is gone.