next: HUD 0.3.0: the apps say their kit version, old builds get what they can draw
MergedThis moves Grain to HUD 0.3.0 in all the places AGENTS.md says to bump: next/package.json and its lock, ios/HUD/Package.swift and ios/Package.resolved, android/gradle/libs.versions.toml, and the app file's hud. It adds kits.oldest: "0.2.0" and points the $schema URLs at HUD's v0.3.0 tag. The diff matches what the body says, and the lock entries all move together to 0.3.0.
I found nothing that must change. The next, android, next-image and test checks were still running when I looked, so the approval doesn't rest on them. The iOS build wasn't run, as the body admits; the package pin and Package.resolved agree.
Optional follow-up, not a reason to hold the pull: some docs still describe the old state.
AGENTS.md(around lines 258 and 304) quotes"hud": ">=0.2.0"andv0.2.0..knotless/workflows/next.yml:10has the same comment.AGENTS.mdsays the$schemaURLs point at a35a6d8, and they now point at v0.3.0.
AGENTS.md could also name kits.oldest, which is raised alongside app-version.json's minimums.
6 passed, 2 skipped
- next: HUD 0.3.0: the apps say their kit version, old builds get what they can draw
- main
What changes
Grain moves to HUD 0.3.0 (
just hud-version 0.3.0):@hud/renderer,@hud/shell,@hud/shared^0.3.0,hud.HUDKit0.3.0 andplace.hud:hudkit0.3.0. With it the web, iOS and Android clients say their kit version as they call HUD, and HUD draws each for its own kit: a component newer than an app build is sent as its children, itsfallback, or nothing, so builds already on phones never show "isn't drawn yet".The app file says
"kits": {"oldest": "0.2.0"}, the oldest app build Grain still serves, sohud checkwarns where a view uses a component or prop newer than 0.2.0 with no{"$kit": …}gate orfallbackaround it. It is raised as old builds age out, besideapp-version.json's minimums. Its"hud"is>=0.3.0, so thenextcheck buildshud checkfrom v0.3.0. The app file's and views'$schemapoint at HUD's v0.3.0 schemas, which knowkits.Why
A view change reaches every client at once, but an app build keeps the renderer it shipped with; until now HUD could not tell them apart, and an unknown component drew a developer placeholder.
How it was checked
node next/check-apps.mjs;npm run checkin next/ (0 errors).swift package resolvefetchedhud.HUDKit0.3.0 from the registry.kits.Shortcomings
Nothing in HUD's catalog is newer than 0.2.0 yet, so the per-kit replacement and the warnings first act on the next new component. Kit gates are on Stack, Pane and Bar alone. The iOS and Android builds were not run locally beyond resolving the package; the
androidcheck builds Android.