replicas-cli 0.2.802 → 0.2.803

package/dist/index.cjs

@@ -24067,10 +24067,11 @@ Explore a codebase, get it running in this workspace, verify it end to end, and
 Use this when:
 - This workspace was started as an environment setup run (\`replicas environment-setup status\` succeeds)
 - The user asks you to set up, configure, audit, or improve a Replicas environment for a repository
-- The user asks what should go in a start hook, warm hook, or environment system prompt`;
+- The user asks what should go in a start hook, warm hook, or environment system prompt
+- A warm pool, warm hook, or start hook is failing, or the fix you found belongs in the environment rather than the repository`;
 var REFERENCE3 = `# Environment setup (agent-led)
 
-Use this workflow to make a repository fully usable by Replicas background agents: agents booted from the environment should be able to install, run, test, verify, and demo changes without a human babysitting them. The result of the workflow is a **proposal**, never a direct change: the user reviews, edits, and saves it in the Environment panel next to the chat.
+Use this workflow to make a repository fully usable by Replicas background agents: agents booted from the environment should be able to install, run, test, verify, and demo changes without a human babysitting them. In a setup run, the result is a **proposal**, never a direct change: the user reviews, edits, and saves it in the Environment panel next to the chat. Outside a setup run, see below.
 
 ## Mental model
 
@@ -24102,7 +24103,14 @@ replicas environment-setup wait-variables [-t 5m]
 
 \`status\` prints the environment, repositories, current steps, and variable requests. \`request-variables\` returns immediately; \`wait-variables\` blocks until the required values arrive, are skipped, or the time runs out. Step statuses are \`pending\`, \`in_progress\`, \`completed\`, and \`skipped\`. Step keys, in order: \`understand\`, \`install\`, \`verify\`, \`configure\`, \`propose\`. Mark the first step \`in_progress\` before your first tool call, keep exactly one step \`in_progress\`, and mark a step \`completed\` only after its work actually succeeded. Use \`skipped\` when something genuinely cannot run (for example no browser UI to record) and say so in the proposal.
 
-If \`replicas environment-setup status\` reports that there is no active setup run, the user asked for this in an ordinary workspace. Follow the same discovery and verification steps, then present the configuration in chat; apply it with \`replicas environment ...\` and \`replicas automation ...\` only when the user explicitly asks you to.
+If \`replicas environment-setup status\` reports that there is no active setup run, you are in an ordinary workspace, either because the user asked for this or because the fix you found while debugging belongs in the environment. Follow the same discovery and verification steps, show the exact change in chat, and offer to apply and test it yourself. Ask the user before changing the environment, since it affects every workspace built from it. Once they approve:
+
+- Warm hook: \`replicas environment warm-hooks save-test <env> -f <file>\` runs it in an isolated sandbox and saves it only if it passes.
+- Start hook: \`replicas environment start-hooks test <env> -f <file>\`, then \`replicas environment start-hooks save <env> -f <file>\` with the same file once it passes.
+- Variables and files: apply with \`replicas environment vars set\` or \`files set\`, then confirm with \`vars list\` or \`files list\`.
+- Automations: apply with \`replicas automation ...\`, then read back with \`replicas automation get <id>\`.
+
+When a test fails, fix the earliest failure and test again instead of saving. If the fix materially changes what the user approved, show the revised change and ask again before saving. Report what you changed and the test result.
 
 ## 1. Understand the codebase
 
@@ -24294,7 +24302,7 @@ After \`propose\` succeeds, mark the \`propose\` step completed and send one mes
 Review the start hook, warm hook, system prompt, variables, and automations in the Environment panel on the right. Edit anything inline, then select **Save configuration**. Ask me here if you want changes and I will revise the proposal.
 \`\`\`
 
-Keep it under 250 words plus the lists. Do not paste the hooks or system prompt into chat; the panel shows them. Never imply the configuration was saved: saving is the user's action.
+Keep it under 250 words plus the lists. Do not paste the hooks or system prompt into chat; the panel shows them. Never imply the configuration was saved: in a setup run, saving is the user's action.
 
 ## Safety
 
@@ -24306,7 +24314,7 @@ Keep it under 250 words plus the lists. Do not paste the hooks or system prompt
 var ENVIRONMENT_SETUP_ABILITY = {
   label: "Environment setup",
   description: "Explore a codebase, verify it runs, and propose environment hooks, a system prompt, variables, and automations for review.",
-  bullet: "- Setting up, auditing, or improving a Replicas environment for a repository (hooks, system prompt, variables, automations)",
+  bullet: "- Setting up, auditing, fixing, or improving a Replicas environment for a repository (hooks, system prompt, variables, automations), including a failing warm pool or hook",
   section: SECTION3,
   referenceFile: { name: "ENVIRONMENT-SETUP.md", content: REFERENCE3 }
 };
@@ -28047,7 +28055,7 @@ var headlessAgentRequestSchema = external_exports.object({
 });
 
 // ../shared/src/cli-version.ts
-var CLI_VERSION = "0.2.802";
+var CLI_VERSION = "0.2.803";
 
 // ../shared/src/version.ts
 function compareVersions(v1, v2) {

package/package.json

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