GeminiCLI.com Feedback: kyisaiah47/kynth-gemini-extension missing from extensions.json despite a fresh crawl and a clean extensions validate

### URL of the page with the issue

https://geminicli.com/extensions/ (and https://geminicli.com/extensions.json)

### What is the problem?

[`kyisaiah47/kynth-gemini-extension`](https://github.com/kyisaiah47/kynth-gemini-extension) is not in the gallery or in `extensions.json`, although it satisfies every requirement in [docs/extensions/releasing.md](https://github.com/google-gemini/gemini-cli/blob/main/docs/extensions/releasing.md) and has done since 2026-07-24 at the latest.

**Requirements, each checked today (2026-08-14):**

1. Public repository — `visibility=PUBLIC`, `archived=false`, `fork=false`, `disabled=false`.
2. `gemini-cli-extension` topic present, and discoverable through the topic search the crawler uses:
```
$ gh api "search/repositories?q=topic:gemini-cli-extension+user:kyisaiah47" --jq '.total_count, (.items[].full_name)'
1
kyisaiah47/kynth-gemini-extension
```
3. `gemini-extension.json` at the absolute repository root, and it validates against the CLI itself:
```
$ npx @google/gemini-cli --version
0.55.1
$ git clone --depth 1 https://github.com/kyisaiah47/kynth-gemini-extension.git kge
$ npx @google/gemini-cli extensions validate "$PWD/kge"
Extension /.../kge has been successfully validated.
```

**Evidence it is absent from a fresh crawl, not a stale file:**

```
$ curl -sI https://geminicli.com/extensions.json | grep -i last-modified
last-modified: Fri, 14 Aug 2026 13:10:13 GMT

$ curl -s "https://geminicli.com/extensions.json?cb=$(date +%s)" -o g.json
$ node -e "const e=require('./g.json');
console.log('count', e.length);
console.log('newest', e.map(x=>x.lastUpdated||'').sort().pop());
console.log('kyisaiah hits', (JSON.stringify(e).match(/kyisaiah/gi)||[]).length)"
count 1472
newest 2026-08-14T13:04:24Z
kyisaiah hits 0
```

The index was rebuilt today and its newest entry is six minutes before the rebuild, so the indexer is running normally — it is simply excluding this repository.

I also checked the properties that separate it from the 1472 entries that *are* indexed, and found none that would explain the exclusion: 455 indexed entries have 0 stars (this repo has 0), 306 have no license (this one is MIT), 627 carry `hasMCP` (so an MCP-only extension is not the problem), and indexed third-party repos such as `3d-era/munin-gemini-extension` have no GitHub releases either, so a release tag does not appear to be required. The manifest name (`kynth-core`) differs from the repository name, which is also true of indexed entries — `avivlyweb/pubmed-gemini-extension` publishes as `nagomi`.

### What did you expect to happen?

`kyisaiah47/kynth-gemini-extension` should appear in `extensions.json` and in the gallery on the next crawl, as the releasing doc says a tagged, valid, public repository will.

### Additional context

This looks like the same crawler-exclusion class as #28208 (open), #28141, #27838 and #21900 — a repository that passes local validation and every documented requirement, which a fresh crawl skips. Those earlier reports were each asked for a CLI version and then auto-closed after 14 days, so to save that round trip: **CLI version 0.55.1**, and the local `extensions validate` output is quoted above.

The indexer is an external service rather than code in this repository, but the releasing doc names this as the discovery surface and the gallery's own Feedback link points here, so I am filing it here. Happy to supply anything else that helps — repository, manifest and crawl output are all public.

Read docs/extensions/releasing.md and inspect the gallery/indexing entry points that produce extensions.json; the report identifies the external crawler as the likely boundary. Reproduce the crawl or trace its exclusion criteria using the listed repository and CLI validation command. Done means the repository is indexed and shown in the gallery, or the applicable exclusion is documented.

Written by the indexing model from the issue text.