Enhance project instructions with tool architecture, formatting, and ZIP requirements - PR_26126_052-project-instructions-enhancements

Author: DavidQ

docs/dev/PROJECT_INSTRUCTIONS.md

@@ -461,4 +461,53 @@ Do not compact:
 - nested arrays
 - complex structures
 
-Do not change JSON contracts or semantics while applying array formatting.
+Do not change JSON contracts or semantics while applying array formatting.
+
+## PROJECT INSTRUCTIONS LOCATION
+
+PROJECT_INSTRUCTIONS.md lives at:
+
+`docs/dev/PROJECT_INSTRUCTIONS.md`
+
+Codex must always read `docs/dev/PROJECT_INSTRUCTIONS.md` from this path as the source of truth before executing repository workflow instructions.
+
+## CODEX COMMAND FORMATTING RULE
+
+All Codex commands must be multi-line and human-readable.
+
+Do not provide single-line Codex commands.
+
+Codex commands must use these sections:
+
+Changes:
+
+Validation:
+
+Required reports:
+
+## REQUIRED ZIP OUTPUT
+
+Codex must ALWAYS produce a repo-structured ZIP for every PR.
+
+The ZIP must follow the existing CODEX ZIP STANDARD.
+
+The ZIP is required output, not optional.
+
+## HTML FILE RESTRICTIONS
+
+Never allow `<script>` blocks inside HTML files.
+
+Never allow `<style>` blocks inside HTML files.
+
+All JavaScript must be external.
+
+All CSS must be external.
+
+## TOOL ARCHITECTURE STANDARDS
+
+- One class per file.
+- One control or section per class.
+- App/root class is coordinator only and must not own DOM logic or business logic.
+- No `tools/shared` dependency is allowed.
+- Shared UI behavior must use reusable classes.
+- Do not duplicate shared UI behavior logic across controls or tools.