@khanglvm/relay 0.10.1 → 0.10.2

package/docs/AGENT.md

@@ -11,6 +11,22 @@ leave comments, and select text in markdown blocks to annotate — their comment
 come back in `result.annotations` alongside their answers. Treat annotations as
 first-class feedback.
 
+**Read ALL four feedback channels, not just `answers`.** A result carries the
+user's input across **four** places, each first-class — never act on `answers`
+alone:
+
+- `answers` — the per-question values (what they picked/typed).
+- `notes` — per-question free-text notes (`result.notes[questionId]`): the small
+  note box under a question, where users qualify or override a pick. **Single
+  (radio) questions show this box by default**, so it is a very common place for
+  the real reasoning to land. Easy to miss because empty notes are omitted —
+  **always inspect `result.notes`.**
+- `comment` — one board-level free-text note ("Anything else?").
+- `annotations` — element-level inline comments on specific blocks/data points.
+
+If any of `notes`, `comment`, or `annotations` is non-empty, it can override or
+contradict an `answers` value — reconcile them before generating output.
+
 Everything machine-relevant is on **stdout as JSON**; human-facing logs go to
 stderr. Exit codes: `0` submitted/acknowledged · `2` timeout · `3` cancelled ·
 `4` usage error · `5` not found.
@@ -137,12 +153,18 @@ boolean/bool/yn→yesno, input→text, longtext→textarea, rating/likert→scal
 ```
 
 Unanswered questions are absent from `answers` and listed in `skipped`.
-Questions with `"note": true` show a small optional free-text field; non-empty
-notes come back in `notes` keyed by question id. **`single` (radio) questions
-show this note by default** so the user can qualify their pick — set
-`"note": false` to hide it. On `timeout`/`cancelled`, a
-`draft` field carries the autosaved partial answers and any annotations written
-so far.
+
+`notes` (a `{ questionId: "text" }` map) is **always present** in a result —
+`{}` when empty — so you can never miss that the channel exists; iterate it
+even when you only expected `answers`. Questions with `"note": true` show a
+small optional free-text field, and only **non-empty** notes appear as keys.
+**`single` (radio) questions show this note by default** so the user can
+qualify or override their pick — set `"note": false` to hide it. A note like
+`notes.approach = "actually B, not A"` is the user's real intent and outranks
+the `answers.approach` radio value — always check `notes` before acting.
+
+On `timeout`/`cancelled`, a `draft` field carries the autosaved partial
+answers, notes, and any annotations written so far.
 
 ## Blocks
 
@@ -277,7 +299,10 @@ Rules of thumb:
 { "type": "html", "htmlFile": "viz.html",   "height": 400 }
 
 // Image — local file path (embedded at spec time, works offline), http(s) URL,
-// or data URI. "height" caps the displayed height; zoom/full-screen included.
+// or data URI. "height" sets only the COMPACT inline preview — every image keeps
+// a full-screen + zoom (⌘/Ctrl+wheel or −/+, up to 8× native) + drag-to-pan
+// viewer, so a small height never hides detail. Local images embed up to 8 MB;
+// for a huge / high-resolution image pass an http(s) URL (streamed, no size cap).
 { "type": "image", "src": "screenshots/variant-a.png", "alt": "Variant A", "height": 220 }
 { "type": "image", "src": "https://example.com/mock.png" }
 ```
@@ -314,7 +339,7 @@ real path over telling the user to paste it into a terminal.
 - `mermaid`: natural flow, max-height 1200 px with internal scroll. Override with `"height"`.
 - `chart`: default 320 px. Override with `"height"`.
 - `html`: default 360 px. Override with `"height"`.
-- `image`: natural size (never upscaled), max-height 1200 px with scroll. `"height"` caps it.
+- `image`: natural size (never upscaled), max-height 1200 px with scroll. `"height"` caps the **inline preview only** — full-screen + zoom (up to 8× native) always reach full detail. Local images embed up to 8 MB; use an http(s) URL for larger.
 - `table`: natural flow.
 - All heights clamp to 100–2400 px.
 - Inside OPTION cards, always set a compact `"height"` (~140–260) on
@@ -538,8 +563,11 @@ call rather than calling it repeatedly in a loop.
   check whether the user has started answering.
 - In the board `intro`, tell users they can hover chart points / select text to
   leave inline comments — they won't discover it otherwise.
-- Check `result.annotations` before generating your next output; a comment on a
-  specific data point or a quoted sentence often overrides the checkbox answer.
+- Check `result.notes` AND `result.annotations` before generating your next
+  output — not just `answers`. A per-question note (e.g. `notes.scope = "docs can
+  wait"`) or a comment on a specific data point / quoted sentence often qualifies
+  or overrides the checkbox answer. `notes` is always present (`{}` when empty),
+  so iterate it every time.
 - Use `rly reopen <id> --replies replies.json` to answer the user's element
   comments and reopen the board as a conversation thread.
 - Use `rly update <id>` to push spec changes to a running board — the page

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@khanglvm/relay",
-  "version": "0.10.1",
+  "version": "0.10.2",
   "description": "Browser-based question boards with rich blocks (markdown, charts, mermaid, tables, code, diffs, video, sandboxed HTML), clickable local file-links, and element-level annotations for AI coding agents (Claude Code, Codex, …): ask users structured questions, present interactive visuals, collect inline comments, wait for submit, read answers as JSON.",
   "keywords": [
     "ai-agents",

package/skills/relay/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: relay
-description: "The tool for collecting user requirements, decisions, and answers (choice, yes-no, text, scale) and for presenting prototypes, plans, structures, code changes, or reports with rich visuals - mermaid/graphviz/plantuml diagrams, charts, tables, code, diffs, video, custom HTML, clickable file-links - plus inline comments on any element. Opens a browser board, waits for Submit, returns JSON answers, comments, and edited diagrams. Use PROACTIVELY instead of (a) native ask-user tools for 2+ answers or options needing explanation, (b) ASCII trees/tables/diagrams in the terminal or prose for structures/designs/plans, (c) hand-rolled HTML demos. Triggers: collect requirements, ask the user, get decisions/feedback, present a prototype, plan/design review, show me the structure/file tree, architecture or dependency graph, visualize, diagram, chart, table, compare alternatives, survey, edit the diagram, show me the diff / git diff, video walkthrough, open a file. Skip for a single trivial yes/no confirmation."
+description: "The tool for collecting user requirements, decisions, and answers (choice, yes-no, text, scale) and for presenting prototypes, plans, structures, code changes, or reports with rich visuals - mermaid/graphviz/plantuml diagrams, charts, tables, code, diffs, video, custom HTML, clickable file-links - plus inline comments on any element. Opens a browser board, waits for Submit, returns JSON answers, per-question notes, comments, and annotations. Use PROACTIVELY instead of (a) native ask-user tools for 2+ answers or options needing explanation, (b) ASCII trees/tables/diagrams in the terminal or prose for structures/designs/plans, (c) hand-rolled HTML demos. Triggers: collect requirements, ask the user, get decisions/feedback, present a prototype, plan/design review, show me the structure/file tree, architecture or dependency graph, visualize, diagram, chart, table, compare alternatives, survey, edit the diagram, show me the diff / git diff, video walkthrough, open a file. Skip for a single yes/no confirmation."
 ---
 
 # relay (`rly`)
@@ -137,6 +137,10 @@ single/multi question.
 { "type": "html",     "htmlFile": "viz.html",         "height": 400 }
 { "type": "image",    "src": "screenshot.png" }       // local file, URL, or data URI
 { "type": "image",    "src": "https://…/mock.png", "alt": "Mockup B", "height": 220 }
+// ^ `height` only sets the COMPACT inline preview — every image keeps a full-
+//   screen + zoom (⌘/Ctrl+wheel or −/+, up to 8× native) + drag-to-pan viewer,
+//   so detail is always reachable regardless of height. Local images embed up
+//   to 8 MB; for a huge/high-detail image pass an http(s) URL (streamed, no cap).
 ```
 
 ### Visual options — show each choice, don't describe it
@@ -203,6 +207,23 @@ mention annotation in the board intro.
 Read annotations before generating your next output — a comment on a specific
 data point often carries sharper signal than a checkbox answer.
 
+## Reading the result — four feedback channels
+
+A result is more than `answers`. **Always read all four** — never act on
+`answers` alone; the user's real intent often lives in the others:
+
+| field | what it is |
+|---|---|
+| `answers` | per-question values `{ questionId: value }` (skipped ones absent, listed in `skipped`) |
+| `notes` | **per-question free-text notes** `{ questionId: "text" }` — the note box under a question. **Always present (`{}` when empty)**; iterate it every time. `single` (radio) questions show this box by default, so it's a very common place for the user's reasoning — and easy to miss. |
+| `comment` | one board-level free-text note ("Anything else?") |
+| `annotations` | element-level inline comments (array; see below) |
+
+A `notes[questionId]`, a `comment`, or an `annotation` can qualify or override
+the matching `answers` value (e.g. `answers.approach = "a"` but
+`notes.approach = "actually B"` → the user means B). Reconcile them before
+generating output. The same channels appear under `draft` on timeout/cancel.
+
 ### Reply to annotations (agent → user conversation)
 
 ```sh

package/src/server.js

@@ -740,7 +740,11 @@ export async function runBoard({ id, port = 0, open = true, timeoutSec = 1800, q
       answers: partial.answers ?? null,
       skipped: partial.skipped ?? null,
       comment: partial.comment ?? '',
-      notes: partial.notes ?? null,
+      // Per-question notes are first-class feedback. Always emit the key (even
+      // empty {}) so a consumer can SEE it exists and never silently misses a
+      // note the user left under a question. Falls back to the autosaved draft
+      // on timeout/cancel.
+      notes: partial.notes ?? (record.draft?.notes || {}),
       annotations: partial.annotations ?? (record.draft?.annotations || []),
       blockEdits,
       createdAt: record.createdAt,

package/src/ui/blocks.css

@@ -440,6 +440,10 @@
   object-fit: contain;
   object-position: left top;
 }
+/* In full-screen a per-block height must never keep the image small — that
+   height only shapes the inline preview; the detail view needs every pixel.
+   (Belt-and-suspenders alongside the viewer's reapply() on full-screen toggle.) */
+.blk-imagewrap.blk-full .blk-img { max-height: none !important; }
 
 /* ---------- viewer controls (full-screen) ---------- */
 /* The full-screen button lives in a reserved strip ABOVE the visual (user

package/src/ui/blocks.js

@@ -1398,7 +1398,10 @@
       alt: block.alt || 'image',
       loading: 'lazy',
     });
-    if (block.height) img.style.maxHeight = clampHeight(block.height, 360) + 'px';
+    // The per-block height only caps the COMPACT inline preview — the viewer
+    // lifts it on zoom / full-screen so the user can always reach full detail.
+    const fitMaxHeight = block.height ? clampHeight(block.height, 360) : null;
+    if (fitMaxHeight) img.style.maxHeight = fitMaxHeight + 'px';
     img.addEventListener('error', () => {
       container.replaceChildren(el('div', { class: 'blk-error' }, 'Image failed to load'));
     });
@@ -1409,6 +1412,7 @@
         natural: () => (img.naturalWidth > 0 ? { w: img.naturalWidth, h: img.naturalHeight } : null),
         label: 'image',
         comment: wholeBlockComment(ctx, blockId, 'image'),
+        fitMaxHeight,
       });
     if (img.complete && img.naturalWidth > 0) attachImgViewer();
     else img.addEventListener('load', attachImgViewer, { once: true });
@@ -1450,6 +1454,7 @@
     fullOpen = null;
     window.dispatchEvent(new Event('resize'));
     if (c._rlyToolsSync) c._rlyToolsSync(); // re-pin toolbar to its scrolled corner
+    if (c._rlyZoom) c._rlyZoom.reapply(); // restore the compact inline height cap
   }
   document.addEventListener('keydown', (e) => {
     if (e.key === 'Escape' && fullOpen) exitFull();
@@ -1569,6 +1574,13 @@
       const target = opts.zoomEl;
       const nat = opts.natural();
       const z = container._rlyZ;
+      // A per-block height caps only the compact inline preview. The moment the
+      // user zooms in (z !== null) or goes full-screen they want pixel detail, so
+      // lift the cap there; restore it when back to the inline fit view.
+      if (opts.fitMaxHeight != null) {
+        const fit = z === null && !container.classList.contains('blk-full');
+        target.style.maxHeight = fit ? opts.fitMaxHeight + 'px' : 'none';
+      }
       if (z === null || !nat || !nat.w) {
         target.style.width = '100%';
         target.style.maxWidth = nat && nat.w ? Math.ceil(nat.w) + 'px' : '100%';
@@ -1592,10 +1604,10 @@
       return shown > 0 ? shown / nat.w : 1;
     }
     function setZoom(next) {
-      container._rlyZ = next === null ? null : Math.min(5, Math.max(0.2, next));
+      container._rlyZ = next === null ? null : Math.min(8, Math.max(0.2, next));
       apply();
     }
-    container._rlyZoom = { setZoom, currentZ };
+    container._rlyZoom = { setZoom, currentZ, reapply: apply };
 
     const tools = el('div', { class: 'blk-tools' });
 
@@ -1652,6 +1664,7 @@
       fullBtn.textContent = '✕';
       window.dispatchEvent(new Event('resize'));
       container._rlyToolsSync();
+      if (container._rlyZoom) container._rlyZoom.reapply(); // lift any inline height cap
     });
     tools.append(fullBtn);