Skip to content

Finish the SharpMUTerm rename: README title, icon font, generator - #6

Merged
HarryCordewener merged 1 commit into
mainfrom
docs/finish-sharpmuterm-rename
Jul 28, 2026
Merged

Finish the SharpMUTerm rename: README title, icon font, generator#6
HarryCordewener merged 1 commit into
mainfrom
docs/finish-sharpmuterm-rename

Conversation

@HarryCordewener

Copy link
Copy Markdown
Member

Four files landed on main still carrying the old name. They were added by PR #3, which
branched before the rename existed, so the rename PR could not reach them.

The visible one: the repository front page announced MuGlyph in its <h1>, two lines above
a paragraph describing SharpMUTerm.

Changes

FileWhat
README.md<h1> title and logo alt text
assets/fonts/MuGlyph.ttfSharpMUTerm.ttfRenamed and regenerated
assets/fonts/README.mdDocument text
tools/make-glyph-font.pyOutput path, GLYPH_NAME, family and PostScript names

Why the font is regenerated, not just renamed

A git mv leaves the old identity inside the binary. Before:

nameID 1 = MuGlyph
nameID 6 = MuGlyph-Regular
glyph order: ['.notdef', 'muglyph']

After regenerating through the fixed tools/make-glyph-font.py:

nameID 1 = SharpMUTerm
nameID 6 = SharpMUTerm-Regular
glyph order: ['.notdef', 'sharpmuterm']
cmap: ['0xe000']

Anyone merging this into their terminal font would otherwise have seen the old family name.

Verification

  • Regenerated font reports 2 contours at U+E000, matching the two <path> elements in
    docs/logo.svg.
  • Rendered the glyph out of the built .ttf and confirmed it matches docs/logo.svg — correct
    shape and orientation (the generator flips the Y axis, since SVG is Y-down and fonts are Y-up).
  • git grep -i muglyph over README.md, assets/, and tools/ returns nothing.
  • No code changedsrc/ and tests/ are untouched, so the 514 tests are unaffected.

Also checked while surveying main, and found correct — no changes needed: docs/PACKAGING.md
(publish profiles exist at the paths it names), docs/SCREENSHOTS.md (the piping form it
documents is genuinely supported by ansi_frame_to_image.py), .github/workflows/release.yml
(artifact names), the snapshot → SVG pipeline end to end, and every relative link across all
tracked Markdown files.

The remaining old-name references are in docs/HANDOFF.md, covered by #5, and in
docs/superpowers/specs/2026-07-28-sharpmuterm-naming-design.md, where they are the subject
matter and correct to keep.

🤖 Generated with Claude Code

These four files were added by PR #3, which branched before the rename
existed, so the rename PR could not reach them. They landed on main
still carrying the old name -- including the README's <h1>, which made
the repository front page announce a name the project no longer uses,
two lines above a paragraph using the new one.
- README.md: <h1> and logo alt text
- assets/fonts/MuGlyph.ttf -> SharpMUTerm.ttf
- assets/fonts/README.md
- tools/make-glyph-font.py: output path, glyph name, family name
The font is regenerated rather than just renamed: a file rename leaves
the old family name baked into the binary (nameID 1 and 6 both read
MuGlyph). Regenerated via tools/make-glyph-font.py and verified -- family
SharpMUTerm, PostScript SharpMUTerm-Regular, glyph `sharpmuterm`, two
contours at U+E000, and the rendered glyph matches docs/logo.svg.
No code changed; src/ and tests/ are untouched.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@coderabbitai

Copy link
Copy Markdown

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in:25 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 10cd3eee-8016-46c2-af27-cccf1558bf40

📥 Commits

Reviewing files that changed from the base of the PR and between fa8479c and 9049966.

⛔ Files ignored due to path filters (2)
  • assets/fonts/MuGlyph.ttf is excluded by !**/*.ttf
  • assets/fonts/SharpMUTerm.ttf is excluded by !**/*.ttf
📒 Files selected for processing (3)
  • README.md
  • assets/fonts/README.md
  • tools/make-glyph-font.py

Comment @coderabbitai help to get the list of available commands.

@HarryCordewener
HarryCordewener merged commit e1878c5 into mainJul 28, 2026
3 checks passed
@HarryCordewener
HarryCordewener deleted the docs/finish-sharpmuterm-rename branch July 28, 2026 20:15
Sign up for freeto 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.

1 participant

@HarryCordewener