replicas-cli 0.3.312 → 0.3.314

package/dist/index.cjs

@@ -20801,9 +20801,9 @@ var init_prompts = __esm({
     MOTHERSHIP_INSTRUCTIONS_TAG = "multitask_instructions";
     BOARD_ANSWER_NOTE = "The user answered on the board.";
     BOARD_RULES = `- The board, a live status page you keep with \`${REPLICAS_MCP_TOOLS.updateBoard}\` in the Ships pane beside this chat, is the user's one view of the work: keep it covering every ship, pull request, deploy, blocker and ask. Show ships, pull requests and Linear tickets as ship, pr and linear blocks, which stay current on their own, instead of describing their status. Start with sections Needs you, Ready to review, Working, Shipping and Done, and add blocks and buttons whenever they help the user act.
-- A ship with open pull requests is not done when it sends \`finished\`: Replicas fixes their CI failures and review comments automatically, then sends \`ready\` or \`needs_attention\`. On \`needs_attention\`, direct the ship, or put the decision to the user if it needs one.
+- A ship with open pull requests is not done when it sends \`finished\`: Replicas fixes their CI failures and review comments automatically, then sends \`ready\` or \`needs_attention\`. On \`needs_attention\`, direct the ship, or put the decision in Needs you if it needs the user.
 - On every ship event and every answer the user gives on the board (marked "${BOARD_ANSWER_NOTE}"), act with tools on the answer or on any work the event unblocks, such as starting the next task once a pull request merges, update the board, and end your turn with no text at all. Never write an acknowledgement such as "Noted.", even if earlier turns did.
-- The chat is like texting an assistant: the user sees only your last message of each turn, never your tool calls or earlier text. Write there only to answer the user, to ask a decision only they can make in a line or two, or to say in a line, with links, that work they asked for is done. Everything else, especially progress, goes on the board: spend your effort there, not in chat. Put each decision on the board too, as a choice when it has clear options, and ask it in chat once. Never restate the board in chat: no status tables, per-ship lists or summaries of what ships did.
+- The chat is like texting an assistant: the user sees only your final reply to each message they type, never your tool calls, earlier text, or anything written on a ship event or board answer. Write in chat only to reply to what the user just asked, in a line or two with links. Anything that needs the user later, such as a decision, a review or finished work, goes in Needs you on the board, as a choice when it has clear options, never in chat. Never restate the board in chat: no status tables, per-ship lists or summaries of what ships did.
 - When the user picks a choice or clicks a button that messages or merges, Replicas removes that item from the board for you. Add it back, or a new item, only if the user is still needed.
 `;
     MOTHERSHIP_INSTRUCTIONS_BLOCK = new RegExp(`\\s*<${MOTHERSHIP_INSTRUCTIONS_TAG}>\\n([\\s\\S]*?)\\n</${MOTHERSHIP_INSTRUCTIONS_TAG}>`);
@@ -31978,7 +31978,7 @@ var CLI_VERSION;
 var init_cli_version = __esm({
   "../shared/src/cli-version.ts"() {
     "use strict";
-    CLI_VERSION = "0.3.312";
+    CLI_VERSION = "0.3.314";
   }
 });
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "replicas-cli",
-  "version": "0.3.312",
+  "version": "0.3.314",
   "description": "CLI for managing Replicas workspaces - SSH into cloud dev environments with automatic port forwarding",
   "main": "dist/index.cjs",
   "bin": {