feat(ui): rebrand to the new citron G mark and (icon)ittensory wordmark

[JSONbored]

Summary

• Replaces the old hexagon-outline GittensoryMark (mint/coral, gradient stroke) with the new brand kit's flat citron "G" glyph, hardcoded to #d5e43f regardless of theme.
• Header, footer, and sidebar shell now render the icon immediately followed by tightly-kerned "ittensory" text (gap-0.5, not gap-2/gap-1.5), so the icon visually stands in for the "G" — matching the new wordmark asset's kerning. Each accessible name stays "Gittensory" (via aria-label on the two Links, and a sr-only span in the sidebar where the visible text independently hides on collapse).
• Swaps favicon.svg/.ico, adds a 512px PNG and a real apple-touch-icon.png (previously reused the SVG for apple-touch-icon, which iOS does not reliably rasterize), and updates theme-color + manifest.webmanifest to the new #0e100d ink background.

Scope

• The PR title follows type(scope): short summary Conventional Commit format.
• This PR is focused and does not mix unrelated backend, UI, MCP, docs, dependency, and 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 — no linked issue; owner-initiated brand refresh, not tracked as a GitHub issue.

Validation

• npm run ui:lint — 0 errors (91 pre-existing warnings, none in touched files)
• npm run ui:typecheck — clean
• npm run ui:test — 71 passed
• npm run ui:build — succeeded
• git diff --check clean

Safety

• No secrets, wallet details, hotkeys, coldkeys, user PATs, private keys, raw trust scores, private rankings, or private maintainer evidence are exposed.
• Auth, cookie, CORS, GitHub App, Cloudflare, or session changes include negative-path tests. — not applicable, no such changes.
• API/OpenAPI/MCP behavior is updated and tested where needed. — not applicable, no API/MCP changes.

UI Evidence

No image hosting available via this CLI session to embed thumbnails directly, so documenting manual verification instead:

• Ran the actual dev server (vite dev) and loaded the homepage. Visually confirmed the header renders as "[citron G icon]ittensory" in the correct brand color, matching the existing lime-accented buttons elsewhere on the page.
• DOM-verified directly: icon path fill = #d5e43f, footer link visible text = "ittensory", document.body background = oklch(0.135 0.006 140) (the existing dark theme token, unaffected), <link rel="icon">/<link rel="apple-touch-icon"> hrefs resolve to the new files, <meta name="theme-color"> = #0e100d.
• Did not get a clean screenshot of the footer/sidebar specifically (a scroll-position screenshot came back blank, likely a capture-timing quirk unrelated to this change, given the same DOM inspection above confirmed correct content and styling at that scroll position).

[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	e8d7a8f	Commit Preview URL Branch Preview URL	Jul 08 2026, 02:10 AM

[loopover-orb]

Warning

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

⏸️ Gittensory review result - manual review recommended

_{Review updated: 2026-07-08 02:12:04 UTC}

10 files · 1 AI reviewer · 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.

Review summary
Clean, self-contained visual rebrand: new flat citron G-mark SVG replaces the gradient hexagon glyph, header/footer/sidebar tighten to icon+"ittensory" kerning, and favicon/apple-touch-icon/manifest assets are swapped to match. Accessibility is preserved correctly — aria-label="Gittensory" on the two Links with all visible children (mark + "ittensory" span) marked aria-hidden, and an sr-only "Gittensory" span in the sidebar where the visible label independently hides on icon-collapse. The apple-touch-icon PNG fix is a real correctness improvement (iOS doesn't reliably rasterize SVG for touch icons). No linked issue is present — the PR description states this is an owner-initiated brand refresh rather than a tracked issue, so per repo convention this should be called out explicitly rather than silently waved through, though it isn't a code defect.

Nits — 6 non-blocking

• No linked GitHub issue — per repo convention every PR should close or reference one; the description labels this owner-initiated, but that exception should be confirmed by a maintainer rather than asserted in the PR body.
• apps/gittensory-ui/src/components/site/mark.tsx now hardcodes fill="#d5e43f" and drops the currentColor/gradient theming the old mark supported via className (text-mint, text-foreground) — worth a one-line note in the PR confirming this citron is intentionally theme-invariant in both light and dark, not just verified against the current (dark) design.
• Three new binary assets (favicon.ico, favicon-512.png, apple-touch-icon.png) are added with no source/generation reference (e.g. a design-kit script or export note) — fine for a brand asset PR, but future contributors regenerating these will have nothing to diff against.
• No test changes accompany the new aria-label/sr-only accessibility pattern across site-header.tsx, site-footer.tsx, and app-shell.tsx; a simple render/testing-library assertion that each Link's accessible name resolves to "Gittensory" would guard against future edits accidentally exposing the visible "ittensory" text to the accessible name tree.
• Confirm with the PR author whether this is genuinely maintainer-authorized (owner-initiated) or needs a tracking issue opened per repo convention before merge.
• 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	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: 51 registered-repo PR(s), 43 merged, 509 issue(s).
Contributor context	✅ Confirmed Gittensor contributor	JSONbored; Gittensor profile; 51 PR(s), 509 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: 51 PR(s), 509 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.

_{🟩 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