zeekay c5a4964d9d fix(type): the calendar reads Zen, and nothing fetches a face from Google ...

Three entry points called next/font/google for Inter and bound it to
--font-sans, so the product rendered in a Google-hosted face and made the
request to fetch it before anything painted. They take @hanzo/font's ZenSans,
which is local; the --font-sans contract the app already sets from the font
object is unchanged, so nothing downstream moves.

The display face was Cal Sans — the upstream product's own, which we have no
licence to ship under our name. Both apps take Zen's matching cuts and the
seven CalSans files are gone.

The platform SDK examples are sixteen more next/font/google imports, and they
matter for the reason the docs examples do: a customer scaffolds from them, so
whatever face they open with becomes the face of somebody else's project.

`interFont` is `sansFont` — a binding named after a face it no longer holds is
the thing the next reader has to be told about.

2026-08-25 12:14:00 -07:00

..

[[...mdxPath]]

fix(docs): pass missing sourceCode prop to Wrapper component (#28901)

2026-04-15 10:14:47 -03:00

fonts.css

…

layout.tsx

fix(type): the calendar reads Zen, and nothing fetches a face from Google

2026-08-25 12:14:00 -07:00

logo.css

…