viveworker 0.8.8 → 0.8.10

package/scripts/viveworker-claude-hook.mjs

@@ -148,7 +148,7 @@ async function handlePermissionRequest() {
   } else if (toolName === "Bash") {
     approvalKind = "command";
     const cmd = String(toolInput.command || "");
-    messageText = `Command approval needed.\n\`\`\`\n${cmd.slice(0, 500)}\n\`\`\``;
+    messageText = `Command approval needed.\n\`\`\`\n${escapeMarkdownCodeFenceBody(cmd.slice(0, 500))}\n\`\`\``;
   } else if (toolName === "ExitPlanMode") {
     approvalKind = "plan";
     messageText = "Plan approval needed.";
@@ -708,6 +708,10 @@ function sanitizeForPath(s) {
   return s.replace(/[^a-zA-Z0-9_-]/gu, "_").slice(0, 64);
 }
 
+function escapeMarkdownCodeFenceBody(text) {
+  return String(text || "").replace(/```/gu, "\\`\\`\\`");
+}
+
 function encodeFilePathForSnapshot(filePath) {
   return filePath.replace(/[/\\]/gu, "_") + ".snap";
 }

package/skills/viveworker-control-plane/SKILL.md

@@ -34,9 +34,14 @@ Keep onboarding calm and step-by-step. Do not make the user debug config files u
 ## Tool Selection
 
 - Use `viveworker_notify` for informational milestones that should appear on the phone or timeline, such as "build finished", "review ready", or "agent is blocked".
+- Use `viveworker_stats` when the user asks for viveworker package adoption or usage stats.
+- Use `viveworker_share_list` when the user asks what is currently in File Share or asks for share usage metrics.
+- Use `viveworker_a2a_activity` or `viveworker_a2a_card` when troubleshooting A2A activity or local agent-card settings.
+- Use `viveworker_moltbook_list`, `viveworker_moltbook_show`, or `viveworker_moltbook_thread` when inspecting Moltbook inbox comments or threads.
 - Use `viveworker_ask` when the next step depends on a human preference, missing requirement, or choice that should not be guessed.
 - Use `viveworker_request_approval` before actions that are externally visible, hard to undo, risky, sensitive, delegated, paid, or likely to surprise the user.
 - Use `viveworker_share_file` when the user wants a workspace deliverable shared as a limited File Share URL. Good fits include `.html`, `.htm`, `.pdf`, `.png`, `.jpg`, `.jpeg`, `.gif`, `.webp`, and `.csv`.
+- Use `viveworker_share_replace` when the user wants to replace or update the file behind an existing File Share slug.
 - Use `viveworker_thread_share` when context should move to another Codex session, Claude session, or viveworker inbox while preserving a human-visible handoff.
 - Use `viveworker_send_a2a_task` only for registered A2A target aliases and bounded tasks with clear acceptance criteria.
 
@@ -47,10 +52,12 @@ Keep onboarding calm and step-by-step. Do not make the user debug config files u
 - Include relevant file refs, but never include secrets, tokens, private keys, or unnecessary file contents.
 - Treat timeout, rejection, or transport failure as "not approved". Do not continue as if approval was granted.
 - After the tool returns, summarize the decision or returned artifact to the user.
+- Read-only inspection tools use fixed command allowlists. Do not try to route arbitrary shell commands or side-effectful viveworker CLI actions through MCP.
 
 ## File Share Rules
 
 - Share only files inside the workspace root.
+- Replacing an existing share changes what existing recipients see at that URL; require phone approval and make that consequence clear.
 - Do not share `.env`, credential files, private keys, `.ssh`, `.aws`, `.gnupg`, or secret-looking paths.
 - Prefer sharing final deliverables, not internal source files, unless the user explicitly asks.
 - For unsupported file types, explain the accepted types and suggest exporting to HTML, PDF, image, or CSV first.

package/templates/CLAUDE.viveworker.md

@@ -23,10 +23,18 @@ Then restart the Claude Code session. If the tools are not available, ask the us
 ## Tools
 
 - `viveworker_status` checks bridge, pairing, Remote connection, A2A, File Share, and Moltbook state.
+- `viveworker_stats` reads package adoption and usage stats.
+- `viveworker_share_list` lists File Share uploads and optional usage metrics.
+- `viveworker_a2a_activity` reads local A2A activity.
+- `viveworker_a2a_card` reads the current local A2A agent card.
+- `viveworker_moltbook_list` lists Moltbook inbox comments.
+- `viveworker_moltbook_show` reads one Moltbook comment.
+- `viveworker_moltbook_thread` reads the thread for one Moltbook comment.
 - `viveworker_notify` sends an informational phone notification and records a timeline entry.
 - `viveworker_ask` asks the paired phone a question and waits for the answer.
 - `viveworker_request_approval` asks the phone to approve or reject a proposed action.
 - `viveworker_share_file` uploads a workspace file to File Share after phone approval. For password-protected handoff, pass `tokenize: true` to return a short-lived passwordless `?t=` URL.
+- `viveworker_share_replace` replaces the file behind an existing File Share slug after phone approval.
 - `viveworker_share_link` mints a short-lived passwordless `?t=` URL for an existing password-protected File Share slug after phone approval.
 - `viveworker_thread_share` shares context into another Codex / Claude / inbox thread.
 - `viveworker_send_a2a_task` sends a task to a registered A2A target after phone approval.
@@ -36,9 +44,11 @@ Then restart the Claude Code session. If the tools are not available, ask the us
 - If the user says "ask me on my phone", "スマホに聞いて", or a short decision blocks progress, use `viveworker_ask`.
 - If the user asks you to proceed with a risky, external, irreversible, payment-related, or user-visible action, use `viveworker_request_approval`.
 - If the user asks for a report, prototype, screenshot, PDF, CSV, or standalone HTML to become a shareable link, use `viveworker_share_file`.
+- If the user asks to replace or update the file at an existing File Share link, use `viveworker_share_replace`.
 - If the user asks for a password-protected share but wants the recipient to open it without knowing the password, use `viveworker_share_file` with `password` and `tokenize: true`, or use `viveworker_share_link` for an existing slug.
 - If the user says "share this with Codex/Claude", "Aの内容をBに共有して", or wants context handed to another session, use `viveworker_thread_share`.
 - If the user wants another registered agent to do work, use `viveworker_send_a2a_task`.
+- For troubleshooting or inspection, prefer the read-only MCP tools above before asking the user to run CLI commands.
 
 ## Prompting rules
 
@@ -64,6 +74,7 @@ Claude may not automatically notice newly shared messages from another session.
 
 - MCP is a control-plane surface, not a shell executor.
 - Do not run shell strings through MCP.
-- File Share and A2A task sending require phone approval.
+- Read-only inspection tools use fixed command allowlists and should not be used to mutate local state.
+- File Share uploads/replacements and A2A task sending require phone approval.
 - Use registered A2A aliases only; do not ask the user to paste API keys into prompts.
 - Prefer `viveworker_status` before troubleshooting a missing notification, stale pairing, or remote connectivity issue.