Base layout with vendored design tokens and fontsБазовый макет с встроенными в сборку токенами дизайна и шрифтами
What this cycle decidedЧто решил этот цикл
Design tokens and fonts are vendored at build time and the bilingual switch is CSS-driven, so the page makes zero third-party requests and stays usable without JavaScript.Токены дизайна и шрифты встраиваются во время сборки, а переключение языка выполняется средствами CSS, поэтому страница не делает сторонних запросов и остаётся рабочей без JavaScript.
TimelineХронология
- Issue openedIssue открыт:
- Proposal approvedПредложение одобрено: +1 h 50 min+1 ч 50 мин
- MergedСмержено: +1 h 3 min+1 ч 3 мин
- ReleasedРелиз выпущен: +3 min+3 мин
Manual interventionsРучные вмешательства
Each record below is quoted verbatim in English, the language it was written in.
Каждая запись ниже приводится дословно по-английски — на языке, на котором она была написана.
regenerated package-lock.json by hand with npm install --package-lock-only
npm install on the implementer's linux/x64 pod pruned every other platform's native binding out of the lockfile, so npm ci in the Dockerfile refused the tree with EUSAGE and the build check could never go green; the shepherd passes the implementer only findings raised by review bots, so the diagnosis posted on the PR never reached it
2026-09-11T01:14:05Z
deleted src/styles/site.css, broke the build, then restored it and gitignored the generated public/styles/site.css instead
the deletion was my error -- scripts/vendor-assets.mjs copies that file from prebuild and I had searched only the source tree for references, not the build scripts; the underlying smell was real, in that the generated copy was committed without being ignored
2026-09-11T01:15:27Z
added the --package-lock-only rule to AGENTS.md (PR #17)
the implementer always runs on linux/x64, so the same failure would recur on any future bump of a package shipping native bindings
2026-09-11T01:16:45Z