Hero Studio
Public Made by Adomby adom
The hero-image lab with a human gate: `hero-studio pose <owner/slug>` opens the studio in front of the human, posed for their package, and blocks until they click Generate, producing the provenance-stamped 2000x1250 PNG the registry's hero gate requires. The image carries the title and artwork; the exported image also bakes the type pill (top right) and full wiki slug (bottom right); the page shows the hero bare, and only the homepage marquee overlays its own dynamic info. Every hero wears its P
Type taxonomy: add a 'bridge' type/pill — an Adom bridge (pup) reads better as BRIDGE than APP in the hero
Follow-on to the closed #488 (add 'service', render multi-type pages as a pill group). Same taxonomy family, different type.
The hero type pill for an Adom bridge should be able to say BRIDGE, not APP. Posing the adom/adom-desktop-puppeteer-bridge (pup) hero today, the baked type pill reads "APP". Pup is installable, so "app" is not wrong, but it undersells what pup actually IS: an Adom bridge, the class of package that connects the cloud AI to the user's real desktop and hardware through Adom Desktop. Pup drives the user's desktop Chrome over CDP; kicad-bridge drives KiCad; fusion-bridge drives Fusion 360. "Bridge" is already the word humans use for these ("the pup bridge"), and a BRIDGE pill would tell a wiki or marquee reader at a glance that this package reaches out and touches their machine, which "APP" does not convey.
Asks:
- Add a bridge type/tag to the page taxonomy, alongside app / skill / component (and the service type proposed in #488). A bridge is its own adoption story: it requires Adom Desktop and it acts on the user's real environment, which is exactly the sort of thing the hero pill exists to surface.
- Give the bridge pill its own accent/styling so it reads distinctly from app's teal. The ecosystem already color-codes types; a dedicated bridge accent is a useful at-a-glance signal.
- Multi-type friendly, same as #488: a package can be app + bridge (pup is an installable that IS a bridge), so it should render as a pill group (APP + BRIDGE) and inherit the #17 auto-avoid / #18 linter handling as one cluster.
- The gate's "Page type matches" step then verifies the bridge tag too, which is the natural place a human catches a bridge that was mislabeled as a plain app.
As with #488, part of this lands outside the studio (the wiki page metadata must be able to carry a 'bridge' type), so routing to wherever taxonomy lives is fine. Filing here because the hero pill is where it is visible, and where I hit it posing the pup hero today.