@valescoagency/runway 0.8.1 → 0.9.0

package/README.md

@@ -156,7 +156,7 @@ sandcastle reads `.sandcastle/.env` per its docs.
 ## Install
 
 ```bash
-pnpm install -g @valescoagency/runway       # or npm i -g, yarn global add
+pnpm add -g @valescoagency/runway           # or npm i -g, yarn global add
 ```
 
 Export runway's own env (in your shell rc, or wherever you keep API keys):
@@ -392,7 +392,7 @@ These are tractable, just not v1.
 
 ## Status
 
-0.8.1 — production-shaped and dogfooded against live Linear queues.
+0.9.0 — production-shaped and dogfooded against live Linear queues.
 The end-to-end pipeline (init → run → review → PR) is stable; surface
 may still shift as the orchestrator's policy and iteration mechanics
 mature. See [CHANGELOG.md](./CHANGELOG.md) for per-release detail.

package/dist/implement.js

@@ -60,6 +60,10 @@ export const runImplementLoop = (issue, deps, branch) => Effect.gen(function* ()
             // and iteration N+1, since the implementer keeps drifting
             // toward the same code paths until corrected.
             priorReviewFeedback: priorFeedback,
+            // VA-417: pass the actual base branch so the prompt
+            // renders the real name (`main`, `master`, etc.) rather
+            // than a hardcoded default.
+            baseBranch,
         }));
         const sandcastleRunId = `impl-${issue.identifier}-iter-${iter}`;
         // VA-389: parse the verdict inside the span scope so the

package/dist/prompts.js

@@ -56,6 +56,10 @@ function implementVars(args) {
         PREVIOUS_ITERATIONS: args.previousIterations,
         PRIOR_REVIEW_FEEDBACK: args.priorReviewFeedback,
         POLICY_FORBIDDEN_BULLET: renderForbiddenPathsBullet(args.policy),
+        // VA-417: fall back to "main" if the caller didn't pass one, so
+        // older test fixtures keep working. Production always passes the
+        // resolved base branch from config / orchestrator detection.
+        BASE_BRANCH: args.baseBranch ?? "main",
     };
 }
 function reviewVars(args) {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@valescoagency/runway",
-  "version": "0.8.1",
+  "version": "0.9.0",
   "description": "Linear-driven orchestrator + scaffolder for coding agents on Sandcastle. `runway init` scaffolds a target repo (sandcastle + varlock + 1Password); `runway run` drains a Linear queue against it; `runway doctor`, `runway upgrade`, `runway upgrade-repo` round out the lifecycle.",
   "license": "MIT",
   "author": {
@@ -63,7 +63,7 @@
     "vitest": "^4.1.6"
   },
   "engines": {
-    "node": ">=22"
+    "node": ">=24"
   },
   "publishConfig": {
     "access": "public"

package/prompts/implement.md

@@ -12,8 +12,15 @@ You are an autonomous coding agent working on a single Linear issue.
 
 # Repository context
 
-You are operating inside a clean checkout of the target repository on a
-fresh branch named `agent/{{ISSUE_IDENTIFIER}}`. Branch off `main`.
+You are operating on the branch `agent/{{ISSUE_IDENTIFIER}}` based off
+`{{BASE_BRANCH}}` (this repo's default branch — usually `main` or
+`master`). The branch is clean on a first attempt. **On a retry it
+may already carry commits from a prior attempt that review rejected**
+— the rejection reasons then appear in the *Review feedback from
+prior attempts* section above. Your job is to produce a final state
+that addresses every blocker in that feedback, replacing the existing
+commits if they would re-introduce a rejected design. Do not treat
+pre-existing commits as authoritative.
 
 # What done looks like
 

package/templates/Dockerfile.claude-code.base

@@ -9,7 +9,7 @@
 # patches AFTER this base, so adopters re-run `runway init --force`
 # to roll forward.
 
-FROM node:22-bookworm
+FROM node:24-bookworm
 
 # Install system dependencies
 RUN apt-get update && apt-get install -y \
@@ -48,12 +48,12 @@ RUN if ! getent group $AGENT_GID >/dev/null; then \
 ENV HOME=/home/agent
 ENV XDG_CACHE_HOME=/home/agent/.cache
 ENV TURBO_CACHE_DIR=/tmp/turbo-cache
-ENV npm_config_cache=/home/agent/.cache/npm
+ENV pnpm_config_cache=/home/agent/.cache/pnpm
 
 # Pre-create cache dirs with agent ownership so the first pnpm/turbo
 # run doesn't have to chown them. Both are inside paths the agent owns
 # anyway; this just makes them exist.
-RUN mkdir -p /home/agent/.cache /home/agent/.cache/npm /tmp/turbo-cache \
+RUN mkdir -p /home/agent/.cache /home/agent/.cache/pnpm /tmp/turbo-cache \
  && chown -R $AGENT_UID:$AGENT_GID /home/agent/.cache /tmp/turbo-cache
 
 # Bake pnpm via corepack at build time so `pnpm` is on PATH inside the
@@ -61,7 +61,7 @@ RUN mkdir -p /home/agent/.cache /home/agent/.cache/npm /tmp/turbo-cache \
 # can override at runtime via `packageManager` in package.json +
 # `corepack use`.
 RUN corepack enable \
- && corepack prepare pnpm@10.0.0 --activate
+ && corepack prepare pnpm@11.1.1 --activate
 
 USER ${AGENT_UID}:${AGENT_GID}
 

package/templates/dockerfile-varlock.snippet

@@ -4,7 +4,7 @@
 
 # Install varlock via npm. The official `ghcr.io/dmno-dev/varlock`
 # image is musl/Alpine — copying its binary into a glibc base
-# (node:22-bookworm) produces an ELF that the loader can't resolve
+# (node:24-bookworm) produces an ELF that the loader can't resolve
 # ("not found" on exec). npm install gets the right binary for the
 # image's libc.
 USER root