fix(#648): move Antigravity into the screen-checked group in five more docs

docs/api-reference.md (the signal notes and the idle/working rows), and the
wiki's Notifications-And-Approvals, Keeping-Agents-Running and Troubleshooting
pages, plus docs/grok-integration.md, still called Antigravity's working and
idle status unreliable. It now declares a working line and prompt marker like
Codex, OpenCode, Gemini, Pi and OMP, so only Grok stays on generic cues. The
Troubleshooting entry for a session stuck showing busy also says that an
Antigravity session waiting on a shell-command approval shows busy until it is
answered, and the API reference says the same of its idle signal.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

docs/wiki/Notifications-And-Approvals.md

@@ -39,8 +39,8 @@ hooks, but its dialogs are distinctive enough to read off the screen, so a Codex
 waiting on an approval, a question or the "Trust this folder?" prompt turns red too, and
 clears a few seconds after you answer. For the other CLIs there are no hooks and no dialog
 reading, so you get only the coarser working and idle state: read off the screen for
-OpenCode, Gemini CLI, Pi and OMP, and unreliable for Antigravity and Grok Build, which
-declare nothing Codeman can read it from.
+OpenCode, Gemini CLI, Pi, OMP and Antigravity, and unreliable for Grok Build, which
+declares nothing Codeman can read it from.
 
 ## Window title and OS notifications