Disable unsafe Cursor reviews

[itsjling]

Closes #31.

Summary

• disable Cursor reviews because its CLI cannot enforce the required read-only, no-network, no-tool boundary
• skip Cursor during automatic agent selection and fail clearly when users request it
• report the disabled state through doctor output
• prove that a hostile Cursor snapshot never starts the Cursor process

Verification

• npm run lint
• npm test
• npm run docs:check
• npm run docs:build
• npx fallow audit --base main

Scope

The adapter stays disabled until Cursor offers an enforceable boundary. Other agents keep their current behavior.

Stack

1. Disable unsafe Cursor reviews #51 👈 current
2. Define developer and summary-agent tool profiles #54
3. Preserve good notes when agents or files fail #56

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 56514568d9

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[itsjling]

@codex review

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: ce416471d6

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".