repo-harness-chatgpt-browser

# repo-harness ChatGPT Browser Use this skill when the user asks to consult ChatGPT Web, GPT Pro, browser GPT, or a logged-in ChatGPT account through repo-harness. ## Rules 1. This uses the user's logged-in ChatGPT Web browser session, not the OpenAI API. 2. Do not ask for or handle passwords, SSO secrets, 2FA codes, cookies, browser storage, or tokens. 3. Before a non-dry-run consult, state that it may create or continue a real ChatGPT Web conversation. 4. Prefer dry-run first when files are involved: ```bash repo-harness chatgpt browser-consult --repo . --dry-run --prompt "<prompt>" --file <path> ``` 5. For Oracle provider readiness, run: ```bash repo-harness chatgpt browser-doctor --repo . --provider oracle --json ``` 6. Oracle's published CLI requires `node >=24`, but that requirement belongs to the resolved Oracle binary. Do not raise repo-harness' overall runtime floor or add Oracle as an implicit dependency just for a GPT Pro consult. If the Oracle doctor reports `nodeCompatible:false`, fix the Oracle install/runtime and rerun doctor. 7. If the Oracle doctor JSON includes `agent_actions` such as `chatgpt-oracle-install-pinned`, `chatgpt-oracle-upgrade-pinned`, or `chatgpt-oracle-fix-configured-source`, run them only when the user has explicitly asked to set up or repair GPT Pro browser consults. Do not run Oracle bootstrap from default repo-harness install or unrelated setup checks. 8. If the user wants Oracle to use an existing signed-in Chrome profile, record ...