=== project/home/.gemini/antigravity/knowledge/gortex-workflow/artifacts/gortex-instructions.md ===
---
type: "Knowledge Item"
description: "Mandatory Gortex public-tool workflow"
---

## MANDATORY: Use Gortex MCP tools instead of Read/Grep

For every coding task:

1. Call `explore` first with the complete task. Work from the returned source and call paths; do not reopen them with file or shell tools.
2. Inspect indexed code only with `search`, `read`, `relations`, and `trace`. Never use Read/Grep/Glob or shell equivalents for indexed source.
3. Before mutation, call `change(operation:"impact")`; for a signature change, also call `change(operation:"verify")` with the proposed signature. Mutate only with `edit` or `refactor`. After mutation, call `change(operation:"detect")`, then use its symbol IDs with `change(operation:"tests")`, `change(operation:"guards")`, and `change(operation:"contract")`.
4. Call `capabilities` only when you need the exact fields for an operation.

Common calls:

- `search({operation:"symbols", query:"<name or concept>"})`
- `read({target:{symbol:"<file>::<Name|Recv.Name>"}})`
- `relations({operation:"usages", target:{symbol:"<id>"}})`
- `edit({target:{file:"<path>"}, match:"<old>", replacement:"<new>"})`

If the Gortex server is configured but these tools are missing from the callable MCP tools, report a Gortex MCP integration failure and stop. Do not start a daemon or switch to a CLI/shell fallback.

Use `recall` before revisiting prior work and `remember` immediately for durable decisions, invariants, or gotchas.
=== project/home/.gemini/antigravity/knowledge/gortex-workflow/metadata.json ===
{
  "summary": "MANDATORY: Use native Gortex MCP tools for indexed code. If configured tools are missing, report an MCP integration failure; do not start a daemon or use a CLI fallback.",
  "references": ["artifacts/gortex-instructions.md"]
}
=== project/home/.gemini/antigravity/mcp_config.json ===
{
  "mcpServers": {
    "gortex": {
      "args": [
        "mcp"
      ],
      "command": "gortex",
      "env": {
        "GORTEX_INDEX_WORKERS": "8"
      }
    }
  }
}
=== project/home/.gemini/settings.json ===
{
  "hooks": {
    "AfterTool": [
      {
        "hooks": [
          {
            "command": "gortex hook --agent antigravity",
            "description": "Gortex graph context + stale-index hint",
            "name": "gortex",
            "timeout": 10000,
            "type": "command"
          }
        ],
        "matcher": "run_shell_command|search_file_content|glob"
      }
    ],
    "SessionStart": [
      {
        "hooks": [
          {
            "command": "gortex hook --agent antigravity",
            "description": "Gortex session orientation",
            "name": "gortex",
            "timeout": 10000,
            "type": "command"
          }
        ]
      }
    ]
  }
}
=== global/home/.gemini/antigravity/knowledge/gortex-workflow/artifacts/gortex-instructions.md ===
---
type: "Knowledge Item"
description: "Mandatory Gortex public-tool workflow"
---

## MANDATORY: Use Gortex MCP tools instead of Read/Grep

For every coding task:

1. Call `explore` first with the complete task. Work from the returned source and call paths; do not reopen them with file or shell tools.
2. Inspect indexed code only with `search`, `read`, `relations`, and `trace`. Never use Read/Grep/Glob or shell equivalents for indexed source.
3. Before mutation, call `change(operation:"impact")`; for a signature change, also call `change(operation:"verify")` with the proposed signature. Mutate only with `edit` or `refactor`. After mutation, call `change(operation:"detect")`, then use its symbol IDs with `change(operation:"tests")`, `change(operation:"guards")`, and `change(operation:"contract")`.
4. Call `capabilities` only when you need the exact fields for an operation.

Common calls:

- `search({operation:"symbols", query:"<name or concept>"})`
- `read({target:{symbol:"<file>::<Name|Recv.Name>"}})`
- `relations({operation:"usages", target:{symbol:"<id>"}})`
- `edit({target:{file:"<path>"}, match:"<old>", replacement:"<new>"})`

If the Gortex server is configured but these tools are missing from the callable MCP tools, report a Gortex MCP integration failure and stop. Do not start a daemon or switch to a CLI/shell fallback.

Use `recall` before revisiting prior work and `remember` immediately for durable decisions, invariants, or gotchas.
=== global/home/.gemini/antigravity/knowledge/gortex-workflow/metadata.json ===
{
  "summary": "MANDATORY: Use native Gortex MCP tools for indexed code. If configured tools are missing, report an MCP integration failure; do not start a daemon or use a CLI fallback.",
  "references": ["artifacts/gortex-instructions.md"]
}
=== global/home/.gemini/antigravity/mcp_config.json ===
{
  "mcpServers": {
    "gortex": {
      "args": [
        "mcp"
      ],
      "command": "gortex",
      "env": {
        "GORTEX_INDEX_WORKERS": "8"
      }
    }
  }
}
=== global/home/.gemini/settings.json ===
{
  "hooks": {
    "AfterTool": [
      {
        "hooks": [
          {
            "command": "gortex hook --agent antigravity",
            "description": "Gortex graph context + stale-index hint",
            "name": "gortex",
            "timeout": 10000,
            "type": "command"
          }
        ],
        "matcher": "run_shell_command|search_file_content|glob"
      }
    ],
    "SessionStart": [
      {
        "hooks": [
          {
            "command": "gortex hook --agent antigravity",
            "description": "Gortex session orientation",
            "name": "gortex",
            "timeout": 10000,
            "type": "command"
          }
        ]
      }
    ]
  }
}
