Supplemental Arrows-B (U+2900-297F) glyphs exceed monospace cell width

Problem

Characters in the Supplemental Arrows-B range (U+2900-297F) render wider than a single monospace cell, breaking strict monospace alignment in terminals.

Example

The character ⥤ (U+2964 RIGHTWARDS HARPOON WITH BARB UP ABOVE RIGHTWARDS HARPOON WITH BARB DOWN) renders at 15px width when the cell width is 11px (measured at 16px font size).

This causes the glyph to be clipped in terminal emulators that strictly enforce monospace cell boundaries.

Test Results

Measured actual pixel bounds (not advance width) using canvas rendering:

Note: U+27F9 from Supplemental Arrows-A (U+27F0-27FF) fits correctly because that range was fixed in v6.0.

Reference

From CHANGELOG.md v6.0:

"Redrew U+27F0..U+27FF Supplemental Arrows-A to be strict monospace"

The same fix should be applied to Supplemental Arrows-B (U+2900-297F).

Environment

• Font: FiraCode (also affects FiraCode Nerd Font Mono)
• Tested with: FiraCodeNerdFontMono-Regular.ttf
• Font size: 16px
• Measurement method: Canvas getImageData() pixel scanning

Expected Behavior

All glyphs in monospace font should fit within a single cell width, consistent with how Supplemental Arrows-A was fixed in v6.0.

Start by reviewing the v6.0 CHANGELOG entry for Supplemental Arrows-A and locating the corresponding glyph source or build entry. Compare that precedent with U+2900–U+297F, then verify the redraw by measuring actual pixel bounds at the reported font size. Done means the Supplemental Arrows-B glyphs fit within one monospace cell without clipping.