fix(github): require repo stats allowlist

[JSONbored]

Motivation

• Prevent the unauthenticated public GitHub repo-stats route from proxying arbitrary owner/repo pairs using the deployment GITHUB_PUBLIC_TOKEN, which could expose metadata or exhaust shared token quota.
• Make the safer default behavior explicit: only repos listed in PUBLIC_REPO_STATS_ALLOWLIST may be requested by the public endpoint.

Description

• Require allowlist membership unconditionally in publicRepoFullName(...) so an empty/unset PUBLIC_REPO_STATS_ALLOWLIST no longer permits all repos (change in src/github/public.ts).
• Update environment documentation to state that unset PUBLIC_REPO_STATS_ALLOWLIST denies all unauthenticated repo-stats requests (change in src/env.d.ts).
• Add a narrow hosted-worker default allowlist entry for JSONbored/gittensory and regenerate Cloudflare/OpenAPI artifacts to keep deployment defaults consistent (changes in wrangler.jsonc, worker-configuration.d.ts, src/openapi/spec.ts, and apps/gittensory-ui/public/openapi.json).
• Update integration tests to cover the new behavior and normalization: deny when the allowlist is unset, accept normalized entries, and ensure no GitHub fetch occurs for denied requests (change in test/integration/api.test.ts).

Testing

• Ran the engine build with npm --workspace @jsonbored/gittensory-engine run build and it completed successfully.
• Ran the targeted integration suite with npx vitest run test/integration/api.test.ts -t "public GitHub repo stats" --reporter=verbose and the updated tests for the public GitHub repo stats passed (5 passed, other unrelated tests skipped as expected).
• Ran npm run ui:openapi:check, npm run cf-typegen:check, and npm run typecheck to verify regenerated artifacts and types, and all checks succeeded.

---

Codex Task

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Preview URL	Updated (UTC)
✅ Deployment successful! View logs	gittensory-ui	7569796	Commit Preview URL Branch Preview URL	Jul 12 2026, 08:27 AM

[superagent-security]

Superagent didn't find any vulnerabilities or security issues in this PR.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 94.34%. Comparing base (6c40d1e) to head (7569796).
⚠️ Report is 5 commits behind head on main.
✅ All tests successful. No failed tests found.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #4978   +/-   ##
=======================================
  Coverage   94.34%   94.34%           
=======================================
  Files         473      473           
  Lines       39927    39927           
  Branches    14557    14557           
=======================================
  Hits        37669    37669           
  Misses       1583     1583           
  Partials      675      675           

Flag	Coverage Δ
shard-1	46.34% <0.00%> (-0.01%)	⬇️
shard-2	34.41% <0.00%> (-0.26%)	⬇️
shard-3	31.22% <0.00%> (-0.81%)	⬇️
shard-4	32.68% <0.00%> (+0.72%)	⬆️
shard-5	33.67% <0.00%> (-0.10%)	⬇️
shard-6	45.09% <100.00%> (+0.21%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines	Coverage Δ
src/github/public.ts	98.59% <100.00%> (ø)
src/openapi/spec.ts	99.42% <ø> (ø)

🚀 New features to boost your workflow:

• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[loopover-orb]

Warning

🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨

⏸️ Gittensory review result - manual review recommended

_{Review updated: 2026-07-12 08:29:43 UTC}

7 files · 1 AI reviewer · 2 blockers · readiness 93/100 · CI green · unstable

⏸️ Suggested Action - Manual Review

• No linked issue detected — If this PR is intended to solve an issue, link it explicitly in the PR body.
• Maintainer requires a linked issue — Link the relevant issue (for example Closes #123) before opening the PR.

Review summary
This PR tightens `publicRepoFullName` in src/github/public.ts so an unset/empty `PUBLIC_REPO_STATS_ALLOWLIST` now denies all requests instead of allowing any owner/repo, closing a real exposure where the unauthenticated public repo-stats route could proxy arbitrary GitHub API calls using the deployment's server-side `GITHUB_PUBLIC_TOKEN`. The fix is at the correct layer (the allowlist check itself), regenerated artifacts (wrangler.jsonc, worker-configuration.d.ts, openapi.json, spec.ts) stay consistent with the new hosted-worker allowlist entry, and the updated integration tests exercise the real denied/allowed paths (asserting `fetch` is never called on denial) rather than fabricating unreachable states.

Nits — 5 non-blocking

• The PR description doesn't cite an explicit 'Fixes #NNNN'/'Closes #NNNN' for an eligible open issue — it only contextually references Fix public repo-stats endpoint hardcoded to jsonbored/gittensory only #4612 in code comments; per repo convention this should be linked explicitly.
• This is a behavior-breaking default change for any self-hosted fork that relied on the old 'unset allowlist = allow own repo' convenience (src/github/public.ts, previously documented at Fix public repo-stats endpoint hardcoded to jsonbored/gittensory only #4612) — worth confirming self-host docs/README call out the new required config step.
• Add an explicit issue link in the PR description per repo convention.
• Consider a CHANGELOG or self-host upgrade note calling out that `PUBLIC_REPO_STATS_ALLOWLIST` is now required for the public repo-stats endpoint to function, since previously-working self-host deployments will silently start returning 400s.
• nit: The PR description should explicitly link or close the eligible issue for this security behavior change, e.g. `Closes Fix public repo-stats endpoint hardcoded to jsonbored/gittensory only #4612` or `Refs Fix public repo-stats endpoint hardcoded to jsonbored/gittensory only #4612`, because the repo convention requires issue-scoped contributor work.

Concerns raised — review before merging

• No linked issue detected — If this PR is intended to solve an issue, link it explicitly in the PR body.
• Maintainer requires a linked issue — Link the relevant issue (for example Closes #123) before opening the PR.

Signal	Result	Evidence
Code review	❌ 2 blockers	1 reviewer
Linked issue	⚠️ Missing	No linked issue or no-issue rationale found.
Related work	✅ No active overlap found	No same-issue or scoped active PR overlap found.
Change scope	✅ 20/20	Low review scope from cached public metadata (no linked issue context).
Validation posture	✅ 25/25	PR body includes validation/test evidence.
Contributor workload	✅ 10/10	Author activity: 45 registered-repo PR(s), 37 merged, 411 issue(s).
Contributor context	✅ Confirmed Gittensor contributor	JSONbored; Gittensor profile; 45 PR(s), 411 issue(s).
Gate result	❌ Blocking	Repo-configured hard blocker found.
Improvement	✅ Minor	risk: clean · value: minor — Code changes are accompanied by test evidence.

Review context

• Author: JSONbored
• Role context: owner (maintainer lane)
• Public audience mode: oss maintainer
• Lane context: Repository is configured for direct PR review.
• Public profile languages: not available
• Official Gittensor activity: 45 PR(s), 411 issue(s).
• PR-specific overlap: none found.

Contributor next steps

• Treat this as maintainer-lane context rather than normal contributor-lane activity.
• Explain no-issue PR.
• Link the issue being solved, or explicitly explain why this is a no-issue PR.

Signal definitions

• Related work = same linked issue, overlapping active PRs, or title/path similarity.
• Change scope = cached public metadata such as size labels, draft state, and review-burden hints.
• Validation posture = whether the PR provides enough public validation/test evidence for maintainer review.
• Contributor workload = public contributor activity and cleanup pressure, not a repo-wide quality failure.
• Contributor context = public GitHub/Gittensor identity context; non-Gittensor status is not a blocker.

[BETA] Chat with Gittensory

Ask Gittensory a question about this PR directly in a comment — grounded only in the same cached, public-safe facts shown above, never a new claim.

• @gittensory ask <question> answers contribution-quality Q&A with source citations and freshness.
• @gittensory chat <question> answers in natural prose from cached decision-pack facts via local inference (maintainer/collaborator; read-only).
• A plain-language @gittensory mention with a real question is routed to the closest matching read-only command automatically -- no exact syntax required.

Full command reference: https://gittensory.aethereal.dev/docs/gittensory-commands

Visual preview

Route	Viewport	Before (production)	After (this PR's preview)	Diff
/	desktop			—
/	mobile			—

Click any thumbnail to open the full-size screenshot. Before = production · After = this PR's preview deploy.

_{🟩 Safe / merged · 🟦 Advisory · 🟨 Held for review · 🟥 Blocked / closed}

---

💰 Earn for open-source contributions like this. Gittensor lets GitHub contributors earn for the work they already do — register to start earning →.

Checked by Gittensory, a quiet PR intelligence layer for OSS maintainers.

• Re-run Gittensory review