cesnimda/jobtrackingapp
1
0
Fork 0
Code Issues Pull Requests Actions 4 Packages Projects Releases Wiki Activity

docs(i18n): resolve conditional keys and triage display literals

Browse Source
This commit is contained in:
cesnimda
2026-11-02 11:40:29 +01:00
parent 138d8fbb6d
commit 55adc1dbd7
7 changed files with 2932 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/i18n/00/SURFACE_INVENTORY.md
+1 -1
View File
@@ -1,6 +1,6 @@
# Surface inventory and message accounting
All rows need a source-bound contextual census before I18N-00 acceptance. Existing-catalogue inventory is in `MESSAGE_INVENTORY.json`; a non-catalogue literal inventory is still PENDING and no `LITERAL_CANDIDATES.json` was produced. This is not a 100% coverage claim. Namespace assignments remain provisional until caller review; translator context cannot be inferred safely from key names alone. The AST inventory identifies syntactically named `t` calls, not symbol-resolved calls; context fields explicitly remain pending.
All rows need a source-bound contextual census before I18N-00 acceptance. Existing-catalogue inventory is in `MESSAGE_INVENTORY.json`; partial JSX/accessibility literals are now recorded in `FRONTEND_LITERAL_CANDIDATES.json`, with direct reads and dynamic calls in separate inventories. This is not a 100% coverage claim. Namespace assignments remain provisional until caller review; translator context cannot be inferred safely from key names alone. The AST inventory identifies syntactically named `t` calls, not symbol-resolved calls. See CONTEXT_TRIAGE.md for reviewed literal context and the 108 resolved conditional calls; 80 table/template/wrapper calls remain.
| Surface / proposed namespace | Source owner / inspection target | Content boundary and required evidence |
|---|---|---|