Skip to content

Home logo: NanumSquare Neo font, brand gradient, Hangul Day variant - #8

Merged
yor42 merged 2 commits into
mainfrom
claude/risutanium-logo-font-83xjgd
Oct 11, 2026
Merged

yor42 merged 2 commits into
mainfrom
claude/risutanium-logo-font-83xjgd

Conversation

@yor42

@yor42 yor42 commented Oct 11, 2026 •

Copy link
Copy Markdown
Owner

What and why

Brings the home-screen "RisuTanium" title in line with the branding in docs/branding.

  • Font: the title uses NanumSquare Neo Heavy by NAVER (SIL OFL 1.1). The unmodified woff2 and its full license (OFL.txt, with NAVER's notice) are in src/etc/fonts/NanumSquareNeo/. Vite bundles the font, so it also works offline and in the desktop build. If it hasn't loaded yet, the title shows in the user's own font setting.
  • Gradient: this matches the *_Gradient.svg logos. "Risu" gets the #00a1ad → #587bff diagonal gradient, which spans the whole word as in the SVG. "Tanium" uses the theme text colour, which gives the same result as the brand files' bright and dark versions. The other holiday versions keep their own styling.
  • Hangul Day easter egg (October 9): the title reads 리스타늄, in the same style. It shows only when the app language is Korean, following the Chuseok egg.
  • README: a new Credits section credits the font, including NAVER's recommended attribution sentence.

The font file comes from the npm package typeface-nanum-square-neo@0.0.6, a repackaging of NAVER's release, because NAVER's CDN was unreachable from the build environment. It was not compared byte-for-byte with NAVER's own download. To use NAVER's original, replace NanumSquareNeoTTF-eHv.woff2 with a file of the same name.

Checks

  • pnpm check passes
  • pnpm test passes (664 files; 13,012 passed, 6 skipped)
  • pnpm build passes (run after the font commit; the font is emitted to dist/assets and referenced from the CSS)
  • A bug fix has a test that fails without the fix (not applicable, no bug fix)
  • Upstream compatibility holds: a .bin backup, character, module, preset or plugin from upstream RisuAI still works, and what this fork exports still imports upstream (UI only; no data or format changes)
  • If it touches saving, the save format or storage, the change is described above and the risk to existing data is explained (does not touch saving)
  • No secrets, keys or personal data are included
  • Comments describe what must stay true, not the history of the change

The new title was rendered in headless Chromium and compared with the brand SVGs. It was not checked in the Safari engine or the Android or Linux app webviews.

🤖 Generated with Claude Code

https://claude.ai/code/session_01ExzsxgbSdJVqkTM5M1xNuQ

Bundle the unmodified NanumSquare Neo Heavy woff2 (NAVER, SIL OFL 1.1)
with its license text and apply it to the RisuTanium title on the home
screen, falling back to the user's font setting. Credit the font in the
README.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01ExzsxgbSdJVqkTM5M1xNuQ
The home-screen title now follows the docs/branding gradient logos:
"Risu" is filled with the #00a1ad to #587bff diagonal gradient spanning
the whole word, and "Tanium" uses the theme text colour. On October 9
Korean-language users see the same logo spelled 리스타늄.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01ExzsxgbSdJVqkTM5M1xNuQ
@yor42
yor42 merged commit 5b0fa42 into main Oct 11, 2026
4 checks passed
yor42 added a commit that referenced this pull request Oct 11, 2026
…m merge and the logo PR, MC-273 to MC-278, CHORE-177 to CHORE-180, ledger rows 1641 to 1696

Ledger rows 1641 to 1694 record the dispatches since 8c6146e: the
Stage 3 plan and its Gate 1, the 3a, 3b-1 to 3b-4 and 3c coders,
translator and gates, the Note 9 passes, the F2 trace and the avatar
cache investigation, the Stage 4 plan with the advisor and Gate 1,
S4-1, S4-2 and its remediation, the S4-2b plan rounds (three
consecutive Gate 1 rejects, the advisor escalation, Change 1 and
Change 2), S4-2c and the hardening review, the upstream merge's test,
review and record, and the logo PR review. Row 1695 is this closeout
and row 1696 its verification.

MC-273 to MC-278 record the maintainer's decisions since 8c6146e:
the first-open dirty effect left to unload stage 2; the Grid app-drawer
direction and the Stage 3 answers; the 3b-2 to 3b-4 answers (the
Grid keeps its folder face, the F2 jank ticketed, the 16 MB avatar
cache budget); the 3c wording and the folder-name shadow; the Stage 4
plan answers with the S4-1, upstream merge and logo PR authorizations;
and the S4-2 decisions D1 to D9 with the commit authorization. The
Orchestrator's reading of the S3/S4-before-unload ordering and its
plan rules are labelled as such, not as maintainer words.

Roadmap and Live-State move the character list rework to a third status
update: Stage 3 (6035dd5, 08b8887, 8f10f04, f4d2205, c8a9947,
49c1086), S4-1 (ff5bd37) and S4-2 with S4-2b and S4-2c (e75b124) are
technically accepted and pushed; S4-3 to S4-6 remain, so the item is
still in progress. The first-open dirty question is marked answered
and the queue now starts with S4-3. A detail section gives the gates,
checks, device figures, accepted limits, carry-forward notes and
remaining work; a short companion section points at the upstream merge
record (Agents/Upstream-Merges.md, not rewritten) and covers the logo
PR #8 merge. The F2 trace and the device reports are marked as not
independently verified.

New tickets: CHORE-177 (Grid fling jank with every folder open, cause
inferred, plus the browser's CSS image re-fetch), CHORE-178 (lorebook
searchMatch scan depth with no clamp), CHORE-179 (phone-browser Back)
and CHORE-180 (Back on screens with their own back stack). The next
free ticket is CHORE-181, the next MC is MC-279 and the next ledger row
is 1697.

Maintainer-Context and Decision-Index are included. The decision index
is regenerated for MC-278 (277 entries, -Check current).

Checked by doc-verifier: PASS WITH FIXES, fixes applied.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_015Q6ABYpmiXZmtpyHTvmFkW
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants