Split from the 15.1 third-party eval follow-ups (#3102 hides the platform i18n baseline from os lint; this is the remaining user-side gap).
A fresh npm create objectstack (blank template) still reports 4 genuine i18n/missing-object / i18n/missing-field errors for its own <ns>_note object, because the template ships no en translation bundle while the default-locale coverage gate demands 100%.
Options (pick one):
- Ship an
en translation bundle with the blank template so a fresh scaffold lints clean.
- Teach the default-locale coverage rule to treat inline
label: metadata as the en source of truth (then a bundle is only required for additional locales) — likely the better long-term semantics, but touches computeI18nCoverage for every project.
Repro:
node packages/create-objectstack/bin/create-objectstack.js demo --skip-skills
cd demo && npx os lint # 4 error(s) on the template's own object
🤖 Generated with Claude Code
Split from the 15.1 third-party eval follow-ups (#3102 hides the platform i18n baseline from
os lint; this is the remaining user-side gap).A fresh
npm create objectstack(blank template) still reports 4 genuinei18n/missing-object/i18n/missing-fielderrors for its own<ns>_noteobject, because the template ships noentranslation bundle while the default-locale coverage gate demands 100%.Options (pick one):
entranslation bundle with the blank template so a fresh scaffold lints clean.label:metadata as theensource of truth (then a bundle is only required for additional locales) — likely the better long-term semantics, but touchescomputeI18nCoveragefor every project.Repro:
🤖 Generated with Claude Code