feat: Command Code projectContext, Antigravity in-turn grounding, Cursor native-exec bridge

[yansigit]

Summary

Three independent feature slices, one commit each:

• feat(command-code) — opt-in projectContext envelope for /alpha/generate. New projectContext: "on" on the OAuth command-code provider fills memory (AGENTS.md), taste (.commandcode/taste/taste.md), and skills (SKILL.md under .commandcode/skills, .agents/skills, .pi/skills) from bounded files under process.cwd(). Absent or "off" keeps the empty envelope; the API-key commandcode preset is unaffected and x-taste-learning stays "false". The loader is fail-soft with canonical-path confinement (symlink-escape proof), cap+1 bounded reads with handle cleanup on timeout, a 256-entry scan cap on skill directories, per-file byte caps with XML escaping, and a 128-entry TTL cache that does not evict siblings on refresh. OAuth upsert preserves projectContext, and the Lab behavior fingerprint records wire.commandCodeProjectContext for command-code only.
• feat(antigravity) — in-turn CCA grounding on the main routed fetch. For Antigravity (CCA) Gemini routes, google_search and url_context built-in tools ride the main routed fetch instead of the web-search sidecar loop when the turn has no conflicting Codex function tools. A per-request FIFO emitInTurnGroundingSourcesQueue keeps grounding state isolated across concurrent requests (enqueued only on a successful buildRequest return, shifted in parseStream). The mixed-tool 400 detector requires coexistence language near a function/tool term, so schema-only errors naming a builtin fall through to schema repair. Media/grounding ordering counts media as tool-presence only when the media branch will actually inject this turn. CCA grounding sources are routed through the shared safe-source validator and the search-suggestion HTML filter is gated on the per-request CCA flag.
• feat(cursor) — bridge native exec to Codex shell when nativeLocalExec is off. When nativeLocalExec is not "on" and the turn advertises a bare Codex shell_command or exec_command bridge tool, native Shell/Read/Ls/Grep/Fetch exec frames map to that Codex shell tool call instead of executing on the proxy host; write/delete stay refused. The bridge selector honors the catalog order of CODEX_SHELL_BRIDGE_TOOL_NAMES. Adds the design spec and updates the transports reference and adapter docs across locales.

Verification

• bun run typecheck (strict + replit-gateway): passed.
• Focused suites across all three slices (command-code-project-context, command-code-provider, oauth-upsert-preserves-api-key, config, routing-compatibility-auth-identity, google-wire-compiler, google-vertex-http, gemini-web-search, google-antigravity-wire, cursor-native-exec-bridge): 226/226 pass.
• core-lab-boundary + web-search-loop: 15/15 pass — no Lab import boundary violation, no loop regression.
• Each fix was written TDD (failing test first → minimal fix → green).

Checklist

• Behavior changes in src/ have focused regression tests.
• bun run typecheck passed.
• Focused tests passed.
• Docs synced across locales (providers, sidecars, adapters, configuration/providers).
• No request bodies, API keys, or account identifiers logged.

Fork-only PR against origin/main (yansigit/opencodex). The .superpowers/ scratch directory was deliberately not committed.

Made with Cursor

[github-actions]

✅ Deterministic PR hygiene checks passed.