Point Gemini CLI at AGENTS.md without breaking the extension

[aaddrick]

GEMINI.md is load-bearing, so it stays the style

gemini-extension.json names GEMINI.md as the extension's contextFileName. It is what a Gemini CLI user gets when they run gemini extensions install https://github.com/aaddrick/attention-control. Repurposing it as a repository guide would inject "never edit a generated file" into their sessions — the opposite of the product. The old root AGENTS.md had no such wiring, which is why removing it cost nothing.

The fix

.gemini/settings.json:

{
  "context": {
    "fileName": ["AGENTS.md", "GEMINI.md"]
  }
}

An agent working in this checkout reads the standards and the style. An extension user reads only the style, because project settings resolve from the workspace, so the file is inert inside an installed extension directory.

The alternative I rejected

contextFileName does accept a subpath — extension-manager.ts joins it to the extension path behind an isSubpath guard, and it also accepts an array. So ".gemini/attention-control.md" would free the root name for a third mirror. That trades a working convention for an unusual layout, and neither gemini nor any CI job here can load a Gemini extension, so the break would ship unverified.

Cursor needs nothing — verified

Cursor's rules documentation lists AGENTS.md and CLAUDE.md as project instructions picked up from the root and "always applied to every conversation". .cursor/rules/attention-control.mdc already carries the style with alwaysApply: true. So Cursor gets the standards and the style with no new file.

Also

• CLAUDE.md gains a table of which file each tool reads, and says plainly that GEMINI.md is the shipped artifact rather than a guide. AGENTS.md follows through the generator.
• check_configs.py parses the new settings file: 8 shipped configs.