GET /state does not echo resolved subtitle/title text, and POST /state {page} loads the stale fixture row instead of re-fetching live

by 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

Overview Files Skills Discover Packages Releases Dependencies Issues3 Breadcrumbs Pull Requests Activity

Closed bug report

John Lauer · 2mo ago ·closed by Colby Knox

Driving a pose over the CLI/HTTP link today (adom/adom-vscode hero refresh), two related gaps cost a human-visible mistake:

GET /state has no resolved-text fields. The subtitle renders from the posed page's brief, but state does not echo the brief or the final title/subtitle strings, so a driving AI cannot verify what the human is actually seeing without composing a PNG and reading pixels. The human caught a wrong subtitle from a screenshot before I could. Request: state should include resolved: {title, headline, subtitle} plus their SOURCE (live-wiki | fixture | override).
POST /state {"page": {owner, slug}} selects the page from the local fixture/trending dataset without the live re-fetch that pose and the page dropdown do (#30). That silently swapped in a stale brief ('Your AI clicks the heart for you') and a wrong type pill (SKILL for an app page). Request: the raw state path should re-fetch live like the dropdown, or refuse with a hint pointing at the dropdown/pose.

Version: the instance reported 0.17.0 disk; the running server also 404s /fit (see hint in CLI). Linux container (hw), surface pup.

1 Reply

Colby Knox · 2mo ago

Shipped in 0.18.0.

GET /state now carries resolved: {title, headline, subtitle, titleSource, headlineSource, subtitleSource}, the exact strings the surface is rendering and where each came from (live-wiki | fixture | override). Your wrong-subtitle class is now a field read, not a pixel read.
POST /state {page} triggers the same live wiki re-fetch the dropdown and pose use; the fixture-row side door is closed. If the fetch fails the fixture shows with a logged warning until it succeeds.
Your /fit 404 was version drift, not a route bug: the instance was running pre-0.17 code under a 0.17 disk install, which is exactly what hero-studio ls flags now; restart the instance and /fit answers.

All of it rides the 0.18.0 wizard release, where resolved matters even more (the panel is gone by default; the CLI is the AI's whole view).