Fix the failures found during the four-tool interactive UAT.
This PR is scoped only to the UAT failures. Do not add new features.
Interactive UAT results:
- Vector Map Editor: FAIL
- Vector Asset Studio: FAIL
- Sprite Editor: FAIL
- State Inspector: PASS
State Inspector passed all VS-001 through VS-005 checks and is out of scope for this PR.
Fix only:
- Vector Map Editor default selected-state visibility after loading sample
1212 - Vector Asset Studio sample load timeouts for
0901,1204,1208 - Vector Asset Studio missing invalid/incomplete-state actionable message
- Sprite Editor missing invalid-state actionable message
Do not modify unrelated tools, sample games, runtime engine files, or start_of_day folders.
PR 10.6V acceptance failed after loading sample 1212.
Observed:
objectCount=3activeCount=0- selected shown as none
After loading a map/sample with objects, the editor must clearly show the selected-state status.
Allowed outcomes:
- If no object is selected, show an explicit visible message such as:
No object selected. Select an object from the map or object list. - If an object is selected by the user, show the selected object clearly.
- Do not silently auto-select the first object.
- Do not restore stale hidden selections.
- Loading sample
1212with three objects shows an explicit no-selection message. - User selection updates the selected-state display.
- Clearing selection returns to the explicit no-selection message.
- No silent auto-selection occurs.
Samples 0901, 1204, and 1208 timed out.
Because they timed out, paint/stroke enablement-after-selection could not be validated.
- Samples
0901,1204, and1208must load or fail with an actionable error before UAT timeout. - Loading must not depend on hidden fallback data.
- If required manifest/config/assets are missing, show an actionable error.
- Do not silently create palette/paint/stroke defaults.
For each sample:
090112041208
Confirm one of:
- Sample loads successfully and paint/stroke selection checks can run, OR
- Sample fails fast with actionable error explaining missing/invalid input.
Timeout is not acceptable.
VS-005 failed because invalid/incomplete-state actionable message was not observed.
When Vector Asset Studio receives invalid or incomplete state:
- Display visible actionable error
- Identify missing or invalid field/config
- Explain what the user should provide or fix
- Do not silently normalize into fake valid state
- Do not auto-build hidden palette defaults
- Invalid state produces visible actionable message.
- Incomplete state produces visible actionable message.
- Error is discoverable by UAT automation and human users.
- No silent fallback data is introduced.
VS-005 failed because invalid-state actionable message was not observed.
When Sprite Editor receives invalid state:
- Display visible actionable error
- Identify the missing or invalid input
- Explain what to fix
- Do not silently load fallback sample sprite/assets
- Invalid state produces visible actionable message.
- Empty/missing state produces safe empty state or actionable message.
- No hidden fallback sprite/sample data loads.
All actionable messages should include:
- Tool name
- What failed
- What is missing or invalid
- What the user should do next
Example:
Vector Asset Studio cannot load sample 0901 because required palette configuration is missing. Provide a palette manifest or choose a valid asset package.Run:
node --check "tools/Vector Map Editor/editor/VectorMapEditorApp.js"
node --check "tools/Vector Asset Studio/main.js"
node --check "tools/Sprite Editor/main.js"
npm run test:launch-smoke -- --toolsThen rerun the interactive UAT checks that failed:
- Vector Map Editor sample
1212 - Vector Asset Studio samples
0901,1204,1208 - Vector Asset Studio VS-005
- Sprite Editor VS-005
- Vector Map Editor passes selected-state visibility for sample
1212 - Vector Asset Studio no longer times out for samples
0901,1204,1208 - Vector Asset Studio VS-005 passes
- Sprite Editor VS-005 passes
- State Inspector remains passing
- No silent fallback data is introduced
- No unrelated files are changed
- New features
- Tileset breakout
- King of the Iceberg implementation
- Runtime engine changes
- State Inspector changes unless required by shared code
start_of_daychanges