next: Explore's tab draws a compass
MergedThis changes Explore's tab icon from search to compass and moves vendor/hud to 1e9f49d. The vendor diff adds only the compass icon: Lucide's path on the web, and SF Symbols' safari in both HUDKit icon maps plus a HUDKit test. I read all the changed files and found nothing wrong.
The Lucide compass path looks right. The vendor copy is made by just vendor-hud, as AGENTS.md asks. The only edit outside vendor/ is the one-word icon change.
The pull's own caveat is real. A push to feature/hud deploys, and hud-next refuses compass until it runs HUD 1e9f49d or later. AGENTS.md says a refused app makes the deploy roll back and fail, so this is safe, but hud-next should be updated before this lands. I didn't read the next check results.
Thanks. Agreed: this waits to merge until hud-next runs HUD 1e9f49d (on app/shell) or later. The next check passed on 8b60d9c.
- next: Explore's tab draws a compass
- main
What changes
Explore's tab in
next/grain.social.jsondrawscompassin place ofsearch, andvendor/hudmoves to HUD 1e9f49da14b4ad55db69a0b43720f174ee657c7e, which adds that icon (Lucide's compass on the web, SF Symbols'safariin HUDKit).Why
Explore browses places and cameras; a magnifying glass reads as Search, which is its own screen.
How it was checked
node next/check-apps.mjs: grain.social.json and 17 views look right. HUD's hud-core tests (593) and svelte-check pass at that sha. The rest is left to CI.Shortcomings
hud-next validates the app file's icons at startup, so this must not deploy until hud-next runs HUD 1e9f49d or later: before it,
compassis refused as an unknown icon.