The kit is going public, so everything a reader sees is now English:
27 model sources, the core vocabulary, meta.ts (titles, descriptions and
every slider label), the viewer UI, all script output, REFERENCE.md and
the READMEs.
Rules applied: only comments, doc comments and human-facing strings were
touched. Identifiers, numbers, logic, registry item ids, part names and
material slot names are unchanged — those are a published contract and
were already English.
Verified rather than assumed: for all 53 changed .ts files the code
skeleton (source with comments stripped and string contents replaced by a
placeholder) is byte-identical before and after. Full gate is green —
typecheck, registry conformance, ~510 model checks, GLB round trip and a
production build.
Also fixed here:
- index.html and viewer.html were missed by the translation pass because
the file list only covered .ts/.md/.css. Both had lang="tr" and Turkish
titles.
- The viewer formatted triangle counts with toLocaleString('tr-TR'), which
prints 15.425 rather than 15,425.
- REFERENCE.md's model table header did not match what
scripts/catalog-table.ts emits, so the next regeneration would have
silently changed it. Aligned to the generator.
- Removed scripts/probe.ts and scripts/zdiag.ts; they were throwaway
diagnostics that got committed by accident.
|
||
|---|---|---|
| .. | ||
| iron-brazier | ||
| README.md | ||
Drafts
Models in this folder are not compiled into the registry — build.ts only
walks models/. The code is kept, but it never enters the published package.
iron-brazier
An iron brazier with a flickering flame, glowing coals, and a light of its own.
It works, technically (typed actions, update(), four material slots), but it
does not belong to the kit's language: the backbone of a medieval kit is not one
showpiece model, it is the many plain pieces that build a scene once they stand
next to each other.
To pull it back into the kit, move it under models/ and add its entry to
MODEL_META in meta.ts.