M0: план разработки, техническая структура, каркас проекта

- docs/PLAN.md — план по этапам, обновляется по мере работы
- docs/TECHNICAL.md — слои, карта папок, контракты, рабочие процессы
- docs/DECISIONS.md — журнал решений, принятых самостоятельно
- разрешение 1080x1920, fit-width (портрет, 4:3..21:9)
- каркас assets/scripts (core / modules / app / ui)
- headless-тесты на vitest + strict typecheck + защита чистоты core
- Rng: детерминированный генератор и перемешивание

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
ftc
2026-09-13 10:28:49 +03:00
co-authored by Claude Opus 5
parent 47e59eab38
commit c980440856
31 changed files with 2333 additions and 1 deletions
+20
View File
@@ -100,3 +100,23 @@ cd extensions/cocos-code-mode && npm install --no-save --os=win32 --cpu=x64 --in
(`extensions/cocos-code-mode/node_modules` is gitignored, so that install does not
survive a clean checkout either.)
## Known issue: the setter tools take arrays, not a single path
[CODE_MODE_TOOLS.md](CODE_MODE_TOOLS.md) is generated from the manual the
extension serves, and for `inspectorSetInstanceProperties` /
`inspectorSetSettingsProperties` that manual advertises a singular
`propertyPath` + `value` pair. The implementation actually loaded
([set-properties-tool.js](../extensions/cocos-code-mode/dist/utcp/tools/set-properties-tool.js))
expects parallel arrays, and the singular form fails with the unhelpful
`Cannot read properties of undefined (reading 'length')`.
Use:
```js
CocosEditor.inspectorSetSettingsProperties({
settingsType: 'ProjectSettings',
propertyPaths: ['general.designResolution.width', 'general.fitWidth'],
values: [1080, true],
});
```