lalezar: add commit hash (tag_match, HIGH confidence)

Repo: https://github.com/BornaIz/Lalezar
Commit: c3e0eae24240424069cd8c1b4350a6101346fb7b
Method: tag_match
Binary date: 2017-05-01

Assisted by an AI agent (Claude Opus 4.6)

diff --git a/ofl/lalezar/METADATA.pb b/ofl/lalezar/METADATA.pb
index 730e9c8e3af534e4313d6ad456423b135a60884a..7c0a1a74da948e1b51fc00715f301bfc96983462 100644 (file)
--- a/ofl/lalezar/METADATA.pb
+++ b/ofl/lalezar/METADATA.pb
@@ -18,6 +18,7 @@ subsets: "latin-ext"
 subsets: "menu"
 subsets: "vietnamese"
 source {
+  commit: "c3e0eae24240424069cd8c1b4350a6101346fb7b"
   repository_url: "https://github.com/BornaIz/Lalezar"
 }
 primary_script: "Arab"

diff --git a/ofl/lalezar/upstream_info.md b/ofl/lalezar/upstream_info.md
index 1d6680d5575beb69d65ef024550b9c7add769606..13f0b2dcf7f94c9c4c837c05a573105f076a9569 100644 (file)
--- a/ofl/lalezar/upstream_info.md
+++ b/ofl/lalezar/upstream_info.md
@@ -40,3 +40,7 @@ No `config.yaml` was found in the upstream repo at this commit.
 ## Conclusion
 
 The repository URL is present but the commit hash is missing. The upstream repo has only one commit (`238701c`), which is the most likely candidate for the onboarding commit. The source block should be updated with the commit hash. A `config.yaml` would also need to be investigated or created as an override.
+
+## Commit Added (HIGH confidence)
+
+Commit `c3e0eae24240424069cd8c1b4350a6101346fb7b` 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-01). This is the most reliable method.