@khanglvm/relay 0.14.2 → 0.15.0

package/README.md

@@ -93,7 +93,7 @@ actually needs them.
 | `rly help` | every command at a glance |
 | `rly git pick` / `rly git cherry-pick` | choose commit actions and rank the order directly on a board; add `--code` to cherry-pick with split code review and per-hunk Apply/Skip/Hold |
 | `rly git conflict [files…]` | auto-detect unmerged conflict files, or open specific local paths, and return resolved content in `result.blockEdits` |
-| `rly share <board-id>` | activate/list/revoke same-Wi-Fi reviewer or collaborator links for a running browser board |
+| `rly share <board-id>` | activate/list/revoke same-Wi-Fi collaborator, reference-only reviewer, or read-only links for a running browser board |
 | `rly view <file.md> …` | open a quick read-only board that renders local markdown file(s), data files, or PDFs — library-free; great for plans, READMEs, reports, quotes |
 | `rly install --target <agent>` | write relay's rules into an agent's instruction file — `claude` `codex` `cursor` `copilot` `kiro` `windsurf` `cline` `gemini` `opencode` `droid` `agents`; `--all`, `--scope`, `--print`, `--list` |
 | `rly upgrade` | update the CLI **and** refresh the skill in one step (safe around open boards; `--dry-run`, `--cli-only`, `--skill-only`) |
@@ -177,7 +177,8 @@ npm test     # smoke tests with no external services (spawns real servers, fake-
   whose connection drops blocks further input instead of losing it, and
   `rly rescue <id>` re-serves on the same port so an open tab reconnects. Active
   same-Wi-Fi share links stay tied to the board and survive a same-port re-serve
-  until revoked.
+  until revoked. Reviewer submissions are isolated, reference-only side reviews
+  that never finish the owner's board; read-only links cannot mutate feedback.
 - Still **zero npm runtime dependencies**, offline, and cross-platform. Vendored
   browser libraries are loaded only for boards that need them.
 

package/docs/AGENT.md

@@ -79,19 +79,24 @@ click the topbar **Share** icon, or you can manage the same links for the user:
 
 ```sh
 rly share b-xxxxx                         # list active share roles
-rly share b-xxxxx --role review           # reviewer: add comments only
-rly share b-xxxxx --role collab           # collaborator: edit/comment/submit
+rly share b-xxxxx --role review           # reviewer: answer/comment + submit a side review
+rly share b-xxxxx --role collab           # collaborator: edit/comment/final-submit as owner-authorized
+rly share b-xxxxx --role read             # read-only viewer: no answers/comments/submit
 rly share b-xxxxx --role review --revoke  # revoke one role
 rly share b-xxxxx --revoke --all          # revoke all active links
 ```
 
-Use `review` unless the user explicitly wants the other device to submit as the
-owner. Reviewers cannot change answers, submit, edit comments, or delete
-comments; their autosaves merge new comments into the existing draft.
-Collaborators can edit answers, comment, open allowed local file links, and
-submit. Shared viewers refresh from the live draft when another viewer saves,
-deferred while someone is typing/commenting. Active share links keep the same
-token across a same-port `rly reopen`/`rly rescue` until revoked.
+Use `review` for independent feedback: each browser gets an isolated review
+draft and may answer, comment, and submit, but the submission is stored as a
+**reference-only side review**. It does not finish the board, wake the agent, or
+complete `rly wait`; the owner (or an owner-authorized collaborator) must still
+submit the final answer. `rly result <id>` exposes current side-review drafts and
+submissions on demand under `sideReviews`, clearly marked `referenceOnly:true`.
+Use `read` when the other device should only view the board and existing
+feedback. Read-only viewers cannot answer, comment, edit blocks, open local file
+links, or submit. Collaborators retain owner-authorized edit/comment/final-submit
+permission. Active links keep the same token across a same-port
+`rly reopen`/`rly rescue` until revoked.
 
 ## Inline mode — relay as an MCP App (Claude & Codex apps)
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@khanglvm/relay",
-  "version": "0.14.2",
+  "version": "0.15.0",
   "description": "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, read answers as JSON — in a local browser board OR rendered INLINE inside the Claude & Codex apps as an MCP App (SEP-1865).",
   "keywords": [
     "ai-agents",

package/skills/relay/SKILL.md

@@ -189,16 +189,22 @@ with `rly share`:
 rly share b-xxxxx                         # list active share roles
 rly share b-xxxxx --role review           # activate a reviewer link
 rly share b-xxxxx --role collab           # activate a collaborator link
+rly share b-xxxxx --role read             # activate a read-only link
 rly share b-xxxxx --role review --revoke  # revoke one role
 rly share b-xxxxx --revoke --all          # revoke all active share links
 ```
 
-Use `review` when the other device should add comments only. Reviewers cannot
-change answers, submit, edit comments, or delete comments; their autosaves merge
-new comments into the existing draft. Use `collab` only when the user explicitly
+Use `review` for independent feedback. Each reviewer browser gets an isolated
+draft and can answer, comment, and submit a **reference-only side review**. That
+submission never finishes the board or wakes/completes the waiting agent; the
+owner (or owner-authorized collaborator) must still provide the final answer.
+When the owner asks for current reviewer input, run `rly result <id>` and inspect
+`sideReviews.submissions` plus `sideReviews.drafts`; both are explicitly marked
+reference-only. Use `read` for a view-only link with no answers, comments, block
+edits, local-file opening, or submit. Use `collab` only when the user explicitly
 wants that device to act as the owner: collaborators can edit answers, comment,
-open allowed local file links, and submit. Shared viewers refresh from the live
-draft when another viewer saves, deferred while someone is typing/commenting.
+open allowed local file links, and final-submit. Shared viewers refresh from the
+relevant live draft when another viewer in the same role/session saves.
 Active share links are durable too: they keep the same token across a same-port
 `rly reopen`/`rly rescue` until `rly share --revoke` disables them.
 

package/src/cli.js

@@ -761,21 +761,27 @@ async function cmdWaitLoop(id, deadline, opts) {
 
 async function cmdResult(args) {
   const record = mustLoad(args._[0]);
+  const sideReviews = {
+    referenceOnly: true,
+    note: 'Side reviews are reference only. Wait for the board owner (or owner-authorized collaborator) to submit the final answer.',
+    submissions: Array.isArray(record.sideReviews) ? record.sideReviews : [],
+    drafts: record.reviewDrafts && typeof record.reviewDrafts === 'object' ? record.reviewDrafts : {},
+  };
   if (record.result && record.result.finishedAt) {
-    printResult(record.result);
+    printResult({ ...record.result, sideReviews });
     return exitCodeFor(record.result.status);
   }
   const running = loadRunning(record.id);
   if (running && isAlive(running.pid)) {
     // While open, expose the real-time autosaved draft so agents can peek, plus
     // best-effort presence (whether the user is still viewing/focused/active).
-    const out = { status: 'open', boardId: record.id, url: running.url, draft: record.draft ?? null };
+    const out = { status: 'open', boardId: record.id, url: running.url, draft: record.draft ?? null, sideReviews };
     const presence = await fetchPresence(running.url);
     if (presence) out.presence = presence;
     printResult(out); // draft can hold many annotations — sidecar it too
     return 0;
   }
-  printResult({ status: 'lost', boardId: record.id, draft: record.draft ?? null });
+  printResult({ status: 'lost', boardId: record.id, draft: record.draft ?? null, sideReviews });
   return 5;
 }
 
@@ -785,9 +791,10 @@ async function cmdShare(args) {
   if (!running || !isAlive(running.pid)) {
     throw new CliError(`board "${record.id}" is not running. Use \`rly reopen ${record.id} --detach\` first.`, 5);
   }
-  const role = args.all ? 'all' : args.role;
-  if (role !== undefined && !['collab', 'review', 'all'].includes(role)) {
-    throw new CliError('--role must be collab or review.', 4);
+  let role = args.all ? 'all' : args.role;
+  if (role === 'readonly' || role === 'read-only') role = 'read';
+  if (role !== undefined && !['collab', 'review', 'read', 'all'].includes(role)) {
+    throw new CliError('--role must be collab, review, or read.', 4);
   }
   const shareUrl = new URL('/api/share', running.url);
   let res;
@@ -1100,8 +1107,10 @@ the user should view — put it in relay instead of printing it.**
   option its own visual (\`options[].blocks\`) so the user picks by looking.
 - Same-Wi-Fi sharing is locked by default. When the user wants another device to
   review or co-fill a running board, manage explicit links with \`rly share <id>\`:
-  \`--role review\` creates a comments-only reviewer link, \`--role collab\` creates
-  an edit/comment/submit link, and \`--revoke\` disables active links. Active
+  \`--role review\` creates an answer/comment link whose submissions are reference-only
+  side reviews (\`rly result\` exposes them but they never complete \`rly wait\`),
+  \`--role collab\` creates an owner-authorized edit/comment/final-submit link,
+  \`--role read\` creates a view-only link, and \`--revoke\` disables active links. Active
   share links are durable across same-port \`rly reopen\`/\`rly rescue\` until
   revoked.
 - **There's a purpose-built component for most content — use the MOST SPECIFIC one,
@@ -1610,8 +1619,9 @@ USAGE
                                         read that file if your shell truncates stdout; never pipe to head/tail
   rly result <id>                     result/status now (includes live autosaved draft + presence while open)
   rly share <id>                      list active same-Wi-Fi share links for a running board
-  rly share <id> --role review        activate a reviewer link (comments only)
-  rly share <id> --role collab        activate a collaborator link (edit/comment/submit)
+  rly share <id> --role review        reviewer: answer/comment/submit a reference-only side review
+  rly share <id> --role collab        collaborator: edit/comment/final-submit as owner-authorized
+  rly share <id> --role read          activate a read-only viewer link
   rly share <id> --role review --revoke
                                       revoke one share role; use --revoke --all to disable all roles
                                       active links survive same-port reopen/rescue until revoked