replicas-cli 0.2.757 → 0.2.758

package/dist/index.cjs

@@ -24152,7 +24152,7 @@ Use subagents for broad, independent analysis when available, but read the files
 
 The user may be watching the panel or may have walked away, so ask early and wait late:
 
-1. Right after step 1, request every secret you found in one batch. \`required\` means the app cannot run locally without it; leave it \`false\` for anything you can work around.
+1. Right after step 1, request in one batch only the secrets you need to run the app and test its main flow (usually including sign-in) that you cannot replace locally. First check for a local stand-in the app supports, such as a local database, an auth emulator, or documented test credentials. Do not request values you can generate, values that duplicate another key, or values that are not secret, and list optional integrations in the proposal instead of requesting them. \`required\` means the app cannot start, or its main flow cannot be tested, without it.
 
 \`\`\`bash
 replicas environment-setup request-variables --file /tmp/variables.json
@@ -24161,24 +24161,23 @@ replicas environment-setup request-variables --file /tmp/variables.json
 \`\`\`json
 {
   "variables": [
-    { "key": "DATABASE_URL", "description": "Postgres connection string; a local docker compose database works", "required": false },
-    { "key": "STRIPE_SECRET_KEY", "description": "Stripe test-mode key; checkout cannot run without it", "required": true }
+    { "key": "FIREBASE_PRIVATE_KEY", "description": "Service account private key for a dev Firebase project; sign-in cannot be tested without it", "required": true }
   ]
 }
 \`\`\`
 
 2. Keep working on everything that does not need the values. The request appears in the Environment panel next to the chat; the user types values there (stored encrypted on the environment, never in chat) or skips them.
-3. At the point you actually need a value, block on it:
+3. At the point you actually need a value, say in chat which keys you are waiting for and why, then block on it once:
 
 \`\`\`bash
-replicas environment-setup wait-variables --timeout 5m
-replicas environment-setup wait-variables --keys STRIPE_SECRET_KEY
+replicas environment-setup wait-variables --timeout 15m
+replicas environment-setup wait-variables --keys FIREBASE_PRIVATE_KEY --timeout 15m
 \`\`\`
 
 Without \`--keys\` it waits for every pending required key. It returns when the keys are provided or skipped, or when the time runs out, and prints which happened. Provided keys are exported for every new shell; restart anything you started with \`replicas service start\` before that point so it picks them up. Never print the values.
-4. For anything skipped or unanswered, use the safest local substitute (local database, mock, documented test value), say so in the verification rows, and list the key as required in the proposal. A key the user skipped is not asked again; do not resend it.
+4. For anything skipped or still unanswered after that wait, use the safest local substitute (local database, mock, documented test value), say so in the verification rows, and list the key in the proposal, marked required only if the app cannot start or its main flow cannot be tested without it. A key the user skipped is not asked again; do not resend it.
 5. Values the user provided are already saved on the environment. Still list those keys in the proposal so the review shows them as set.
-6. Requests are only accepted before you propose. Anything still missing after that goes into the proposal as a required variable, which the user fills in at review.
+6. Requests are only accepted before you propose. Anything still missing after that goes into the proposal for the user to fill in at review.
 
 ## 2. Install and run
 
@@ -24191,7 +24190,7 @@ Work from the smallest failing layer, in this workspace:
 
 Use the repository's pinned package manager and lockfile. Do not upgrade dependencies, rewrite lockfiles, or change application code to make setup pass; environment configuration and narrowly necessary fixes to setup scripts are in scope. Do not deploy, publish, or touch production resources.
 
-When something needs a secret you do not have, request it and run \`wait-variables\` at the point you need it (see "Asking for variables"). If it is skipped or unanswered, use the safest local substitute, keep going, and record the variable as required in the proposal with a clear description. Never invent or paste secret values anywhere.
+When something needs a secret you do not have, request it and run \`wait-variables\` at the point you need it (see "Asking for variables"). If it is skipped or unanswered, use the safest local substitute, keep going, and record the variable in the proposal with a clear description. Never invent or paste secret values anywhere.
 
 ## 3. Verify and record
 
@@ -28012,7 +28011,7 @@ var headlessFilesystemAgentResultSchema = external_exports.object({
 });
 
 // ../shared/src/cli-version.ts
-var CLI_VERSION = "0.2.757";
+var CLI_VERSION = "0.2.758";
 
 // ../shared/src/version.ts
 function compareVersions(v1, v2) {

package/package.json

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