reship-fontpack-bundle

name

reship-fontpack-bundle

description

Regenerate PolyKybd font-pack bundles from the committed firmware headers and reship the changed ones to the host (PolyKybdHost) — WITHOUT needing the pinned fontconvert / FreeType-HarfBuzz build. Use when a bundle's shipped .plyf must be refreshed: after a fonts.yaml render/size tweak, after the shadowed-glyph dedupe, when host and firmware bundle bytes have drifted, or when asked to "reship the symbol/emoji/fantasy/… bundle", "resync the font packs to the host", or "regenerate bundles.json". Handles the finicky parts the manual procedure gets wrong: dedupe parity, the --bundle-version=0 reset trap, minimal version bumps, the per-field bundles.json rebuild (size/sha256), and the firmware committed manifest. NOT for adding a NEW bundle or changing fonts.yaml itself (that needs fontconvert), and NOT for making a font resident (use make-font-resident).

Reship a font-pack bundle to the host

The external-flash font pack ships as N per-family bundles (symbol, mideast, syllabic, asia, flags, emoji, fantasy). Each is a .plyf shipped to both the firmware (as the committed fontpack_bundles.manifest.json ABI contract) and the host (PolyKybdHost/polyhost/res/fontpack/<id>.plyf + bundles.json, which the host flashes on connect). There is no ship script — this skill is the recipe, and reship_bundles.py (beside this file) is the actuator.

Key fact that makes this cheap: bundles derive deterministically from the committed category headers (base/fonts/generated/*.h). fontconvert only regenerates those headers from the TTFs. So for any reship where the headers are already committed — a dedupe bump, a version-only resync, copying a firmware-side render change to the host — you do need the pinned FreeType/HarfBuzz build at all. The helper rebuilds the straight from the headers (mirroring the build's default-on dedupe), so it works in any container.