Update JetBrains inspection instructions for skill helper

[cbusillo]

Objective

Update repo instructions that still hard-code the old Every Code JetBrains MCP tool workflow now that cbusillo/codex-skills#62 has landed the jetbrains-inspection skill/helper path.

Stale References Found

• README.md:183-184 currently says:
  • inspection_trigger(scope="whole_project")
  • inspection_get_problems()
• AGENTS.md:48 currently instructs agents to trigger inspections with inspection_trigger(scope="whole_project") and review via inspection_get_problems.
• AGENTS.md:129 has a readiness checklist item for inspection_trigger(scope="whole_project") / inspection_get_problems().

Desired Update

Replace Every Code user-workflow guidance with the skill/helper workflow, for example:

uv run ~/.code/skills/jetbrains-inspection/scripts/jb-inspect.py run --repo "$PWD" --scope changed_files

Use whole_project only when repo policy requires it or when validating a broad change. Keep repo-specific guidance about .github/github.json, preferred IDE, and inspection scope if present.

Acceptance Criteria

• Instructions no longer tell Every Code agents to call inspection_trigger, inspection_get_problems, inspection_wait, or other MCP tools for the normal readiness path.
• Instructions point to the jetbrains-inspection skill/helper and say that findings, stale results, capture_incomplete, timeouts, or wrong-worktree routing are not clean.
• Existing MCP documentation is retained only if this repo intentionally documents MCP behavior for non-Code clients.
• Link back to cbusillo/codex-skills#52 when fixed so the local clone sweep can close cleanly.

Context

This was found during the local cloned-repo sweep tracked by cbusillo/codex-skills#52. jetbrains-inspection-api keeps its MCP server for non-Code clients and rollback, but Every Code should prefer the skill/helper path after codex-skills#62.