Valid tagged extension not appearing in Extensions Gallery

### URL of the page with the issue

https://geminicli.com/extensions/

### What is the problem?

The `certscore-ai` extension is not appearing in the Gemini CLI Extensions Gallery or its public `extensions.json` registry, although it meets the documented publishing requirements and installs successfully from its GitHub Release.

Extension: `certscore-ai`

Repository:
https://github.com/ergoveritas1-alt/certscore-ai-gemini

Release:
https://github.com/ergoveritas1-alt/certscore-ai-gemini/releases/tag/v0.1.0

Verified repository/release state:

- public GitHub repository
- exact `gemini-cli-extension` topic present
- root-level `gemini-extension.json`
- current `main`: `861da58f6fa789d48adca951db020235da1a9b67`
- tag: `v0.1.0`
- annotated tag resolves to commit `861da58f6fa789d48adca951db020235da1a9b67`
- manifest version at the tagged commit: `0.1.0`
- release published at `2026-08-15T19:09:57Z`
- release is public and marked Latest
- release is not a draft or prerelease

Validation with Gemini CLI 0.55.1 succeeds:

```text
$ gemini extensions validate .
Extension . has been successfully validated.
```

Installation in an isolated temporary Gemini home also succeeds:

```text
$ gemini extensions install https://github.com/ergoveritas1-alt/certscore-ai-gemini --consent --skip-settings

Extension "certscore-ai" installed successfully and enabled.
```

`gemini extensions list --output-format json` reports:

```json
{
"name": "certscore-ai",
"version": "0.1.0",
"installMetadata": {
"source": "https://github.com/ergoveritas1-alt/certscore-ai-gemini",
"type": "github-release",
"releaseTag": "v0.1.0"
},
"isActive": true
}
```

The extension's MCP server starts successfully:

```text
✓ certscore (from certscore-ai): https://mcp.certscore.ai/mcp/light (http) - Connected
```

An MCP `tools/list` request returns the expected three tools:

- `certscore_scan_site`
- `certscore_get_scan_status`
- `certscore_get_scan_bundle`

I checked the live gallery and registry at `2026-08-18T17:01:09Z`, approximately 69 hours and 51 minutes after the release was published.

At that time:

```text
extensions.json last-modified: Tue, 18 Aug 2026 16:10:27 GMT
registry entries: 1496
certscore matches: 0
```

The registry had therefore been rebuilt recently, but the extension remained absent.

Could you check whether `ergoveritas1-alt/certscore-ai-gemini` is being discovered and whether it has an ingestion or crawler-validation error? If there is an additional gallery requirement beyond the current publishing documentation, please let us know.

Current Gemini CLI source marks `httpUrl` deprecated in favor of `url` plus `type: "http"`, while the official validator and installer accept the current manifest and the MCP connection works. If the gallery crawler requires the newer form, it would be helpful to document that requirement or align crawler validation with `gemini extensions validate`.

This appears similar to #28809, #28861, #28208, and #28141. I checked those issues immediately before filing; none contains a confirmed resolution or maintainer explanation that applies to this repository.

### What did you expect to happen?

Per the publishing documentation, a valid public repository with the `gemini-cli-extension` topic, a root manifest, and a release tag should be discovered by the daily crawler and appear in the Extensions Gallery.

### Additional context

No source code, tags, release metadata, repository topics, manifest, or MCP configuration were changed during this verification.

Start by tracing the gallery crawler or registry ingestion path for the repository topic, root-level gemini-extension.json, and v0.1.0 release, then compare its checks with gemini extensions validate and install. Check whether the manifest's deprecated httpUrl form affects ingestion. Done means certscore-ai is accepted by the crawler and appears in extensions.json and the Extensions Gallery.

Written by the indexing model from the issue text.