Skip to content

Commit 46ae8b5

Browse files
author
DavidQ
committed
PLAN PR: replace non-executable shared extraction target map with execution-grade target map requirements. No code changes.
1 parent 805c987 commit 46ae8b5

7 files changed

Lines changed: 143 additions & 14 deletions

docs/dev/CODEX_COMMANDS.md

Lines changed: 11 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,11 @@
1-
MODEL: GPT-5.3-codex
2-
REASONING: high
3-
COMMAND:
4-
Execute BUILD_PR_SHARED_EXTRACTION_02_EXACT_HELPER_MOVE exactly.
5-
Use target map only.
6-
Output zip to <project folder>/tmp/.
1+
# docs/dev/codex_commands.md
2+
3+
No Codex command included.
4+
5+
Reason:
6+
This is a docs-only correction PLAN. The previous BUILD failed because the referenced target map was not executable.
7+
Do not send Codex another BUILD until the target map contains:
8+
- exact source files
9+
- exact destination files
10+
- exact source -> destination mapping
11+
- exact import-update targets

docs/dev/COMMIT_COMMENT.txt

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1 +1 @@
1-
BUILD PR: exact helper move to src/shared using target map.
1+
PLAN PR: replace non-executable shared extraction target map with execution-grade target map requirements. No code changes.

docs/dev/NEXT_COMMAND.txt

Lines changed: 8 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1 +1,8 @@
1-
Proceed to APPLY_PR after validation.
1+
Next step:
2+
Create an executable replacement for PLAN_PR_SHARED_EXTRACTION_02_TARGET_MAP with:
3+
1. exact source file list
4+
2. exact destination file list
5+
3. exact source->destination mapping
6+
4. exact import-update targets
7+
8+
Do not issue another BUILD until all four are explicit.
Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1 +1,3 @@
1-
Helper extraction to shared.
1+
Created a docs-only correction PLAN after BUILD fail-fast.
2+
Recorded the exact blocker and defined the minimum execution-grade target map structure required before retrying BUILD.
3+
No code changes. No file moves. No runtime claims.

docs/dev/reports/file_tree.txt

Lines changed: 11 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1 +1,11 @@
1-
src/shared populated per target map
1+
docs/
2+
pr/
3+
PLAN_PR_SHARED_EXTRACTION_02_EXECUTABLE_TARGET_MAP.md
4+
dev/
5+
codex_commands.md
6+
commit_comment.txt
7+
next_command.txt
8+
reports/
9+
change_summary.txt
10+
validation_checklist.txt
11+
file_tree.txt
Lines changed: 15 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,15 @@
1-
- Matches target map
2-
- No duplicates
3-
- Imports updated
4-
- Build passes
1+
SESSION VALIDATION GATE
2+
- Bundle type: PLAN
3+
- One PR purpose only: yes
4+
- BUILD command included: no
5+
- Repo scan requested: no
6+
- Vague execution language present: no
7+
- Code claims made: no
8+
- Start-of-day directories touched: no
9+
- ZIP repo-structured: yes
10+
11+
PLAN-SPECIFIC CHECKS
12+
- Exact blocker captured: yes
13+
- Next required artifact defined: yes
14+
- Non-goals explicit: yes
15+
- Prevents premature BUILD retry: yes
Lines changed: 94 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,94 @@
1+
# PLAN_PR_SHARED_EXTRACTION_02_EXECUTABLE_TARGET_MAP
2+
3+
## Purpose
4+
Replace the non-executable target map with an execution-grade target map for shared-helper extraction.
5+
6+
This PLAN exists because `BUILD_PR_SHARED_EXTRACTION_02_EXACT_HELPER_MOVE` failed the BUILD fail-fast rule:
7+
the referenced target map does not provide enough explicit information to execute without guessing.
8+
9+
## Current Blocker
10+
The current target map is not executable because it does **not** provide all of the following:
11+
12+
1. Exact source file list
13+
2. Exact destination file list
14+
3. Exact source -> destination mapping
15+
4. Exact import-update targets
16+
17+
Because those details are missing, any attempted execution would require guessing, which is not allowed.
18+
19+
## Scope
20+
This PR purpose is **only** to define the execution-grade target map requirements and replacement structure.
21+
It does **not** execute moves.
22+
It does **not** change runtime code.
23+
It does **not** change engine APIs.
24+
25+
## Required Replacement Artifact
26+
Create or replace the target map with a document that contains these four sections exactly:
27+
28+
### 1) Exact Source Files
29+
List each source file that currently contains a duplicate helper.
30+
31+
Required format:
32+
33+
- `source_file: <repo-relative path>`
34+
- `helpers_in_file: [<helper_1>, <helper_2>, ...]`
35+
36+
### 2) Exact Destination Files
37+
List each destination file under `src/shared` that will own moved helpers.
38+
39+
Required format:
40+
41+
- `destination_file: <repo-relative path>`
42+
- `helpers_owned: [<helper_1>, <helper_2>, ...]`
43+
44+
### 3) Exact Source -> Destination Mapping
45+
List every helper move individually.
46+
47+
Required format:
48+
49+
- `helper: <helper_name>`
50+
- `from: <repo-relative source file>`
51+
- `to: <repo-relative destination file>`
52+
53+
### 4) Exact Import Update Targets
54+
List every file whose imports must change because of the move.
55+
56+
Required format:
57+
58+
- `consumer_file: <repo-relative path>`
59+
- `remove_import_from: <old path or inline/local helper reference>`
60+
- `add_import_from: <new shared path>`
61+
- `helpers: [<helper_1>, <helper_2>, ...]`
62+
63+
## Mandatory Constraints
64+
- DO NOT scan the repo
65+
- ONLY use explicitly listed files
66+
- NO engine API changes
67+
- NO new files unless explicitly listed
68+
- One PR purpose only
69+
- No guessing
70+
- No fallback wording such as "as needed", "if found", or "scan for duplicates"
71+
72+
## Execution Readiness Gate
73+
The replacement target map is executable only if all answers below are **yes**:
74+
75+
- Are all source files explicitly listed?
76+
- Are all destination files explicitly listed?
77+
- Does every helper have one exact `from` and one exact `to`?
78+
- Are all import update targets explicitly listed?
79+
- Can Codex execute the moves without opening unrelated files or discovering anything?
80+
81+
If any answer is **no**, stop and do not issue a BUILD.
82+
83+
## Non-Goals
84+
- No helper movement
85+
- No import edits
86+
- No refactors
87+
- No renames
88+
- No logic changes
89+
- No validation claims about code
90+
91+
## Next Allowed Step
92+
Only after this executable target map exists should the workflow proceed to:
93+
94+
`BUILD_PR_SHARED_EXTRACTION_02_EXACT_HELPER_MOVE`

0 commit comments

Comments
 (0)