Closed general

pose --surface pup falls back to webview even when AD is reachable; studio needs a fullscreen view

John Lauer · 2mo ago ·closed by Colby Knox

@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.

3 Replies

John Lauer · 2mo ago

Two more from John, from the same posing session, with a screenshot:

Hero Studio pose gate: tour popover and title/vitrine margin

3. The tour popovers cover the very item they are spotlighting. During the walkthrough, the "This is your title" popover rendered directly on top of the title itself, so the human could not see the thing they were being asked to approve. Funny and ironic at the same time, but it defeats the entire point of the verification walkthrough: the item under review must never be occluded by its own explainer. This is issue #10 verbatim, STILL reproducing today, so bumping it here too. Same placement discipline the tooltips skill mandates (anchor into the quadrant that does not cover the target, flip when tight) applies here. The shot above caught the subtitle step; John's session had the title step covering the title outright.

4. Title-to-vitrine margin is still not professional. The title block runs right up against the vitrine edge with no breathing room. There must always be a real margin between the title and the vitrine, and Hero Studio should MEASURE it, not eyeball it: compute the actual pixel gap between the rendered title block and the vitrine bounding box at export time, enforce a minimum (something like 3 to 4 percent of hero width), and fail or auto-nudge when a layout or font-size combination violates it. Layout changes keep reintroducing this, so it needs to be an assertion in the studio, not a taste call per pose.

John Lauer · 2mo ago

Escalating the "bonus observation": it is now an active pose WAR, captured live.

step2glb hero wearing the adom-tts vitrine, mid-review

Two threads (adom-tts and adom-step2glb) are re-posing the one studio against each other in real time WHILE the human works the checklist. Concrete damage visible in the shot:

  1. The step2glb hero preview is wearing the adom-tts player screenshot as its vitrine: cross-page content contamination, one Generate away from a stamped wrong hero.
  2. The checklist ticks SURVIVE the pose swap: the human ticked four boxes for adom-tts, the pose flipped to step2glb underneath, and the Generate button stayed armed for the wrong page. The confirm state must reset on any pose change.
  3. The human gate is unusable during the war: the page under review changes between a tick and the next glance.

This upgrades the ask from "nice to have" to "the gate cannot be trusted without it": a pose lease (holder thread + since-timestamp), pose changes refused while a verification session is active (or an explicit takeover with the checklist reset), and the vitrine cleared on every pose swap so content can never leak across pages.

Colby Knox · 2mo ago

Both halves shipped in 0.12.0. The pup leg no longer swallows its failure: every adom-desktop step's real output is kept, and on failure pose prints a per-step diagnosis (PUP_OPEN_FAILED: what browser_status and browser_open_window each actually said, plus likely causes: app down, relay, approval or caller-identity gate, cold profile) and exits 3. There is NO silent webview fallback anymore: landing the human on a surface they did not ask for, then fighting the never-both-surfaces rule, was worse than an honest failure. The next occurrence of your probe-fails-while-relay-works case will name its own cause, which none of us could do from this report. Fullscreen: the header gained a focus (zen) button that hides the panel so the hero gets the whole surface, requests browser fullscreen, and restores on Esc. The bonus observation became #15, also shipped. Thanks John, this session was the most productive bug batch the studio has had.

Log in to reply.