— drives repeated duplicate issue filing
Description: Today's GEO Audit Report (discussion #53758) claims llms_txt scores 0/18 with found: false at https://github.github.com/gh-aw/llms.txt, and "No AI Discovery signals" (0/6) on the docs site for /.well-known/ai.txt, /ai/summary.json, /ai/faq.json, /ai/service.json. Live verification during this analysis shows all of these URLs return HTTP 200 with correct, real content:
https://github.github.com/gh-aw/llms.txt → 200 (served by the Astro dynamic route docs/src/pages/llms.txt.ts)https://github.github.com/gh-aw/.well-known/ai.txt → 200https://github.github.com/gh-aw/ai/summary.json → 200
The report itself already diagnosed the same class of bug for robots_txt this cycle ("the scanner probes the domain root... rather than the /gh-aw/ project-site base path") but did not extend that root-cause reasoning to the llms_txt/ai_discovery checks, which are also false negatives. This scanner bug is very likely the direct cause of at least 4 currently-open near-duplicate [geo-optimizer] issues asking to "create" files that already exist and work: #53759, #53435, #52534, #52763 — plus at least 3 previously closed AI-discovery issues (#48045, #48046, #48209) that appear to have been legitimately fixed already. A prior dedup-check fix (#48695, closed) has evidently not stopped this recurrence.
Expected Impact: Fixing the scanner's base-URL/path handling for these checks eliminates a recurring source of false-positive findings and wasted duplicate-issue triage across every future GEO audit run. Also close #53759, #53435, #52534, #52763 as invalid once the scanner is fixed (they ask for files that already exist).
Suggested Agent: geo-optimizer workflow maintainer / New Agent for scanner fix
Estimated Effort: Medium (1-4 hours) — includes scanner fix + closing the stale duplicate issues
Data Source: DeepReport analysis, 2026-08-18 18:23Z cycle, cross-referencing discussion #53758 against live curl verification and gh api issue history.
Generated by 🔬 Deep Report · agent · 155.1 AIC · ⌖ 9.71 AIC · ⊞ 11.9K · ◷
— drives repeated duplicate issue filing
Description: Today's GEO Audit Report (discussion #53758) claims
llms_txtscores 0/18 withfound: falseathttps://github.github.com/gh-aw/llms.txt, and "No AI Discovery signals" (0/6) on the docs site for/.well-known/ai.txt,/ai/summary.json,/ai/faq.json,/ai/service.json. Live verification during this analysis shows all of these URLs return HTTP 200 with correct, real content:https://github.github.com/gh-aw/llms.txt→ 200 (served by the Astro dynamic routedocs/src/pages/llms.txt.ts)https://github.github.com/gh-aw/.well-known/ai.txt→ 200https://github.github.com/gh-aw/ai/summary.json→ 200The report itself already diagnosed the same class of bug for
robots_txtthis cycle ("the scanner probes the domain root... rather than the/gh-aw/project-site base path") but did not extend that root-cause reasoning to thellms_txt/ai_discoverychecks, which are also false negatives. This scanner bug is very likely the direct cause of at least 4 currently-open near-duplicate[geo-optimizer]issues asking to "create" files that already exist and work: #53759, #53435, #52534, #52763 — plus at least 3 previously closed AI-discovery issues (#48045, #48046, #48209) that appear to have been legitimately fixed already. A prior dedup-check fix (#48695, closed) has evidently not stopped this recurrence.Expected Impact: Fixing the scanner's base-URL/path handling for these checks eliminates a recurring source of false-positive findings and wasted duplicate-issue triage across every future GEO audit run. Also close #53759, #53435, #52534, #52763 as invalid once the scanner is fixed (they ask for files that already exist).
Suggested Agent: geo-optimizer workflow maintainer / New Agent for scanner fix
Estimated Effort: Medium (1-4 hours) — includes scanner fix + closing the stale duplicate issues
Data Source: DeepReport analysis, 2026-08-18 18:23Z cycle, cross-referencing discussion #53758 against live
curlverification andgh apiissue history.