Skip to content

Commit a2b3677

Browse files
author
DavidQ
committed
Recover Workspace Manager games tile UAT path
PR Details: - Uses PROJECT_INSTRUCTIONS.md as the active workflow contract. - Adds mandatory Codex anti-pattern guard rules. - Directs a smallest-scoped BUILD for opening Workspace Manager from games/index.html. - Requires UAT report and repo-structured Codex ZIP output. & Enforce extended anti-pattern rules in codex_rules.md
1 parent b42ae78 commit a2b3677

13 files changed

Lines changed: 596 additions & 90 deletions

‎docs/dev/PROJECT_INSTRUCTIONS.md‎

Lines changed: 196 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,196 @@
1+
# PROJECT INSTRUCTIONS
2+
3+
You are working in a docs-first repo workflow.
4+
5+
Workflow:
6+
PLAN_PR → BUILD_PR → APPLY_PR
7+
8+
Rules:
9+
- One PR purpose only
10+
- Smallest scoped valid change
11+
- BUILD must be one-pass executable
12+
- No vague wording
13+
- No repo-wide scanning unless required
14+
15+
Responsibilities:
16+
- ChatGPT: create plans, PR docs, and ZIP bundles
17+
- Codex: writes implementation code
18+
- User: runs Codex + validates
19+
20+
Output rules:
21+
- Always produce repo-structured ZIPs
22+
- Place ZIPs under <project folder>/tmp/
23+
- Preserve exact repo structure inside ZIP
24+
25+
Do not:
26+
- Write implementation code unless explicitly asked
27+
- Expand scope beyond the PR
28+
- Modify start_of_day folders unless requested
29+
30+
NEXT resolution rules:
31+
32+
If the user says "NEXT":
33+
1. Look for the highest completed or referenced PLAN_PR in the session
34+
2. Increment to the next logical PLAN_PR in sequence
35+
3. If sequence is unclear, STOP and ask for clarification
36+
37+
Assume naming pattern:
38+
PLAN_PR_LEVEL_<major>_<minor>_<name>
39+
40+
Example:
41+
If last = PLAN_PR_LEVEL_11_1_...
42+
NEXT = PLAN_PR_LEVEL_11_2_...
43+
44+
If no prior context exists:
45+
STOP and ask: "What is the base PLAN_PR?"
46+
47+
One-shot execution rule:
48+
49+
If the user says:
50+
"Run full workflow for <PLAN_PR_NAME>" or "NEXT"
51+
52+
Then:
53+
1. Validate the PLAN
54+
2. Generate a compact BUILD_PR
55+
3. Generate Codex command
56+
4. Package a repo-structured ZIP
57+
5. Return all outputs
58+
59+
Do not ask for confirmation unless ambiguity exists.
60+
61+
OUTPUT FORMAT (STRICT)
62+
63+
When producing BUILD, PLAN, or APPLY results:
64+
65+
- ALWAYS return a downloadable ZIP
66+
- DO NOT output full command text, PR docs, or reports inline
67+
- Keep chat response minimal:
68+
- ZIP download
69+
- short summary (1–3 lines max)
70+
- NEXT step (if applicable)
71+
72+
All detailed content must be placed inside the ZIP, including:
73+
- docs/pr/*
74+
- docs/operations/dev/codex_commands.md
75+
- docs/operations/dev/commit_comment.txt
76+
- docs/dev/reports/*
77+
78+
If a ZIP cannot be produced:
79+
- STOP and explain why
80+
- DO NOT fall back to full inline output
81+
82+
ZIP STANDARD (ENFORCED)
83+
84+
- Exactly one ZIP per request
85+
- ZIP name MUST match PR name
86+
- ZIP path MUST be:
87+
<project folder>/tmp/<PR_NAME>.zip
88+
- Internal structure MUST be repo-relative only
89+
- No extra files outside defined structure
90+
91+
Commit Comment:
92+
<change details>
93+
<PR Details>
94+
## 🔒 EXECUTION DEFAULTS (MANDATORY)
95+
96+
### ALWAYS CONTINUE
97+
- Never pause for confirmation
98+
- Never present optional branches
99+
- Always proceed to the next logical step
100+
101+
### NO COMMIT-ONLY PRs
102+
- Roadmap lives at: docs\dev\roadmaps\MASTER_ROADMAP_ENGINE.md
103+
- Only one roadmap
104+
- PRs must include something testable and improve the Roadmap
105+
- All PRs numbe improve the roadmap [ ] to [.] or [.] to [x]
106+
- If a PR is doc-only, bundle with next smallest executable/testable change
107+
108+
### ZIP IS ALWAYS REQUIRED
109+
- Never ask if a ZIP is needed
110+
- Always produce a ZIP
111+
112+
### DEFAULT EXECUTION MODE
113+
- Assume approval
114+
- Continue automatically
115+
- Do not stop unless blocked
116+
117+
## Productization Rules
118+
- Do not create standalone showcase tracks in future roadmaps
119+
- Fold showcase importance into the main feature or sample title when needed
120+
121+
## Roadmap Instruction Move Guards
122+
- If roadmap content is moved to `PROJECT_INSTRUCTIONS.md`, move it and do not delete it without relocation.
123+
- Ensure destination text exists before removing the source text.
124+
- Preserve wording unless the PR explicitly requires rewriting.
125+
- Keep roadmap handling status-only unless explicitly requested otherwise.
126+
- Do not delete roadmap content during cleanup work.
127+
- Do not modify roadmap content during cleanup work.
128+
- Only update status [ ] [.] [x] in roadmap content during cleanup work.
129+
130+
131+
## EXECUTION EFFICIENCY
132+
133+
- Bundle PRs whenever it is safe and testable to reduce overall timeline and churn.
134+
- Codex must always return a ZIP artifact at:
135+
<project folder>/tmp/<PR_NAME>.zip
136+
- Never ask whether to create the next ZIP for Codex; always assume it is required.
137+
- Default execution behavior:
138+
- Choose the correct path automatically
139+
- Reduce the number of options presented
140+
- Do the right thing and complete the task fully and correctly
141+
- Don't ask if I want the next bundled PR, assume I want it.
142+
- Update Roadmap stutus every PR.
143+
- Every PRs must improve roadmap and be testable.
144+
145+
# BUILD_PR_LEVEL_19_20_TOOLCHAIN_ROADMAP_GUARD_ENFORCEMENT
146+
147+
## Purpose
148+
Enforce the master roadmap guard for future Codex executions during the Phase 19 closeout lane.
149+
150+
## Mandatory Roadmap Rules
151+
- never delete roadmap content
152+
- never rewrite existing roadmap text
153+
- only append new roadmap content when explicitly required by the PR
154+
- only update status markers using:
155+
- [ ] -> [.]
156+
- [.] -> [x]
157+
158+
## Scope
159+
- docs-first enforcement only
160+
- no implementation code
161+
- no tests
162+
- no scripts
163+
- no roadmap rewrite
164+
- no roadmap replacement file in this bundle
165+
166+
## Codex Responsibilities
167+
- validate any roadmap touch against the guard rules above
168+
- reject edits that delete, shorten, paraphrase, reflow, or otherwise rewrite existing roadmap text
169+
- if roadmap status must change for this PR, edit the existing repo roadmap in place with status-only transitions
170+
- if no roadmap status change is execution-backed, leave roadmap content untouched
171+
- place validation findings in docs/dev/reports
172+
173+
## Acceptance
174+
- no roadmap text deletion
175+
- no roadmap text rewrite
176+
- any roadmap update is status-only unless explicit additive content is required by the PR
177+
- bundle remains docs-only
178+
179+
## Codex Anti-Pattern Guard
180+
181+
These rules are mandatory for every Codex BUILD execution:
182+
183+
- One concept = one name.
184+
- Do not introduce alias variables or remapping chains such as `name1` -> `nameA`.
185+
- Do not create pass-through variables that only copy another variable.
186+
- Do not create `a` -> `b` -> `c` assignment chains.
187+
- Only introduce a variable when it transforms data, improves a complex expression, or is required for control flow.
188+
- Preserve existing meaningful names unless a rename is required for correctness and is applied consistently.
189+
- Do not add abstraction layers, helper functions, or broad refactors unless the BUILD explicitly requires them.
190+
- Do not change unrelated files.
191+
- Before finishing, review the diff and remove unused, redundant, pass-through, or alias variables.
192+
193+
## Current Recovery Lane
194+
195+
The active UAT lane is opening Workspace Manager from a `games/index.html` game tile.
196+
Treat this as a recovery/stabilization PR only. Do not expand into a broader games hub, tool registry, template, or roadmap rewrite.

‎docs/dev/codex_commands.md‎

Lines changed: 1 addition & 48 deletions
Original file line numberDiff line numberDiff line change
@@ -1,48 +1 @@
1-
# Codex Commands
2-
3-
MODEL: GPT-5.4
4-
REASONING: high
5-
6-
## Command
7-
Implement `BUILD_PR_LEVEL_20_1_PHASE20_TOOL_PRESET_INTEGRATION` in `HTML-JavaScript-Gaming` as one small executable PR.
8-
9-
Requirements:
10-
- use numbered sample folders only
11-
- use `samples/phase-20/2001` through `samples/phase-20/2051`
12-
- allocate exactly 3 Phase 20 samples per listed tool
13-
- do not create `samples/phase-20/<tool>` folders
14-
- when a Phase 20 sample is clicked, open the matching tool with that sample's preset data already applied
15-
- fullscreen is already complete; do not modify it
16-
- preserve repo conventions for sample folder contents and sample discovery
17-
- keep the change surgical; do not scan or rewrite unrelated areas
18-
- update roadmap status only if execution-backed and only with marker transitions
19-
20-
Listed tools:
21-
- 3D Asset Viewer
22-
- 3D Camera Path Editor
23-
- 3D JSON Payload Normalizer
24-
- Asset Browser
25-
- Asset Pipeline Tool
26-
- Palette Browser
27-
- Parallax Scene Studio
28-
- Performance Profiler
29-
- Physics Sandbox
30-
- Replay Visualizer
31-
- Sprite Editor
32-
- State Inspector
33-
- Tile Model Converter
34-
- Tilemap Studio
35-
- Vector Asset Studio
36-
- Vector Map Editor
37-
- Workspace Manager
38-
39-
Implementation target:
40-
- executable sample lane under `samples/phase-20`
41-
- clickable sample-to-tool launch path
42-
- preset data applied at open
43-
44-
Validation:
45-
- prove all 51 Phase 20 samples are mapped
46-
- prove each sample opens the correct tool
47-
- prove preset data is visible/applied after open
48-
- place findings in `docs/dev/reports`
1+
Run via your standard injected rules workflow.

0 commit comments

Comments
 (0)