test(ui): add AGPL-3.0 badge to footer to validate visual-capture pipeline

[JSONbored]

Summary

• This is a deliberate test PR, not a feature. It adds a small, real, visible "AGPL-3.0" badge to the site footer (reusing the existing Badge UI component, variant="outline") purely to validate the newly-activated before/after visual-capture pipeline end-to-end on a real gittensory-ui PR.
• Verified locally in a dev server first (preview_eval/DOM inspection confirmed the badge renders with the correct classes and a real, visible bounding box).
• Expecting: the bot's review comment to show a before/after table (production vs. this PR's preview deploy) with the badge visible in the "after" shot at both desktop and mobile viewports.

Scope

• The PR title follows type(scope): short summary Conventional Commit format.
• This PR is focused (one file, one small visible change) and does not mix unrelated backend/UI/MCP/docs/dependency/deploy changes.
• This follows CONTRIBUTING.md and does not reintroduce GitHub Pages, VitePress, site/, or CNAME.
• I linked a currently open issue this PR resolves -- N/A, deliberate test PR, no feature being solved.

Validation

• git diff --check
• npm --workspace @jsonbored/gittensory-ui run typecheck
• npm --workspace @jsonbored/gittensory-ui run lint (0 errors; pre-existing warnings elsewhere untouched)
• npm --workspace @jsonbored/gittensory-ui run format (no changes needed)
• npm run ui:build
• Manually verified in a local dev server via DOM inspection (real bounding box, correct Badge classes)
• npm run test:coverage -- N/A, apps/** is not measured by Codecov and no src/** logic changed.

Safety

• No secrets, wallet details, hotkeys, coldkeys, PATs, private keys, trust scores, private rankings, or private maintainer evidence are exposed.
• Public GitHub text stays sanitized and low-noise.
• Auth/cookie/CORS/GitHub App/Cloudflare/session changes include negative-path tests. -- N/A, no such changes.
• API/OpenAPI/MCP behavior is updated and tested where needed. -- N/A, no such surface touched.
• Public docs/changelogs are updated where needed; changelogs are only edited for release-prep PRs. -- N/A.

UI Evidence

Intentionally left blank -- this PR's entire purpose is to let the bot's own visual-capture pipeline produce that evidence automatically. See the gittensory-orb review comment for the actual before/after table once it renders.

Notes

• This PR is expected to be held for manual review regardless of CI outcome (apps/gittensory-ui/src/components/** is in this repo's hardGuardrailGlobs) -- that's expected and fine, this isn't meant to auto-merge.

[superagent-security]

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

[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	59275be	Commit Preview URL Branch Preview URL	Jul 08 2026, 07:09 PM

[loopover-orb]

Warning

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

⏸️ Gittensory review result - manual review recommended

_{Review updated: 2026-07-08 20:32:30 UTC}

1 file · 2 blockers · readiness 93/100 · CI green · clean

⏸️ 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.

Nits — 1 non-blocking

• Code changes lack test evidence — Add focused regression tests or explain why existing coverage is sufficient.

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	No AI review summary
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: 52 registered-repo PR(s), 43 merged, 497 issue(s).
Contributor context	✅ Confirmed Gittensor contributor	JSONbored; Gittensor profile; 52 PR(s), 497 issue(s).
Gate result	❌ Blocking	Repo-configured hard blocker found.

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: Python, TypeScript, JavaScript, Ruby, Go, Kotlin, MDX, Shell
• Official Gittensor activity: 52 PR(s), 497 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.

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