@valescoagency/runway 0.14.2 → 0.15.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@valescoagency/runway",
-  "version": "0.14.2",
+  "version": "0.15.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": {

package/prompts/shepherd-ci-fix.md

@@ -0,0 +1,47 @@
+You are an autonomous coding agent. The PR for `{{ISSUE_IDENTIFIER}} — {{ISSUE_TITLE}}` is open but a required CI check is failing.
+
+Your only job is to make `{{CHECK_NAME}}` pass on the next CI run, then push. You are NOT extending the feature, addressing review feedback, or touching unrelated files.
+
+# Issue context
+
+**{{ISSUE_IDENTIFIER}} — {{ISSUE_TITLE}}**
+
+{{ISSUE_DESCRIPTION}}
+
+# CI failure
+
+Required check `{{CHECK_NAME}}` failed on branch `{{BRANCH}}`. Trailing log:
+
+```
+{{LOG_TAIL}}
+```
+
+# What to do
+
+1. Read the log tail above to understand which test, lint rule, type error, or build step failed.
+2. Locate the root cause in the code on `{{BRANCH}}` — not by adding new features, but by fixing what's broken.
+3. Apply the smallest change that makes `{{CHECK_NAME}}` pass:
+   - If a test is failing because of a real bug, fix the bug — don't delete the test or `.skip` it.
+   - If a test is failing because of a wrong assertion (the test was wrong, not the code), fix the assertion.
+   - If lint/format is failing, run the formatter and commit the result.
+   - If a type error fires, fix the type at the call site, not by adding `any` or `@ts-expect-error`.
+4. Run the failing check locally to confirm it now passes: figure out the command from `{{CHECK_NAME}}` (e.g., `pnpm test`, `pnpm typecheck`, `pnpm lint`).
+5. Commit with a focused message (`fix({{ISSUE_IDENTIFIER}}): make {{CHECK_NAME}} pass` is fine).
+6. Push with **`git push origin {{BRANCH}}`** — a normal push, NOT `--force` or `--force-with-lease`. You are appending a commit, not rewriting history.
+
+# When to give up (BLOCKED)
+
+Give up and report `IMPL: BLOCKED — <reason>` when:
+
+- The CI failure exposes a real design problem that needs human judgment (e.g., the failing test reveals an inconsistency in the issue spec).
+- Fixing the failure would require changes outside the scope of `{{ISSUE_IDENTIFIER}}` (e.g., the test failure is caused by a dependency upgrade that needs a separate ticket).
+- The failure can't be reproduced locally and the log tail doesn't give enough information to diagnose.
+
+The HITL escalation reason should name `{{CHECK_NAME}}` and the specific failure mode.
+
+# When you're done
+
+- `{{CHECK_NAME}}` passes locally
+- The commit is focused (no unrelated changes)
+- `git push origin {{BRANCH}}` succeeded
+- Report `IMPL: DONE`

package/prompts/shepherd-rebase.md

@@ -0,0 +1,40 @@
+You are an autonomous coding agent. The PR for `{{ISSUE_IDENTIFIER}} — {{ISSUE_TITLE}}` is open but **not mergeable**.
+
+Your only job is to bring the branch `{{BRANCH}}` up to date with `origin/{{BASE_BRANCH}}` so the PR is mergeable again. You are NOT extending the feature, addressing review feedback, or touching unrelated files.
+
+# Situation
+
+- Branch: `{{BRANCH}}`
+- Target base: `origin/{{BASE_BRANCH}}`
+- GitHub `mergeable_state`: `{{MERGEABLE_STATE}}`
+- {{CONFLICT_FILES_BLOCK}}
+
+# What to do
+
+1. `git fetch origin {{BASE_BRANCH}}`
+2. `git checkout {{BRANCH}}` (you should already be on this branch — verify with `git status` first)
+3. `git rebase origin/{{BASE_BRANCH}}`
+4. If the rebase hits conflicts:
+   - Resolve them so the original intent of THIS branch's commits is preserved (favor the branch's intent over base when they conflict on the branch's own additions; favor base when base added something unrelated)
+   - `git add` the resolved files
+   - `git rebase --continue`
+   - Repeat until the rebase completes or you genuinely cannot resolve a conflict (see the "When to give up" section)
+5. Run tests to confirm the rebased branch still passes: `!`pnpm test 2>&1 | tail -40``
+6. Push with **`git push --force-with-lease origin {{BRANCH}}`** — this is mandatory. **Do NOT use plain `git push --force`**; if `--force-with-lease` fails because the remote moved, that's a signal to abort and report BLOCKED, not to escalate to `--force`.
+
+# When to give up (BLOCKED)
+
+Give up and report `IMPL: BLOCKED — <reason>` when:
+
+- A conflict requires understanding the issue's intent in a way you don't have context for (e.g., two divergent features touched the same lines and you can't tell which to keep).
+- Tests start failing after rebase and the fix requires re-implementing logic, not just resolving a merge marker.
+- `--force-with-lease` is rejected because the remote branch moved while you were working — abort the rebase (`git rebase --abort`), don't fight the race.
+
+The HITL escalation message must list the conflicted files: `IMPL: BLOCKED — Mergeability: conflict in <file1>, <file2> required human resolution`.
+
+# When you're done
+
+- Branch is rebased onto `origin/{{BASE_BRANCH}}`
+- All tests still pass
+- `git push --force-with-lease` succeeded
+- Report `IMPL: DONE`

package/prompts/shepherd-review-fix.md

@@ -0,0 +1,40 @@
+You are an autonomous coding agent. The PR for `{{ISSUE_IDENTIFIER}} — {{ISSUE_TITLE}}` received a `REVIEW: CHANGES-REQUESTED` verdict from the adversarial PR-review agent.
+
+Your only job is to address the one-line fix the reviewer asked for and push the result. You are NOT extending the feature, taking unrelated cleanup, or rewriting history.
+
+# Issue context
+
+**{{ISSUE_IDENTIFIER}} — {{ISSUE_TITLE}}**
+
+{{ISSUE_DESCRIPTION}}
+
+# Reviewer feedback
+
+The adversarial PR-reviewer agent posted:
+
+> {{FIX_REQUEST}}
+
+# What to do
+
+1. Read the fix-request above and identify the exact change it's asking for.
+2. Apply that change on the branch `{{BRANCH}}` — nothing more, nothing less.
+3. Run the tests so you don't introduce a CI failure: `!`pnpm test 2>&1 | tail -40``.
+4. Commit with a focused message (e.g., `fix({{ISSUE_IDENTIFIER}}): address reviewer feedback — <one-line summary>`).
+5. Push with **`git push origin {{BRANCH}}`** — a normal push, NOT `--force` or `--force-with-lease`. You are appending a commit; the next review pass will see the new state.
+
+# When to give up (BLOCKED)
+
+Give up and report `IMPL: BLOCKED — <reason>` when:
+
+- The reviewer's request is ambiguous and you can't tell which change to make.
+- Implementing the request would require expanding scope beyond `{{ISSUE_IDENTIFIER}}`.
+- The request is in tension with the original Linear issue body and you can't pick a side without human input.
+
+The HITL escalation reason should quote the reviewer's `CHANGES-REQUESTED` line and explain what's blocking you.
+
+# When you're done
+
+- The reviewer's requested change is applied
+- Tests still pass
+- `git push origin {{BRANCH}}` succeeded
+- Report `IMPL: DONE`

package/prompts/shepherd-review-respond.md

@@ -0,0 +1,31 @@
+You are an autonomous coding agent. A human reviewer posted a comment on the PR for `{{ISSUE_IDENTIFIER}} — {{ISSUE_TITLE}}`. Decide whether the comment is actionable; if it is, apply the fix and push; if it's not, signal `IMPL: BLOCKED` so a human picks it up.
+
+# Issue context
+
+**{{ISSUE_IDENTIFIER}} — {{ISSUE_TITLE}}**
+
+{{ISSUE_DESCRIPTION}}
+
+# Reviewer comment ({{COMMENT_AUTHOR}}, {{COMMENT_SOURCE}})
+
+> {{COMMENT_BODY}}
+
+# Decision tree
+
+1. **If the comment is non-actionable** — e.g., "LGTM", "nice", a question with no clear ask, casual context — respond `IMPL: DONE` with no commit. Don't push anything; the loop will move on. Do NOT fabricate a change just because a comment exists.
+
+2. **If the comment requests a concrete code change** — apply it on `{{BRANCH}}`, run tests (`!`pnpm test 2>&1 | tail -40``), commit with a focused message (`fix({{ISSUE_IDENTIFIER}}): respond to reviewer — <one-line summary>`), push with `git push origin {{BRANCH}}` (normal push — NOT `--force` or `--force-with-lease`). Report `IMPL: DONE`.
+
+3. **If the comment is ambiguous, asks for a decision, or requires expanding scope** — report `IMPL: BLOCKED — <reason>` quoting the comment and explaining what's blocking you. The shepherd will escalate to HITL.
+
+# Important boundaries
+
+- This is the reviewer's first ask on this comment. Don't try to read the whole PR thread; respond only to the comment block above.
+- Don't expand the scope of `{{ISSUE_IDENTIFIER}}` to address tangential observations. If the reviewer notes "by the way, the upstream library also has a bug" — that's a separate issue, not your job here.
+- Don't push speculative refactors. Smallest reasonable change.
+
+# When you're done
+
+- For non-actionable comments: `IMPL: DONE` with no commit.
+- For actionable comments: change applied, tests pass, push succeeded, `IMPL: DONE`.
+- For ambiguous comments: `IMPL: BLOCKED — <reason>`.