Repository navigation
feat: translation library + glossary, slim README (top 10, first screen) - #10
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: d85a0eff52
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| if not gaps: | ||
| result["translate"] = {"todo": 0} | ||
| log("translate: nothing to do, every displayed description already has a current translation") | ||
| hs = nci.hit_stats(lib, items) | ||
| result["translate"] = {"todo": 0, **hs, "calls": 0} | ||
| log(f"translate: library {hs['hits']}/{hs['total']} hits ({_pct(hs['hits'], hs['total'])}), " | ||
| "nothing new, 0 model calls") |
There was a problem hiding this comment.
Refresh usage dates even when every translation is cached
When all ranked descriptions are cache hits, this branch skips translate(), which is the only place that calls nci.touch(). Consequently, a successful run leaves the entries' seen dates unchanged, and a subsequent --prune-days N can delete translations that were just used once their stored dates exceed the retention window. The same problem affects cached entries when other descriptions have gaps but the model is unavailable. Refresh and save usage dates independently of whether model work is needed, while preserving the no-write behavior of dry runs.
Useful? React with 👍 / 👎.
d85a0ef to
53c0e42
Compare
…y, slim README (top 10, first screen) + generated docs/HOW_IT_WORKS
…d against docs/FAQ.md
53c0e42 to
9b778af
Compare
Stacked on #8 (base
feat/agy-local-polish; merge #8 first, then this PR retargets tomain). Not merged. About / topics /llms.txtuntouched.1. Token saving
data/newcomer_i18n.jsonis now the translation librarydata/translation_library.json, keyed exactly by repo + sha256(source)[:12] + language. Hit = no model call. Miss (new or changed text) = only the missing languages of that text are sent. Old versions stay (a change back is a hit).seen+newcomer_i18n.py --prune-days Nfor cleanup (never automatic). Old flat files are still read.data/glossary.json: fixed terms (star, agent, skill, repo, prompt ...) in 5 languages; only the terms present in a batch go into the prompt.translate: library 45/50 hits (90%), 0 partial, 5 new -> 5 to send to the model, 0 calls for the hits,polish: 8/12 texts already polished or given up on (skipped), 4 to send. Printed also when the model is unavailable.2. Slim README (generator only, 5 languages)
First screen: switcher (line 1), headline, header image
.github/social-preview.png, 3 badges (MIT, CI, last updated), one sentence, update stamp, links (Website, How it works, Facts, History, Latest), category leaders table (rows link to the boards), top-10 note, 3 Q&A subheads linkingdocs/FAQ.md. Then the boards (top 10 each; full top 20 inlatest/), star prompt, how to cite (CITATION.cff).Intro, schedule, methodology, categories table, contributing and the long new-repo explanation moved to generated
docs/HOW_IT_WORKS*.md. Daily scripts nowgit add docs/HOW_IT_WORKS*.md.docs/FAQ.md,docs/FACTS.md,CITATION.cff,.github/social-preview.pngcome from GEO PR #9; they are only linked (the link test skips exactly these four until #9 merges).README.md size: 148,743 B before -> 113,426 B after (zh-Hans 150,814 -> 114,907).