Skip to content

V3 Part 1: arrows and status glyphs drawn in the page's own fonts #80

Closed

Description

@realRaghavGupta

Part 1 of the V3 batch.

Why

live.setkernel.com draws its arrows and status glyphs in a system font, not the page's own fonts, and no @font-face declares a unicode-range, so nothing notices. setkernel-live deploys on every merge to main. This part needs nothing from the shared visual check and goes first.

Acceptance criteria

  • One of two fixes. (a) Inline SVG arrows, aria-hidden, with the key named in text. (b) A subset cut from the OFL source that adds U+2190 to U+2193 and the status glyphs (U+25CF, U+25CB, U+25CE, U+22EF, U+2016, U+25CC, U+2715), with its pyftsubset command and source version in a new public/fonts/PROVENANCE.txt and the OFL file beside it. If Manrope's source lacks the arrows, /usage uses (a). Prefer (a): no binary fonts.
  • Each @font-face in public/style.css declares the unicode-range its file covers.
  • A new test/glyphs.test.mjs fails when a non-ASCII character drawn from public/index.html or a string literal in public/**/*.js (comments skipped) is outside the declared unicode-range of the face that draws it. It fails on main and passes on the branch under npm test. No existing test is edited.
  • CDP CSS.getPlatformFontsForNode, run on setkernel-linux (not a Mac), lists only Manrope and IBM Plex Mono for #keys, one lane's status glyph and stage line on ?demo at 1440x900, and #months on /usage with the fixture from test/usage-page.test.mjs. The output is pasted in the PR.
  • Before and after shots in the PR, taken on setkernel-linux with an opaque background: ?demo at 1440x900 in light, and /usage from fixture data only.
  • npm run validate passes on the head.

Files likely touched

public/style.css, public/index.html, public/app.js, public/usage/page.js, public/fonts/ (option b only: subset woff2, PROVENANCE.txt, OFL), test/glyphs.test.mjs (new).

Risk class

R1 with option (a); R2 with option (b), which adds binary fonts. Every merge deploys live.setkernel.com, so Raghav merges.

Activity

  1. added
    agent-readyReady for an agent to pick up
    and removed
    agent-readyReady for an agent to pick up
    on Nov 3, 2026
  2. vega-setkernel commented on Nov 3, 2026

    @vega-setkernel
    Contributor

    Picked up. Working on branch agent/80-v3-part-1-arrows-and-status-glyphs-drawn. Automated: @vega-setkernel's agent on vega-dev.

  3. setkernel-lead commented on Nov 4, 2026

    @setkernel-lead

    Ticked the 6 remaining boxes: #84 merged and closed this issue. (board-sync, hq#1043)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

agent-reviewWaiting for agent review

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions