Contributions should preserve the project's core boundary: user-level, reversible patches that do not modify or repackage app.asar, session JSONL, SQLite databases, or permanent Windows proxy settings.
- Fork the repository and create a focused branch.
- Keep compatibility changes minimal and avoid unrelated refactors.
- Do not commit
.env, logs, databases, local handovers, credentials, screenshots with private data, or installed runtime copies. - Update the affected component version and README when behavior changes.
From the repository root, run:
node --test `
'.\reasoning-labels\reasoning-label-renderer.test.mjs' `
'.\subagent-status\completion-evidence.test.mjs' `
'.\subagent-status\subagent-status-renderer.test.mjs' `
'.\shared\codex-devtools-transport.test.mjs'
& '.\network-proxy\manage-hotpatch.tests.ps1'
& '.\network-proxy\network-health.tests.ps1'
& '.\network-proxy\network-runtime-observer.tests.ps1'
& '.\network-proxy\install-rollback.tests.ps1'For user-visible UI changes, also verify the affected menu or panel in a running Codex instance. Network changes require targeted Status/Doctor evidence and must preserve the official compatibility fallback.
Explain the reproduced problem, the smallest behavioral change, validation results, and remaining compatibility risk. Never include secrets or private runtime evidence in the pull request.