laila: add commit hash (tag_match, HIGH confidence)

Repo: https://github.com/itfoundry/laila
Commit: a8b5b4ee6cf52508cc0d4f606d4ec0ae4994953a
Method: tag_match
Binary date: 2017-05-15

Assisted by an AI agent (Claude Opus 4.6)

diff --git a/ofl/laila/METADATA.pb b/ofl/laila/METADATA.pb
index 76d62efb942b3d3b1800a0fc2128eaac7c7677d0..544148e20a7038ba514e4fcd9582ebcfe69874ef 100644 (file)
--- a/ofl/laila/METADATA.pb
+++ b/ofl/laila/METADATA.pb
@@ -53,6 +53,7 @@ subsets: "latin"
 subsets: "latin-ext"
 subsets: "menu"
 source {
+  commit: "a8b5b4ee6cf52508cc0d4f606d4ec0ae4994953a"
   repository_url: "https://github.com/itfoundry/laila"
 }
 primary_script: "Deva"

diff --git a/ofl/laila/upstream_info.md b/ofl/laila/upstream_info.md
index 50709ec1c142ed649435f4d483ee9de934606e1c..a9ccb7f8c1c59fa7ecf4884bae998a884705c609 100644 (file)
--- a/ofl/laila/upstream_info.md
+++ b/ofl/laila/upstream_info.md
@@ -40,3 +40,7 @@ The upstream repo uses a custom Python build system (`build.py`, `config.py`) wi
 ## Conclusion
 
 The source block exists with the repository URL but is missing the commit hash. The upstream sources are UFO + VFB with a custom build system and no `config.yaml`. An investigation into the ITF build infrastructure would be needed to determine the exact commit used for the v1.302 onboarding. The most likely candidate is `a8b5b4e` (the latest commit before the 2017 google/fonts update), but this cannot be confirmed without further research.
+
+## Commit Added (HIGH confidence)
+
+Commit `a8b5b4ee6cf52508cc0d4f606d4ec0ae4994953a` was determined by **tag_match**. Matched a version tag in the upstream repo whose date is on or before the binary modification date in google/fonts (2017-05-15). This is the most reliable method.