Anatomy · a255f8b5-0

Jekyll site url points to a different repo than the project

mediumdocs-gapclosed in 4b9b492

repo 6f7fc663·PR #6·reviewed 1 week ago·closed 1 week ago

The vulnerable code

docs/_config.yml:1-5

1title: "Aeon — Skill Gallery"
2description: "Public output showcase for Aeon, an autonomous AI agent running on GitHub Actions powered by Claude Code."
3baseurl: ""
4url: "https://aaronjmars.github.io/aeon"
5

The reasoning

Opus

Jekyll site url points to a different repo than the project

mediumdocs-gaphigh

docs/_config.yml:1-5

The project root identifies this repository as AntFleet/aeon-bench, but the Jekyll site config sets url to https://aaronjmars.github.io/aeon and the social link/author URL also point to github.com/aaronjmars/aeon. When this docs/ site is published via GitHub Pages from AntFleet/aeon-bench, generated absolute links (canonical URL, RSS feed, social meta tags) will point at a completely different site/user. This breaks SEO, sitemap, and any 'fork the repo and your copy inherits this page' promise the status page itself makes — a fork will inherit the upstream's hard-coded URL rather than auto-detecting.

Recommendation

Either remove the hard-coded `url`/`baseurl`/author URL (letting GitHub Pages inject the correct site.github.url) or update them to the AntFleet/aeon-bench Pages URL. Same for the minima social_links and author.url.

GPT-5

Forks will publish a status page with wrong links/canonical URLs due to hardcoded upstream site/repo, contradicting “no extra config” claim

mediumdocs-gaphigh

docs/status.md:15
docs/_config.yml:4
docs/_config.yml:13
docs/_config.yml:51-52

The status page claims every fork gets a public dashboard with no extra config, but the site config hardcodes the original site URL and GitHub repo links. On forks or renames, canonical URLs and footer/social links will point to the upstream project, confusing users and undermining the claim of zero configuration. This is an actionable docs/config gap with concrete impact on published forks.

Recommendation

Make the Jekyll site fork-agnostic: - Use GitHub Pages metadata instead of hardcoded URLs: set url: "" and baseurl: "" and rely on the relative_url/absolute_url filters with site.github.url/baseurl, or explicitly set url: {{ site.github.url }} and baseurl: {{ site.github.baseurl }} via config defaults. - Replace hardcoded social_links user_url with {{ site.github.repository_url }} (or omit if the theme supports dynamic repo links). - Update the status page text to qualify that forks must enable GitHub Pages (and Actions) or remove the “no extra config” claim. These changes keep links and canonicals correct across forks and repo renames.

The agreement

Both frontier models flagged this within the same line range. AntFleet's unanimous gate fired — the finding posted on the PR. Closed in 4b9b492.

The fix

1title: "Aeon — Skill Gallery"
2description: "Public output showcase for Aeon, an autonomous AI agent running on GitHub Actions powered by Claude Code."
3baseurl: ""
4url: "https://aaronjmars.github.io/aeon"
5

Closure

Closed 1 week ago

SHA: 4b9b49251c8c9808bf147d55aa2930352af2e8c0

View closure receipt on GitHub →

Tweet thread template

tweet 1 of 8146 / 280

Two frontier models reviewed PR #6 on 6f7fc663. Both found this bug: medium docs-gap: Jekyll site url points to a different repo than the project

tweet 2 of 8106 / 280

The vulnerable code (docs/_config.yml:1-5): (full snippet at https://www.antfleet.dev/anatomy/a255f8b5-0)

tweet 3 of 8280 / 280

What Opus saw: "The project root identifies this repository as AntFleet/aeon-bench, but the Jekyll site config sets url to https://aaronjmars.github.io/aeon and the social link/author URL also point to github.com/aaronjmars/aeon. When this docs/ site is published via GitHub Pag…

tweet 4 of 8280 / 280

What GPT-5 saw: "The status page claims every fork gets a public dashboard with no extra config, but the site config hardcodes the original site URL and GitHub repo links. On forks or renames, canonical URLs and footer/social links will point to the upstream project, confusing …

tweet 5 of 897 / 280

Both flagged the same line range. AntFleet's unanimous gate fired — the finding posted on the PR.

tweet 6 of 893 / 280

The fix landed in commit 4b9b492: (view diff at https://www.antfleet.dev/anatomy/a255f8b5-0)

tweet 7 of 881 / 280

AntFleet reviews every PR with two frontier models. Only unanimous findings post.

tweet 8 of 877 / 280

Full anatomy + reasoning + diffs: https://www.antfleet.dev/anatomy/a255f8b5-0

Paste into X composer one tweet at a time. X has no multi-tweet intent API.

view receipt →all receipts →view disagreements →case studies →