lato: add commit hash (date_correlation, MEDIUM confidence)

Repo: https://github.com/googlefonts/LatoGFVersion
Commit: 080cb69711ca050d91e9c866e58df7a73095c69a
Method: date_correlation
Binary date: 2016-12-02

Assisted by an AI agent (Claude Opus 4.6)

diff --git a/ofl/lato/METADATA.pb b/ofl/lato/METADATA.pb
index 3f709b8f6cbc8ce3df3705bc8381480883ba1d41..f2036e722223ef4134d2d8c36ef4faa7cd147480 100644 (file)
--- a/ofl/lato/METADATA.pb
+++ b/ofl/lato/METADATA.pb
@@ -174,6 +174,7 @@ subsets: "latin-ext"
 subsets: "menu"
 subsets: "vietnamese"
 source {
+  commit: "080cb69711ca050d91e9c866e58df7a73095c69a"
   repository_url: "https://github.com/googlefonts/LatoGFVersion"
 }
 fallbacks {

diff --git a/ofl/lato/upstream_info.md b/ofl/lato/upstream_info.md
index e0b83d5a722f9f17aa7c5c3b14324fc52167ffc3..523b91e582982b61cc6a0aa667907bb743ff6858 100644 (file)
--- a/ofl/lato/upstream_info.md
+++ b/ofl/lato/upstream_info.md
@@ -42,3 +42,7 @@ This repo contains prebuilt TTF files in `src/` rather than design-time sources.
 ## Conclusion
 
 The repository URL is present but the commit hash is missing. The most likely onboarding commit is `080cb69` ("fonts: regenerated", 2016-11-28), which is the HEAD of the LatoGFVersion repo at the time of the google/fonts addition. However, the source contains only prebuilt TTF files and custom shell/Python build scripts — no gftools-builder compatible sources. No `config.yaml` is possible without proper design sources.
+
+## Commit Added (MEDIUM confidence)
+
+Commit `080cb69711ca050d91e9c866e58df7a73095c69a` was determined by **date_correlation**. Found the latest upstream commit before the binary modification date in google/fonts (2016-12-02). This assumes the upstream HEAD at onboarding time was the commit used.