GeminiCLI.com Feedback: tagged extension with `gemini-cli-extension` topic not indexed in the Extensions Gallery after 4+ daily crawls

### URL of the page with the issue

https://geminicli.com/extensions/

### What is the problem?

My extension repository https://github.com/machouz/ifillpdf-gemini-extension is not indexed in the Extensions Gallery (checked https://geminicli.com/extensions.json — 1486 entries, no match for "ifillpdf"), although it meets all the documented requirements from https://geminicli.com/docs/extensions/releasing/:

- Public GitHub repository
- GitHub topic `gemini-cli-extension` present (since 2026-07-27)
- `gemini-extension.json` at the repository root
- Lowercase extension name (`ifillpdf`), stable version `1.0.0`
- Git tag `v1.0.0` present (created 2026-08-13, i.e. 4+ daily crawls ago)

Current manifest:

```json
{
"name": "ifillpdf",
"version": "1.0.0",
"description": "Detect the fillable fields of any PDF with AI — including scans with no AcroForm — then fill and sign it.",
"mcpServers": {
"ifillpdf": {
"httpUrl": "https://mcp.ifillpdf.com/mcp",
"authProviderType": "dynamic_discovery"
}
}
}
```

`authProviderType: "dynamic_discovery"` is a valid value of the `AuthProviderType` enum in `packages/core/src/config/config.ts`.

The underlying remote MCP server (streamable-http at https://mcp.ifillpdf.com/mcp) is also published in the official MCP registry as `com.ifillpdf/pdf`.

This looks similar to #28208 (PandaDoc, also tagged and still not indexed).

Could you check whether `machouz/ifillpdf-gemini-extension` is being discovered by the gallery crawler, and if it is discovered but skipped, share the validation reason so I can fix the repository?

### What did you expect to happen?

I expected `machouz/ifillpdf-gemini-extension` to be picked up by the daily crawler within 24-48h of tagging (per the releasing guide: "Our system crawls tagged repositories daily. Once you tag your repository, your extension will appear in the gallery if it passes validation") and to appear in the gallery at https://geminicli.com/extensions/ and in https://geminicli.com/extensions.json.

### Additional context

_No response_

Start with the extension releasing guide and packages/core/src/config/config.ts, then compare the repository's manifest, topic, and tag with the published extensions.json output. Trace the gallery discovery and validation entry points to determine whether the repository is skipped or never discovered. Done means the extension appears in the gallery, or the validation reason is clearly exposed.

Written by the indexing model from the issue text.