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
pose --surface pup falls back to webview even when AD is reachable; studio needs a fullscreen view
@colby, two field asks from posing the adom-tts hero today (reported on behalf of John):
1. Let the AI actually honor the user's surface preference (webview vs pup).
pose --surface pup fell back to a webview tab with WARN [PUP_UNREACHABLE]: Adom Desktop did not answer, while the same container was successfully driving Adom Desktop (browser_open_window, screenshots) seconds before and after. So the pup leg's reachability probe is failing where the real relay works, and the fallback silently lands users on the wrong surface. Many users now carry a real preference here (adom-cli hydrogen probe reports window_mode), and the skill instructs us to pass it, so the pup path needs to be as reliable as the webview path. Workaround today: pose falls back, then the AI hand-opens the proxy URL in a pup session and removes the webview tab, which also fights the "never open both surfaces" rule.
2. Hero Studio needs a fullscreen view. The studio genuinely needs room to function: the 16:10 hero preview, the verification checklist, the marquee overlay, and the control panel do not fit comfortably in a webview pane, which is a smaller surface by construction. In a maximized pup window it works well. Suggested: a fullscreen/zen toggle in the studio UI (and defaulting the pose gate to the user's preferred surface from item 1, since pup gives it the space it wants).
Bonus observation from the same session: two AI threads posed different packages (adom-tts, then adom-step2glb) against the one studio server and silently clobbered each other's pose state. A per-pose token or a "studio busy since for /" guard would make the human gate collision-proof.

