replicas-engine 0.1.100 → 0.1.101

package/dist/src/index.js

@@ -1091,7 +1091,7 @@ function parseReplicasConfigString(content, filename) {
 }
 
 // ../shared/src/engine/environment.ts
-var DAYTONA_SNAPSHOT_ID = "13-04-2026-relay-codex-gating";
+var DAYTONA_SNAPSHOT_ID = "13-04-2026-royal-york";
 
 // ../shared/src/engine/types.ts
 var DEFAULT_CHAT_TITLES = {
@@ -3349,7 +3349,15 @@ Your primary resource is your context window. Every tool call result, every code
 
 ## Parallel execution
 
-You can spawn multiple subagents in parallel by making multiple spawn_agent tool calls in a single response. Do this whenever you have independent tasks \u2014 do NOT call them sequentially if they don't depend on each other. For example, if you need to test three endpoints, spawn three subagents in one response, not one after another.
+You can spawn multiple subagents in parallel by making multiple spawn_agent tool calls in a single response. Do this whenever you have truly independent tasks \u2014 do NOT call them sequentially if they don't depend on each other. For example, if you need to test three endpoints, spawn three subagents in one response, not one after another.
+
+**IMPORTANT \u2014 recognize implicit dependencies:** Tasks are NOT independent when one task's output shapes what the other needs to know. The most common case: if you are building both a backend and a frontend, the frontend depends on the backend \u2014 it needs to know the API endpoints, request/response shapes, data models, etc. You MUST complete the backend subagent first, then use its output to write an informed prompt for the frontend subagent. Other examples of implicit dependencies:
+- Building a library/SDK and code that consumes it
+- Creating a database schema and code that queries it
+- Implementing an API and writing tests for that API
+- Any producer/consumer relationship where the consumer needs to match the producer's interface
+
+When in doubt about whether tasks are independent, run them sequentially. The cost of unnecessary sequencing is just latency; the cost of incorrect parallelization is a subagent working blind and producing incompatible code.
 
 ## Testing your work
 
@@ -3369,6 +3377,19 @@ The default subagent timeout is 10 minutes. For tasks you expect to take longer
 
 ${agentSelectionLines}
 
+## Incremental progress on complex tasks
+
+For complex, multi-step tasks (building a full feature, large refactors, new systems), do NOT try to accomplish everything in one shot. Instead, take an incremental commits approach \u2014 work step by step, feature by feature, commit by commit.
+
+**How to work incrementally:**
+- Break the task into discrete, meaningful steps (e.g., schema first, then API endpoints, then frontend, then tests).
+- After each step, commit the work in a clean state before moving on. By clean state, we mean the kind of code that is stable, does not introduce major bugs, the code is orderly and well-documented. A good rule of thumb is: could another agent or human pick up from this commit and continue building without having to clean up an unrelated mess?
+- Review the results of each step before starting the next. This lets you catch issues early, adjust course, and carry accurate context forward about what was already built.
+
+**Why this matters:** Trying to build an entire system in one shot tends to produce lower-quality, harder-to-debug output. Incremental commits create natural checkpoints \u2014 if something goes wrong, you only lose one step's worth of work, not everything. This approach also preserves your context window since you track high-level progress without holding all the implementation details.
+
+**When to use this:** Apply incremental progress for tasks that span multiple components, require many files to be changed, or would otherwise be a large, complex, time-consuming piece of work. For simple, self-contained tasks (a bug fix, a single endpoint, a small refactor), working in one pass is fine.
+
 ## Effective delegation
 
 - Subagents start with a blank context. Include all relevant file paths, code snippets, requirements, and constraints in the prompt.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "replicas-engine",
-  "version": "0.1.100",
+  "version": "0.1.101",
   "description": "Lightweight API server for Replicas workspaces",
   "type": "module",
   "main": "dist/src/index.js",