Repair master roadmap using additive and move-only rules

DavidQ · DavidQ · commit 902dfd0492f5 · 2026-04-14T18:38:54.000-04:00
BUILD_PR_ROADMAP_REPAIR_ADDITIVE_MOVE_ONLY
diff --git a/docs/dev/CODEX_COMMANDS.md b/docs/dev/CODEX_COMMANDS.md
@@ -2,29 +2,40 @@ MODEL: GPT-5.4
 REASONING: high
 
 COMMAND:
-Create `BUILD_PR_LEVEL_11_2_COMBINED_RUNTIME_DIRECTION_AND_RULE_MOVE_GUARDS` as one combined Level 11 setup PR.
+Create `BUILD_PR_ROADMAP_REPAIR_ADDITIVE_MOVE_ONLY`.
 
-Goals:
-1. Define and prepare the next core runtime direction in one compact PR.
-2. Add an explicit migration guard for any future roadmap/instruction cleanup.
+Repair:
+`docs/dev/roadmaps/MASTER_ROADMAP_HIGH_LEVEL.md`
 
-Required rules:
-- if roadmap content is being moved to PROJECT_INSTRUCTIONS.md, MOVE it; do not simply delete it
-- destination text must exist before source text is removed
-- preserve wording unless the PR explicitly requires rewriting
-- roadmap handling remains status-only unless explicitly requested otherwise
-- do not delete roadmap content during cleanup work
+Hard rules:
+- NO delete
+- NO text rewrite
+- NO summarization
+- ONLY adds, moves, and status marker updates
+- preserve every existing roadmap line somewhere in the repaired file
+
+Required actions:
+1. Repair roadmap structure using MOVE operations first
+2. Preserve all existing text exactly as written
+3. If duplicated/appended content exists:
+   - move it into the correct location when clear
+   - otherwise preserve it in an additive `Recovery / Preserved Content` section
+4. Productization-rule style content:
+   - move to the correct policy/instruction area if touched
+   - do not delete
+   - do not rewrite
+5. Update status markers only where execution truth clearly supports it
+6. Do not change any other wording
 
-Outputs:
-- compact PR doc
-- any required docs updates for Level 11 direction
-- validation notes
-- repo-structured ZIP
+Validation output must explicitly confirm:
+- no roadmap text deleted
+- no roadmap wording changed
+- only adds, moves, and status updates were used
 
 Final packaging step is REQUIRED:
-`<project folder>/tmp/BUILD_PR_LEVEL_11_2_COMBINED_RUNTIME_DIRECTION_AND_RULE_MOVE_GUARDS.zip`
+`<project folder>/tmp/BUILD_PR_ROADMAP_REPAIR_ADDITIVE_MOVE_ONLY.zip`
 
 Hard rules:
-- combine work to reduce PR count
+- roadmap repair only
 - no unrelated repo changes
 - no missing ZIP
diff --git a/docs/dev/COMMIT_COMMENT.txt b/docs/dev/COMMIT_COMMENT.txt
@@ -1,2 +1,2 @@
-Combine Level 11 runtime direction setup and add move-not-delete roadmap guard
-BUILD_PR_LEVEL_11_2_COMBINED_RUNTIME_DIRECTION_AND_RULE_MOVE_GUARDS
+Repair master roadmap using additive and move-only rules
+BUILD_PR_ROADMAP_REPAIR_ADDITIVE_MOVE_ONLY
diff --git a/docs/dev/NEXT_COMMAND.txt b/docs/dev/NEXT_COMMAND.txt
@@ -1 +1 @@
-BUILD_PR_LEVEL_11_3_COMBINED_RUNTIME_FOUNDATION
+BUILD_PR_LEVEL_01_STRUCTURE_FINALIZATION_AND_ROADMAP_CORRECTION
diff --git a/docs/dev/reports/change_summary.txt b/docs/dev/reports/change_summary.txt
@@ -1,3 +1,4 @@
-- Combined the next Level 11 setup work to reduce PR count
-- Added explicit move-not-delete guard for future roadmap/instruction migrations
-- Kept roadmap handling status-only unless explicitly requested otherwise
+- Added strict roadmap-repair bundle
+- Enforced no-delete and no-text-change rules
+- Limited Codex to adds, moves, and status-marker updates only
+- Added recovery section fallback to preserve uncertain content rather than deleting it
diff --git a/docs/dev/reports/validation_checklist.txt b/docs/dev/reports/validation_checklist.txt
@@ -1,6 +1,7 @@
-- Combined PR reduces follow-on PR count
-- Rule-migration guard is explicit
-- Roadmap cleanup cannot silently delete moved content
-- Outputs remain docs-first and repo-structured
+- No roadmap text deleted
+- No roadmap wording changed
+- Only adds, moves, and status-marker updates used
+- Duplicated/appended content preserved and relocated
+- Recovery / Preserved Content section used if placement uncertainty remained
 - Output ZIP created at:
-  <project folder>/tmp/BUILD_PR_LEVEL_11_2_COMBINED_RUNTIME_DIRECTION_AND_RULE_MOVE_GUARDS.zip
+  <project folder>/tmp/BUILD_PR_ROADMAP_REPAIR_ADDITIVE_MOVE_ONLY.zip
diff --git a/docs/dev/roadmaps/MASTER_ROADMAP_HIGH_LEVEL.md b/docs/dev/roadmaps/MASTER_ROADMAP_HIGH_LEVEL.md
@@ -634,6 +634,9 @@
 
 - [x] relocate active template surfaces to `tools/templates/` and remove the empty root `templates/` directory
 
+---
+
+## Recovery / Preserved Content
 # MASTER ROADMAP HIGH LEVEL (status updates only)
 
 [.] asset naming normalization
diff --git a/docs/pr/BUILD_PR_ROADMAP_REPAIR_ADDITIVE_MOVE_ONLY.md b/docs/pr/BUILD_PR_ROADMAP_REPAIR_ADDITIVE_MOVE_ONLY.md
@@ -0,0 +1,84 @@
+# BUILD_PR_ROADMAP_REPAIR_ADDITIVE_MOVE_ONLY
+
+## Purpose
+Repair `docs/dev/roadmaps/MASTER_ROADMAP_HIGH_LEVEL.md` under strict additive/move-only rules.
+
+## Non-negotiable rules
+- NO delete
+- NO text rewrite
+- NO summarization
+- NO compression/shortening
+- NO line replacement except status marker updates where explicitly needed
+- ONLY allow:
+  - adds
+  - moves
+  - status marker updates
+
+## Intent
+The roadmap currently has drift and appended/duplicated content.
+This PR repairs structure while preserving all existing roadmap text.
+
+## Required approach
+
+### A. Preserve all text
+- Every existing roadmap line must survive somewhere in the repaired file
+- If text is in the wrong place, MOVE it
+- Do not delete duplicated/appended content; relocate it to the correct place or preserve it in an explicit additive holding section if exact placement is uncertain
+
+### B. No wording changes
+- Keep wording exactly as-is
+- Do not normalize spelling
+- Do not rephrase
+- Do not "clean up" text
+
+### C. Status-only updates
+- Status markers may be updated where execution truth clearly supports it
+- No surrounding text changes
+
+### D. Productization rule handling
+- If rule text is currently in the roadmap in a task-like place, MOVE it to the correct policy/instruction area in the roadmap or preserve it in an additive policy section
+- Do not delete it
+- Do not rewrite it
+
+### E. Duplicate / appended content handling
+- If the roadmap has duplicated headings or appended fragments, MOVE them into the correct section or into an additive recovery section at the end
+- Do not delete the content
+- Do not rewrite the content
+
+### F. Recovery-first rule
+If Codex cannot confidently place a line into its exact intended location:
+- preserve it in an additive `Recovery / Preserved Content` section at the bottom
+- do not delete it
+- do not rewrite it
+
+## Validation requirements
+Codex must report:
+- lines/sections moved
+- lines/sections added
+- any status markers updated
+- confirmation that no roadmap text was deleted
+- confirmation that no roadmap wording was changed
+
+## Packaging requirement
+Codex must package all changed files into:
+`<project folder>/tmp/BUILD_PR_ROADMAP_REPAIR_ADDITIVE_MOVE_ONLY.zip`
+
+## Scope guard
+- roadmap repair only
+- docs-first
+- no unrelated repo changes
+
+## Applied delta
+- Added structural containment at the roadmap tail:
+  - `---`
+  - `## Recovery / Preserved Content`
+- Preserved and retained the appended status fragment directly under that section with exact original wording:
+  - `# MASTER ROADMAP HIGH LEVEL (status updates only)`
+  - `[.] asset naming normalization`
+  - `[.] manifest discovery`
+  - `[x] fullscreen bezel overlay system (low priority, before next game)`
+
+## Validation output
+- no roadmap text deleted: confirmed (`MISSING_COUNT=0` in before/after line-preservation check)
+- no roadmap wording changed: confirmed (roadmap diff shows additive insertion only; no modified/deleted wording lines)
+- only adds, moves, and status updates were used: confirmed (this repair used additive structural placement only; no status markers changed)

Original file line number	Diff line number	Diff line change
`@@ -1 +1 @@`
`1`		`-BUILD_PR_LEVEL_11_3_COMBINED_RUNTIME_FOUNDATION`
	`1`	`+BUILD_PR_LEVEL_01_STRUCTURE_FINALIZATION_AND_ROADMAP_CORRECTION`