← Commit history

Capture shared lessons on showcases and Bridge operation results; defer illustrated guides

John Lauer ·7962af0335 ·1mo ago ·parent 109155b
3 files changed +35
TODO.mdadded+5
@@ -0,0 +1,5 @@+# Codex follow-up work++- [ ] Give every sub-readme a substantial visual pass: many real screenshots, annotated steps, demo stills, and consistent layouts. Deferred at John's request while the complicated KiCad board takes priority.+- [ ] Independently route a stripped copy of the Pinch toolboard, validate it against the human baseline, then record and caption the live KiCad comparison.+- [ ] Implement the Codex Desktop bridge and dock installation flow.
skills/codex-adom-operation-results/SKILL.mdadded+15
@@ -0,0 +1,15 @@+---+name: codex-adom-operation-results+description: Interpret Adom Bridge approval, asynchronous operation and artifact responses correctly when driving a desktop from Codex in Hydrogen.+---+# Operation results and continuation++Inspect the semantic response, including nested JSON, stderr, success/error fields and next-action hints. A transport success or PowerShell exit code zero can coexist with a Python traceback. Confirm the requested artifact or live state before claiming success.++An immediate approval rejection tells you the request was refused at that moment. It does not establish that approval expired, that a user has since granted it, or that an operation is queued. Explain the actual returned condition without inventing its cause. Human-only approval must remain human-only.++Discover the live operation contract. If a verb supports a job ID or stream, record the ID and follow its hints for status, reconnect, cancellation and approval continuation. Do not resubmit mutations after a timeout until the operation state is known. Do not assume a stream wakes a detached AI thread: that requires delivery by Hydrogen or the calling tool adapter.++Caller-selectable job/stream responses with approval and completion events were requested in adom/adom-bridge#154. This is a proposal, not evidence that those arguments or verbs are implemented. Verify current capabilities before using them.++For screenshots, save the response to disk and print only paths, dimensions and errors; responses may include very large base64 images. View the returned image file. For host videos and other artifacts, transfer to the intended machine and open with a host-side verb when requested; a container file link alone does not open the user's Windows player.
skills/codex-adom-showcase/SKILL.mdadded+15
@@ -0,0 +1,15 @@+---+name: codex-adom-showcase+description: Capture real Hydrogen conversations for an Adom wiki hero and verify the Hero Studio composition and human-generated export.+---+# Hydrogen showcase captures++Read the installed hero-studio skill for the current generation contract. Keep the product title and typography consistent with the user's selected sibling heroes; the dock uses that same image as its card artwork.++Capture actual app content. When the user permits resizing, inspect the monitor work area and DPI before changing dimensions. In the September 2026 Codex showcase session, the user preferred full usable screen height with only width adjusted to match the showcase slot. Apply this as a useful starting point when appropriate, not permission to resize any user's window. Keep the entire window on-screen, preserve normal text zoom, and do not disturb drafts in neighboring AI conversations.++Read the current showcase slot aspect after choosing layout and chrome. Stale slot dimensions cause letterboxing. A bottom black strip can be the studio's contain-fit background rather than part of the screenshot. Compare the source image with a composed preview; correct capture proportions instead of silently cropping or stretching. Verify again at hero and dock scale.++The subtitle should express what the integration enables, rather than merely saying the product lives in Adom. Use real screenshots, captions and illustrated steps in supporting readmes, not only a polished hero.++Hero Studio's pose command waits for the human Generate action up to its timeout. Do not claim to be listening after that wait ends. Check the approved record for the correct page and the generated artifact before publishing. A compose preview is not a provenance-stamped approved export. Keep any human-generation requirements from the current hero-studio skill intact.