@khanglvm/relay 0.10.2 → 0.10.3

package/docs/AGENT.md

@@ -5,6 +5,14 @@ rich content blocks (markdown, charts, diagrams, tables, code, custom HTML),
 then **wait for them to click Submit** and read the answers as JSON from stdout.
 No "type 'done' in the terminal", no hand-rolled HTML+server.
 
+**Use relay even in plan mode** — for any clarifying or decision question (Claude
+Code / Codex), route it through a relay board, **not** the native
+`AskUserQuestion` / ask-user tool: that tool is **not** a substitute, even though
+plan-mode guidance suggests it. Do NOT ask in plain terminal text and do NOT
+reach for the native ask tool for anything beyond one trivial yes/no — open a
+board. Reserve the harness's `ExitPlanMode` strictly for the final plan-approval
+gate (it's a mode transition, not a question).
+
 **Tell the user** at the start of your intro text that they can hover chart
 points, diagram nodes, table cells, and any element of a custom-HTML block to
 leave comments, and select text in markdown blocks to annotate — their comments

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@khanglvm/relay",
-  "version": "0.10.2",
+  "version": "0.10.3",
   "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

@@ -31,8 +31,15 @@ Schema).** The essentials are below.
 | "Show me the diff" / git diff / code changes / before-after | **rly** (`diff` block — run `git diff`, render it; never dump it in the terminal) |
 | A demo, screen recording or walkthrough | **rly** (`video` block) |
 | Point the user at a file to open (log, capture, report) | **rly** (a clickable local file-link in markdown) |
+| Plan-mode clarifying question (Claude Code / Codex) | **rly** (not AskUserQuestion / the native ask tool) |
 | Something you can decide yourself from context | neither — just decide |
 
+This holds **in plan mode** too: route every clarifying or decision question
+through relay — the native `AskUserQuestion` / ask-user tool is **not** a
+substitute, even though plan-mode guidance suggests it. Reserve the harness's
+`ExitPlanMode` strictly for the final plan-approval gate (it's a mode
+transition, not a question).
+
 Once the user has answered one board in a session, prefer boards for later
 question rounds too — they've shown they engage with them. Batch related
 questions into ONE board rather than opening several in a row.

package/src/cli.js

@@ -799,8 +799,12 @@ function stampSkillVersion() {
 const SKILL_RULES = `## relay — ask & show in the browser, not the terminal
 
 - Need the user's decisions, feedback, requirements, or approval (anything
-  beyond one trivial yes/no)? Do NOT ask in plain terminal text. Build a board
-  spec and run: \`rly ask --file spec.json --detach\`, then \`rly wait <boardId>\`.
+  beyond one trivial yes/no)? Do NOT ask in plain terminal text **and do NOT use
+  the native \`AskUserQuestion\` / ask-user tool** — for anything beyond one
+  trivial yes/no, open a relay board. Build a board spec and run:
+  \`rly ask --file spec.json --detach\`, then \`rly wait <boardId>\`. **This holds
+  in plan mode too** — route clarifying/decision questions through relay there as
+  well; reserve \`ExitPlanMode\` for the final plan-approval gate only.
 - Presenting a plan, structure, architecture, data, or a prototype? Show a
   relay board with mermaid/graphviz/chart/table/code/diff/video/image/html
   blocks — never ASCII diagrams or walls of prose.