waypoint-codex 1.0.2 → 1.0.3
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json
CHANGED
|
@@ -98,6 +98,7 @@ Do not optimize for brevity by dropping relevant material.
|
|
|
98
98
|
If a file is relevant, include it in full.
|
|
99
99
|
If multiple files are relevant, include all of them.
|
|
100
100
|
If prior plans, failed attempts, docs, architecture notes, or state files materially change the answer, include them too.
|
|
101
|
+
Do not trim the bundle down to only the files that seem to directly answer the question. Include files that define constraints, history, surrounding system behavior, rejected approaches, current state, or any other context that materially changes how GPT-5.4-Pro should reason.
|
|
101
102
|
|
|
102
103
|
The bottleneck here is not token thrift inside Codex. The bottleneck is giving GPT-5.4-Pro enough real context to reason well.
|
|
103
104
|
|
|
@@ -139,9 +140,13 @@ This is not a fixed checklist. Include whatever materially changes the quality o
|
|
|
139
140
|
|
|
140
141
|
Create `files/` and copy in the relevant source material.
|
|
141
142
|
|
|
143
|
+
The standard is completeness, not minimality.
|
|
144
|
+
If a file materially affects the question, the answer, the constraints, or the reasoning path, include it even when it is only indirectly relevant.
|
|
145
|
+
|
|
142
146
|
Examples of relevant files:
|
|
143
147
|
|
|
144
148
|
- core implementation files
|
|
149
|
+
- supporting files that materially change the reasoning, even if they do not directly answer the question
|
|
145
150
|
- architecture docs
|
|
146
151
|
- plans
|
|
147
152
|
- active plan or workspace files
|