Amethysta: document unreproducible shipped binary (won't-fix)

No METADATA.pb change. See upstream_info.md for the rationale.

Assisted by an AI agent (Claude Opus 4.8)

diff --git a/ofl/amethysta/upstream_info.md b/ofl/amethysta/upstream_info.md
index e2f515ad69cdbc14c9267f34898813feb51d8247..1fe4397fda4b144c0ad2a4ea878ef51933ffd236 100644 (file)
--- a/ofl/amethysta/upstream_info.md
+++ b/ofl/amethysta/upstream_info.md
@@ -53,3 +53,12 @@ Override `config.yaml` exists in `ofl/amethysta/config.yaml`.
 ## Notes
 
 Second commit in upstream (2016-04-06, adds sample image). Font files present since initial commit. Used for gfonts PR #760 merged 2017-08-07.
+
+
+## Source-metadata review (2026-06-02) — WON'T FIX (unreproducible)
+
+**Model**: Claude Opus 4.8
+
+fontc_crater reports `missing source 'sources/Amethysta-Regular.glyphs'`: at the pinned commit `10ae36bc` (2016) the repository has no `.glyphs` source at all. The only commit that contains `sources/Amethysta-Regular.glyphs` is `d3cd4cae` (tag v1.002, 2024-12-29). However the shipped google/fonts binary is **Version 1.003**, which no upstream commit produces (the repo only ever builds v1.002). Repointing to `d3cd4cae` would make the family buildable but would **downgrade** it (v1.002 < the shipped v1.003), so it is not a valid provenance correction.
+
+Decision: **WON'T FIX** here — the METADATA.pb source block is left unchanged. Resolving this requires either locating the lost v1.003 source upstream or a deliberate decision to refresh the family down to the available v1.002 source; both are owner/maintainer calls, not a mechanical metadata fix.