[superche]

Summary

• make npm run codex:dev:app rebuild the Dev gateway, stop only the isolated Dev App, cold-refresh the Dev plugin installation, and relaunch it
• remove all cached versions under the isolated pippit-bridge-dev marketplace before reinstalling
• verify the installed cache hash and registered source against the freshly built gateway bundle
• pin the supported Node executable through PIPPIT_NODE_PATH and reject unsupported development Node versions
• retain codex:dev:app:launch for launching an already-refreshed profile without modifying cache

Root cause

Codex loads an immutable plugin cache snapshot. The previous profile setup repeatedly added the local marketplace and plugin without removing the existing cached snapshot, so a new source build could still be tested against an older manifest, Skill, Widget, or launcher. The GUI App could also resolve an unsupported Node runtime independently of the shell used for bootstrap.

Safety and impact

The cleanup is restricted to ~/.codex-profiles/dev/plugins/cache/pippit-bridge-dev. It rejects unsafe/symlinked cache roots and does not touch the production Codex profile, login/browser data, Pippit accounts, jobs, runtime state, or generated artifacts. A cold restart stops only the ChatGPT main process carrying the exact Dev --user-data-dir marker.

Validation

• npx vitest run scripts/codex-dev-profile.test.ts --configLoader native — 9 tests passed
• npm test — 53 files / 385 tests passed
• npm run lint
• npm run typecheck
• npm run build
• npm run check:architecture
• npm run check:dev-gateway — 17 tools, 2 resources, 2 templates
• two consecutive cold setups in an isolated temporary CODEX_HOME removed an injected stale cache marker and produced matching gateway/cache SHA-256 values
• real Dev profile cold restart replaced PID 73162 with PID 7193; cache and gateway hashes matched and sourceMatches was true

No npm publish or production marketplace activation was performed.