Bug
The GitHub stars pill on lazycodex.ai links to https://github.com/code-yeongyu/lazycodex/stargazers, and GitHub now returns 404 on /stargazers for logged-out visitors — reproducible even on facebook/react/stargazers, so it's a GitHub-wide policy change, not repo-specific. The most prominent CTA on the landing page dead-ends for anonymous visitors. Easy to miss while logged in.
Repro
Open https://lazycodex.ai in a logged-out browser session and click the "2.6k stars" pill in the header → GitHub 404 page.
Fix (ready to cherry-pick)
I opened #121 with a verified one-line-ish fix (point githubStarsUrl in packages/web/lib/site-config.ts at the repo page — where the star button lives anyway — plus the matching e2e test name and the README badge link). It was auto-closed by pr-source-guidance.yml, but the diff is still there. Full e2e suite passed locally: 59/59 including both Lighthouse 100/100/100/100 presets.
Side note on PR routing
pr-source-guidance.yml redirects contributors to oh-my-openagent/packages/omo-codex, but packages/web (the lazycodex.ai source) exists only in this repository and the sync script upstream copies only the marketplace/plugin and the workflow file — so website fixes currently have no valid PR path. Might be worth scoping the auto-close to non-web paths, or moving the web source upstream.
Bug
The GitHub stars pill on lazycodex.ai links to
https://github.com/code-yeongyu/lazycodex/stargazers, and GitHub now returns 404 on/stargazersfor logged-out visitors — reproducible even onfacebook/react/stargazers, so it's a GitHub-wide policy change, not repo-specific. The most prominent CTA on the landing page dead-ends for anonymous visitors. Easy to miss while logged in.Repro
Open https://lazycodex.ai in a logged-out browser session and click the "2.6k stars" pill in the header → GitHub 404 page.
Fix (ready to cherry-pick)
I opened #121 with a verified one-line-ish fix (point
githubStarsUrlinpackages/web/lib/site-config.tsat the repo page — where the star button lives anyway — plus the matching e2e test name and the README badge link). It was auto-closed bypr-source-guidance.yml, but the diff is still there. Full e2e suite passed locally: 59/59 including both Lighthouse 100/100/100/100 presets.Side note on PR routing
pr-source-guidance.ymlredirects contributors tooh-my-openagent/packages/omo-codex, butpackages/web(the lazycodex.ai source) exists only in this repository and the sync script upstream copies only the marketplace/plugin and the workflow file — so website fixes currently have no valid PR path. Might be worth scoping the auto-close to non-web paths, or moving the web source upstream.