docs/feat: Adaptive Execution Docs & Extension Configuration

[dandye]

Summary

This PR finalizes the Google SecOps Extension by documenting the "Adaptive Execution" strategy and completing the Gemini extension configuration.

Changes

• Documentation: Updated docs/google_secops_extension.md to detail how skills automatically choose between the Remote MCP Server (preferred) and Local Python Tools (fallback).
• Extension Spec: Added extensions/google-secops/GEMINI.md to provide extension-specific documentation.
• Configuration: Updated extensions/google-secops/gemini-extension.json to include:
  • settings: Prompts for PROJECT_ID and SERVER_URL during installation.
  • mcpServers: Dynamic configuration for the remote-mcp-secops server.

Verify

• Check that GEMINI.md correctly references the adaptive nature.
• Validate gemini-extension.json structure for direct use with gemini extensions install.

Test Strategy

1. Ensure not already installed

   gemini extensions list
   ls -la ~/.gemini/extensions/secops/gemini-extension.json

   1.1. Back up existing installation file if desired (useful for tests)

   cp ~/.gemini/extensions/secops/gemini-extension.json{,_$(date +%Y%m%d%H%M%S)}.bak

   1.2 Uninstall if needed

   gemini extensions uninstall google-secops
   gemini extensions list

2. Install the extension

   git clone https://github.com/google/mcp-security  # If starting fresh
   # Or just navigate to your repo
   gemini extensions install ./extensions/google-secops

   You will be prompted for:

   • PROJECT_ID (e.g., secops-ai-staging)
   • SERVER_URL (e.g., https://staging-chronicle.sandbox.googleapis.com/mcp)

3. Verify installation

   gemini extensions list
   ls -la ~/.gemini/extensions/secops/gemini-extension.json

   3.1 Compare with backup

   diff ~/.gemini/extensions/secops/gemini-extension*

4. Re-testing

   gemini extensions uninstall google-secops && gemini extensions install ./extensions/google-secops