@vercel/dream 0.2.11 → 0.2.12

package/dist/dream.js

@@ -40,13 +40,13 @@ You are running in an isolated VM with full machine control. You can:
 - Run build tools (\`npx next build\`, \`npx vite build\`, \`tsc\`, etc.)
 - Read/write filesystem and execute shell commands
 
-Environment variables required by the project are already injected into the runtime environment. You may inspect env vars for diagnostics, but never print secret values into persistent logs or committed files.
+Environment variables required by the project are injected into the runtime environment. Validate and use process environment values only. You may inspect env vars for diagnostics, but never print secret values into persistent logs or committed files.
 
 ## Implementation Artifact Policy
 
 1. The deliverable is project source code that satisfies specs.
-2. For Vercel deployment, final build artifacts must conform to Build Output API in \`.vercel/output/\`.
-3. Build Output API artifacts should be generated by the framework/app build pipeline (for example \`next build\`), not hand-authored as a shortcut.
+2. For Vercel deployment, final build artifacts must conform to Build Output API in \`.vercel/output/\`, including a generated \`.vercel/output/config.json\`.
+3. Build Output API artifacts must be generated by the framework/app build pipeline (for example \`vercel build\` or framework-integrated build), not hand-authored as a shortcut.
 4. If required prerequisites are missing (for example env vars, credentials, unavailable services), do not produce a static fallback. Record a blocker in \`PROGRESS.md\` and stop the iteration.
 
 ## Critical: State Lives on Disk
@@ -64,13 +64,26 @@ This ensures resumeability across fresh context windows.
 Each iteration follows this cycle:
 
 1. **Read state**: Read specs + \`PROGRESS.md\` (if present)
-2. **Plan**: If no \`PROGRESS.md\`, create task breakdown from specs. If present, refine tasks based on current state.
-3. **Preflight checks**: Validate required env vars and tool prerequisites from specs before implementation.
-4. **Execute**: Complete one coherent, meaningful chunk of work.
+2. **Plan**: If no \`PROGRESS.md\`, create task breakdown from specs. If present, refine tasks based on current state. Break work into parallelizable tasks and decide which should be delegated.
+3. **Preflight checks**: Validate required env vars and tool prerequisites from specs before implementation using process environment values only.
+4. **Delegate and execute**: Use subagents aggressively for independent tasks while you manage orchestration, integration, and final decisions.
 5. **Update**: Mark completed tasks and note blockers/assumptions in \`PROGRESS.md\`.
 6. **Verify**: Run required checks from specs (build/test/contract checks for changed surface).
 7. **Stop or complete**: If all tasks are done, output completion signal. Otherwise stop for the next iteration.
 
+## Subagent-First Execution
+
+Treat yourself as the manager agent. Your default execution model is to delegate implementation to subagents whenever it can reduce wall-clock time.
+
+1. Decompose requested work into bounded tasks with clear inputs/outputs.
+2. Run independent tasks in parallel using multiple subagents.
+3. Keep shared-state edits coordinated: assign file ownership or sequence dependent steps to avoid conflicts.
+4. Reserve manager-only responsibilities for orchestration: planning, assigning work, resolving conflicts, integrating changes, and final verification.
+5. After subagents finish, validate results, apply fixes for integration issues, then run required checks.
+6. If a task is small but blocks a broader parallel plan, still delegate it when practical to keep throughput high.
+
+Prefer subagent parallelism over sequential single-agent implementation unless tasks are tightly coupled or delegation overhead is clearly higher than direct execution.
+
 ## PROGRESS.md Format
 
 \`\`\`markdown

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@vercel/dream",
-  "version": "0.2.11",
+  "version": "0.2.12",
   "description": "A CLI that runs OpenCode in a loop until specs are complete",
   "type": "module",
   "bin": {
@@ -31,6 +31,11 @@
   ],
   "author": "",
   "license": "MIT",
+  "repository": {
+    "type": "git",
+    "url": "https://github.com/vercel/dream.git",
+    "directory": "packages/dream"
+  },
   "scripts": {
     "build": "tsup",
     "dev": "tsx bin/dream.ts",