You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/dev/CODEX_COMMANDS.md
+25-12Lines changed: 25 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,16 +2,26 @@ MODEL: GPT-5.4
2
2
REASONING: high
3
3
4
4
COMMAND:
5
-
Create BUILD_PR_TOOL_REGISTRY_VALIDATOR_AND_SPRITE_FIRST_CLASS as a docs-aligned implementation PR.
5
+
Create BUILD_PR_TOOLS_INDEX_SURFACE_CLEANUP as a docs-first, surgical surface cleanup PR for HTML-JavaScript-Gaming.
6
6
7
-
REQUIREMENTS:
8
-
1. Keep `tools/` first-class and registry-driven.
9
-
2. Make `Sprite Editor` first-class and active in `tools/toolRegistry.js`.
10
-
3. Keep `SpriteEditor_old_keep` preserved but excluded from active tool rendering.
11
-
4. Update all active header/tool-surface rendering to use `entry.active === true`.
12
-
5. Add a registry validator script that compares registry entries to filesystem directories.
13
-
6. Fail validation on missing folders, missing registry entries, duplicate ids/names/paths, inactive `Sprite Editor`, or active legacy `SpriteEditor_old_keep`.
14
-
7. Add a validation report output under `docs/dev/reports/` or equivalent repo-appropriate dev report location.
7
+
GOAL:
8
+
Make `tools/index.html` show only true first-class launchable tools. Keep `Sprite Editor` first-class and visible. Keep `SpriteEditor_old_keep` legacy and hidden. Remove `Advanced Systems & Extensions` from the tools landing page unless each item in that section is verified to be an actual active launchable tool under `tools/`.
9
+
10
+
TARGET FILES TO AUDIT:
11
+
- tools/index.html
12
+
- tools/toolRegistry.js
13
+
- tools/renderToolsIndex.js
14
+
- any config/data feeding the tools page
15
+
16
+
RULES:
17
+
1.`tools/index.html` is a user-facing tool launcher, not a platform/dev page.
18
+
2. Only render entries that are true first-class tools.
19
+
3. Keep `Sprite Editor` active and visible.
20
+
4. Keep `SpriteEditor_old_keep` hidden from active UI.
21
+
5. If `Advanced Systems & Extensions` entries are platform/dev/internal, move or delete them.
22
+
6. If they are duplicate/placeholder/dead, delete them.
23
+
7. Do not expand scope beyond this cleanup.
24
+
8. Preserve engine theme usage.
15
25
16
26
EXPECTED ACTIVE TOOLS:
17
27
- Vector Map Editor
@@ -20,8 +30,11 @@ EXPECTED ACTIVE TOOLS:
20
30
- Parallax Scene Studio
21
31
- Sprite Editor
22
32
23
-
EXPECTED LEGACY TOOL:
24
-
- SpriteEditor_old_keep
33
+
EXPECTED RESULT:
34
+
- no misleading `Advanced Systems & Extensions` on main tools page unless truly valid
Restore Sprite Editor as a first-class active tool, keep SpriteEditor_old_keep preserved but hidden, and add a filesystem-aware tool registry validator with report output.
Clean up `tools/index.html` so it acts as a user-facing launcher for true first-class tools only.
5
+
6
+
## Scope
7
+
In scope:
8
+
- remove non-launchable planning and platform/internal sections from `tools/index.html`
9
+
- keep the landing page aligned with the registry-driven first-class tool set
10
+
- keep `Sprite Editor` first-class and visible
11
+
- keep preserved legacy sprite tooling hidden
12
+
- preserve engine theme usage
13
+
14
+
Out of scope:
15
+
- registry shape changes beyond what is needed for alignment
16
+
- tool implementation changes
17
+
- engine runtime changes
18
+
- broader content refactors outside the tools landing surface
19
+
20
+
## First-Class Launchable Tools
21
+
- Vector Map Editor
22
+
- Vector Asset Studio
23
+
- Tilemap Studio
24
+
- Parallax Scene Studio
25
+
- Sprite Editor
26
+
27
+
## Preserved But Hidden
28
+
-`tools/SpriteEditor_old_keep/`
29
+
30
+
## Implementation Summary
31
+
- removed the `Planned Next` section from the tools landing page because it did not represent active launchable tools
32
+
- removed the `Advanced Systems & Extensions` section from the tools landing page because those entries are platform/dev placeholders rather than actual tools under `tools/`
33
+
- kept the landing page focused on the registry-driven first-class tool launcher only
34
+
- preserved the engine theme and shared shell usage
35
+
- kept registry and renderer behavior aligned with the active tool list
0 commit comments