Rename Codex runtime prompt snapshot directory#76274
Conversation
|
Codex review: needs maintainer review before merge. Summary Reproducibility: yes. for the prior review finding: Next step before merge Security Review detailsBest possible solution: Merge the rename after maintainer review and exact-head CI confirm the generator, fixtures, tests, and docs stay in sync. Do we have a high-confidence way to reproduce the issue? Yes for the prior review finding: Is this the best way to solve the issue? Yes. Updating the shared fixture-directory constant, generator stale-file logic, drift tests, fixtures, and docs is the narrow maintainable path; the latest generator change also makes the Markdown formatting intentional rather than ad hoc. What I checked:
Likely related people:
Remaining risk / open question:
Codex review notes: model gpt-5.5, reasoning high; reviewed against ae82a39150f9. |
55057bd to
13a1c19
Compare
* 'main' of https://github.com/openclaw/openclaw: Rename Codex runtime prompt snapshot directory (#76274) fix(plugins): canonicalize install provenance paths
* test: rename Codex runtime prompt snapshots * test: refresh prompt snapshots with node24 * test: format prompt snapshot markdown in generator
* test: rename Codex runtime prompt snapshots * test: refresh prompt snapshots with node24 * test: format prompt snapshot markdown in generator
* 'main' of https://github.com/openclaw/openclaw: Rename Codex runtime prompt snapshot directory (openclaw#76274) fix(plugins): canonicalize install provenance paths
The prompt snapshot fixtures started out under a generic
happy-pathdirectory. After adding the reconstructed Codex runtime prompt layers, that name became too broad: the snapshots are specifically for the Codex runtime happy path, not every OpenClaw happy path.This renames the fixture directory to
codex-runtime-happy-pathand updates the generator, tests, and docs to use the more precise path. The snapshot contents stay the same aside from generated path metadata.