Skip to content

Commit 747333e

Browse files
author
DavidQ
committed
MODEL: GPT-5.3-codex
REASONING: low PR purpose: Validate the tool workflow for creating a basic King of the Iceberg layout. Do not implement gameplay. Do not add new features unless a tiny test-only artifact is required to validate existing workflow. Do not modify start_of_day folders. Do not modify sample games or runtime engine files. Main workflow: 1. Launch Vector Map Editor. 2. Confirm no hidden/default map loads. 3. Create or load an explicit baseline layout. 4. Represent 3 to 5 fragmented horizontal ice platforms. 5. Confirm each platform is independently selectable. 6. Confirm clearing selection shows explicit no-selection state. 7. Save/export the layout state. 8. Inspect exported state in State Inspector. 9. Sanity-check Vector Asset Studio paint/stroke controls. 10. Sanity-check Sprite Editor launch/header/no-fallback behavior. Required report: Create docs/dev/reports/PR_tool_layout_workflow_baseline_report.md Report must include: - PASS/FAIL - Changed files, if any - Validation steps performed - Export/save path - Any blockers - Remaining issues without masking them Hard rules: - No silent fallback data. - No hidden sample auto-load. - Missing/invalid input must produce actionable messages. - Do not add King of the Iceberg runtime code. - Do not build tileset breakout yet. Validation: - Run node --check on any changed JavaScript files. - Run npm run test:launch-smoke -- --tools. - If an exported JSON/layout file is produced, verify it with State Inspector.
1 parent aa5bb6a commit 747333e

10 files changed

Lines changed: 766 additions & 39 deletions

File tree

‎docs/dev/codex_commands.md‎

Lines changed: 40 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1,12 +1,45 @@
11
MODEL: GPT-5.3-codex
22
REASONING: low
33

4-
Run interactive UAT:
4+
PR purpose:
5+
Validate the tool workflow for creating a basic King of the Iceberg layout.
56

6-
- Open each tool in browser
7-
- Execute manual test steps from PR doc
8-
- Record PASS/FAIL per tool
9-
- Capture issues without fixing them
7+
Do not implement gameplay.
8+
Do not add new features unless a tiny test-only artifact is required to validate existing workflow.
9+
Do not modify start_of_day folders.
10+
Do not modify sample games or runtime engine files.
1011

11-
Do not modify code in this PR.
12-
Only report findings.
12+
Main workflow:
13+
1. Launch Vector Map Editor.
14+
2. Confirm no hidden/default map loads.
15+
3. Create or load an explicit baseline layout.
16+
4. Represent 3 to 5 fragmented horizontal ice platforms.
17+
5. Confirm each platform is independently selectable.
18+
6. Confirm clearing selection shows explicit no-selection state.
19+
7. Save/export the layout state.
20+
8. Inspect exported state in State Inspector.
21+
9. Sanity-check Vector Asset Studio paint/stroke controls.
22+
10. Sanity-check Sprite Editor launch/header/no-fallback behavior.
23+
24+
Required report:
25+
Create docs/dev/reports/PR_tool_layout_workflow_baseline_report.md
26+
27+
Report must include:
28+
- PASS/FAIL
29+
- Changed files, if any
30+
- Validation steps performed
31+
- Export/save path
32+
- Any blockers
33+
- Remaining issues without masking them
34+
35+
Hard rules:
36+
- No silent fallback data.
37+
- No hidden sample auto-load.
38+
- Missing/invalid input must produce actionable messages.
39+
- Do not add King of the Iceberg runtime code.
40+
- Do not build tileset breakout yet.
41+
42+
Validation:
43+
- Run node --check on any changed JavaScript files.
44+
- Run npm run test:launch-smoke -- --tools.
45+
- If an exported JSON/layout file is produced, verify it with State Inspector.

‎docs/dev/commit_comment.txt‎

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
1-
Run interactive UAT on stabilized tools
1+
Validate baseline tool layout workflow
22

3-
- Validate Vector Map Editor behavior
4-
- Validate paint/stroke interactions
5-
- Validate State Inspector JSON handling
6-
- Confirm header UX consistency
7-
- Capture issues without modifying behavior
3+
- Verify Vector Map Editor can represent fragmented platform layout
4+
- Confirm explicit selection and no-selection behavior
5+
- Confirm layout save/export path can be inspected
6+
- Sanity-check asset, sprite, and state tools after stabilization
7+
- Document workflow findings for first King of the Iceberg layout

‎docs/dev/pr_tool_layout_workflow_baseline.md‎

Lines changed: 155 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,155 @@
1+
# PR — Tool Layout Workflow Baseline
2+
3+
## Purpose
4+
5+
Validate the tool workflow needed to create, load, edit, inspect, and save a simple King of the Iceberg platform layout.
6+
7+
This PR is workflow validation only. Do not implement King of the Iceberg gameplay.
8+
9+
---
10+
11+
## Scope
12+
13+
Use the existing stabilized tools to validate the layout pipeline:
14+
15+
- Vector Map Editor
16+
- Vector Asset Studio
17+
- Sprite Editor
18+
- State Inspector
19+
20+
The main focus is the Vector Map Editor workflow.
21+
22+
---
23+
24+
## Goal
25+
26+
Confirm the tools can support a basic screen layout workflow for King of the Iceberg:
27+
28+
- Create or load a simple layout
29+
- Represent fragmented ice platforms
30+
- Verify explicit selection behavior
31+
- Verify object/property visibility
32+
- Save/export the layout state
33+
- Inspect the saved/exported state
34+
35+
---
36+
37+
## Baseline Layout Definition
38+
39+
Create a simple non-gameplay test layout representing the first King of the Iceberg arena concept.
40+
41+
### Layout Requirements
42+
43+
- One main iceberg area
44+
- 3 to 5 fragmented horizontal platforms
45+
- Visible gaps between platforms
46+
- Lowest platform reachable from water zone
47+
- Top platform clearly marked as control/top area
48+
- Background/midground placeholders may be represented as non-collision objects only
49+
50+
### Platform Mode Note
51+
52+
This PR does not implement pass-through or solid platform behavior.
53+
54+
It only validates that the layout can represent platforms and gaps clearly enough for later gameplay work.
55+
56+
---
57+
58+
## Workflow Steps
59+
60+
### 1. Vector Map Editor
61+
62+
- Launch the tool fresh.
63+
- Confirm no hidden/default map loads.
64+
- Create or load an explicit test layout.
65+
- Add 3 to 5 platform objects.
66+
- Ensure each platform is individually selectable.
67+
- Verify no object is auto-selected unless the user selects it.
68+
- Select each platform and confirm selected-state display updates.
69+
- Clear selection and confirm explicit no-selection state appears.
70+
- Save/export the layout state.
71+
72+
### 2. State Inspector
73+
74+
- Load or paste the exported layout state.
75+
- Confirm JSON formats correctly.
76+
- Confirm platform objects are visible in the state.
77+
- Confirm no silent fallback state appears.
78+
79+
### 3. Vector Asset Studio
80+
81+
- Open or create a simple ice platform/vector object if supported by existing workflow.
82+
- Confirm fill/paint/stroke controls work on selected object.
83+
- Confirm no-selection state disables controls with reason.
84+
85+
### 4. Sprite Editor
86+
87+
- Launch only as sanity check.
88+
- Confirm no invalid fallback sprite loads.
89+
- Confirm header behavior remains correct.
90+
91+
---
92+
93+
## Expected Layout Object Shape
94+
95+
Use existing project conventions where available.
96+
97+
The exported layout should make it possible to identify:
98+
99+
- layout/map id
100+
- object list
101+
- platform objects
102+
- position
103+
- size/bounds
104+
- collision intent if already supported
105+
- render/layer role if already supported
106+
107+
Do not invent a new runtime schema in this PR unless the existing tool requires a local test-only shape.
108+
109+
---
110+
111+
## Acceptance Criteria
112+
113+
- Vector Map Editor can create/load a baseline platform layout.
114+
- 3 to 5 platform objects are visible and individually selectable.
115+
- Explicit no-selection state is visible after clearing selection.
116+
- Layout can be saved/exported.
117+
- State Inspector can read/format the exported layout state.
118+
- No silent fallback map, object, sprite, or state data appears.
119+
- Vector Asset Studio paint/stroke behavior still works on a selected object.
120+
- Sprite Editor launches without fallback/invalid-state regression.
121+
- No gameplay code is added.
122+
123+
---
124+
125+
## Out of Scope
126+
127+
- King of the Iceberg gameplay
128+
- Player movement
129+
- Platform collision behavior
130+
- Pass-through platform physics
131+
- Solid platform physics
132+
- Tile slicing
133+
- Tileset breakout
134+
- Parallax asset production
135+
- Runtime engine refactors
136+
- start_of_day changes
137+
138+
---
139+
140+
## Reporting
141+
142+
Create a short report under:
143+
144+
```txt
145+
docs/dev/reports/PR_tool_layout_workflow_baseline_report.md
146+
```
147+
148+
The report must include:
149+
150+
- PASS/FAIL
151+
- Changed files, if any
152+
- Layout workflow notes
153+
- Export/save result location
154+
- Any blockers found
155+
- Screenshots optional

0 commit comments

Comments
 (0)