Skip to content

Worktrunk is a CLI for Git worktree management, designed for parallel AI agent workflows

chore: update tend workflows (0.2.0 → 0.2.5) (#4057)

Worktrunk Botc308b204cfac
diff --git a/.claude/skills/running-tend/SKILL.md b/.claude/skills/running-tend/SKILL.md
index 604273e37..03dccc51e 100644
--- a/.claude/skills/running-tend/SKILL.md
+++ b/.claude/skills/running-tend/SKILL.md
@@ -74,7 +74,12 @@ CI runs on Linux, Windows, and macOS.
## Session Log Paths
-Artifact paths: `-home-runner-work-worktrunk-worktrunk/<session-id>.jsonl`
+The artifact directory is named after the agent's working directory, and from
+tend 0.2.5 that is a per-run `/tmp/tend-agent-workspace-*/checkout` — so the
+old `-home-runner-work-worktrunk-worktrunk/` prefix appears only in runs
+predating the bump, and there is no literal to match on any more. Use the
+bundled `find "$DEST" -name '*.jsonl'` recipe; either shape is one
+`<session-id>.jsonl` under a single slugified directory.
## Labels
@@ -290,6 +295,14 @@ succeed. A failure is reported in the PR, never worked around: leave the file
alone if the update fails, `git checkout flake.lock` if the eval does, and
hand-compute an entry in neither case.
+**Expect both commands to fail with a permission error from tend 0.2.5 on.**
+`nix` resolves on the agent's PATH, but the multi-user client reaches the store
+by connecting to `/nix/var/nix/daemon-socket/socket`, and the sandbox blocks
+`socket(AF_UNIX, …)` outright. That is the reported failure above, not a
+problem with the bump: say so in the PR, leave `flake.lock` untouched, and
+carry the rest of the toolchain change as normal. It clears when
+max-sixty/tend#1197 gives the action a lever for it.
+
After bumping, run the full test suite (`cargo run -- hook pre-merge --yes`)
and verify `cargo msrv verify` passes.
@@ -338,12 +351,11 @@ jq -n --arg cwd "$PWD" '{
context_window: {used_percentage: 42.0}
}' > /tmp/statusline-input.json
-# Debug build on purpose. `tend-weekly` installs no `wt`, and its rust-cache
-# step is `save-if: false` under a key no workflow writes, so `--release`
-# means a cold optimized build of the whole dependency graph before the first
-# render. The duplicate `(command, context)` pairs this check reads are
-# profile-independent; only the timing columns, which this section doesn't
-# triage, would be worth a release build.
+# Debug build on purpose. `tend-weekly` installs no `wt` and restores no Rust
+# cache, so `--release` means a cold optimized build of the whole dependency
+# graph before the first render. The duplicate `(command, context)` pairs this
+# check reads are profile-independent; only the timing columns, which this
+# section doesn't triage, would be worth a release build.
cargo run -- -vv list statusline --format=claude-code \
< /tmp/statusline-input.json > /dev/null
cargo run -- config state logs profile --format=json | jq .cache
diff --git a/.claude/skills/running-tend/references/nightly-cleaner.md b/.claude/skills/running-tend/references/nightly-cleaner.md
index d14dffe8f..a31e78128 100644
--- a/.claude/skills/running-tend/references/nightly-cleaner.md
+++ b/.claude/skills/running-tend/references/nightly-cleaner.md
@@ -12,4 +12,4 @@ For each `.rs` file in the survey, also check:
## Repo-Wide CI Breakage
-A failure that reproduces identically on `main` and every PR (a broken system-package install in `code-coverage`, say) belongs to `tend-ci-fix`, which fires on any watched-workflow `failure` on `main` — the list lives in `.config/tend.yaml` under `ci-fix.watched_workflows`; a non-required job failing is enough to trigger it. It does not fire on runs that end `cancelled`, so record the breakage in the summary rather than assuming the handoff lands.
+A failure that reproduces identically on `main` and every PR (a broken system-package install in `code-coverage`, say) belongs to `tend-ci-fix`, which fires on any watched-workflow `failure` on `main` — the list lives in `.config/tend.yaml` under `ci-fix.watched_workflows`; a non-required job failing is enough to trigger it. It fires on `cancelled` too, and its prompt carries `Conclusion:` so the session can tell the two apart — but a cancellation is usually a queue or timeout artifact rather than a defect, so record the breakage in the summary rather than assuming the handoff produces a fix.
diff --git a/.config/tend.yaml b/.config/tend.yaml
index b9f94a683..04e473953 100644
--- a/.config/tend.yaml
+++ b/.config/tend.yaml
@@ -2,18 +2,17 @@ bot_name: worktrunk-bot
setup:
- uses: ./.github/actions/tend-setup
# `setup:` runs as `runner`, so what it installs into the runner's home never
-# reaches the agent (see "Sandbox toolchain" in .github/CLAUDE.md). These run as
-# the sandbox user once its PATH is built, with ~/.local/bin already first on it:
-# pre-commit installs into the sandbox's own home so uv's shim shebang resolves
-# there, and the cargo binaries are copied from where `tend-setup` already built
-# them, at the versions pinned there. `nu` and `nix` take the system-location
-# route instead and need no line. The probe asserts all five: sandbox-setup
-# runs the block under `bash -eo pipefail`, so a tool that goes missing fails
-# the job and files a tend-outage issue naming it.
+# reaches the agent — and from tend 0.2.5 the sandbox denies reads there
+# outright, so a line copying a binary out of it fails the whole lifecycle
+# before the harness starts (see "Sandbox toolchain" in .github/CLAUDE.md).
+# Only pre-commit is left: it installs into the sandbox's own home, where uv's
+# shim shebang resolves, and needs no runner-owned file to do it. `cargo-insta`,
+# `cargo-nextest`, `nu` and `nix` all take the system-location route in
+# `tend-setup` instead and need no line here. The probe still asserts all five:
+# sandbox-setup runs the block under `bash -eo pipefail`, so a tool that goes
+# missing fails the job and files a tend-outage issue naming it.
sandbox_setup:
- mkdir -p ~/.local/bin
-- install -m755 /home/runner/.cargo-install/cargo-insta/bin/cargo-insta ~/.local/bin/
-- install -m755 /home/runner/.cargo-install/cargo-nextest/bin/cargo-nextest ~/.local/bin/
- uv tool install --quiet pre-commit
- 'for t in cargo-insta cargo-nextest pre-commit nu nix; do command -v "$t" >/dev/null || { echo "::error::tend sandbox is missing $t; see Sandbox toolchain in .github/CLAUDE.md"; exit 1; }; done'
secrets:
diff --git a/.github/CLAUDE.md b/.github/CLAUDE.md
index 9871afcee..dd1a6d4a5 100644
--- a/.github/CLAUDE.md
+++ b/.github/CLAUDE.md
@@ -86,12 +86,26 @@ rewriting a leading `/home/runner` to `/home/tend-sandbox` and keeping an entry
only where the rewritten directory exists and the sandbox UID can traverse it.
`useradd -m` seeds the sandbox home from `/etc/skel`, so an image-baked
toolchain has a sibling there and survives; anything `tend-setup` installs at
-runtime into the runner's home has none and is dropped, unlogged. So a tool the
-agent needs has to land in a system location (`/opt/hostedtoolcache/...`,
-`/nix/var/nix/profiles/default/bin`), which carries across verbatim — the route
-`nu` and `nix` take — or be copied in by `.config/tend.yaml`'s `sandbox_setup:`,
-which is what the pre-merge gate's `cargo-insta`, `cargo-nextest` and
-`pre-commit` take. Its closing probe asserts every tool on both routes.
+runtime into the runner's home has none and is dropped, unlogged. From tend
+0.2.5 the runner's home isn't merely off-PATH but unreadable: the Sandbox
+Runtime denies reads across it and the runner's checkout, so a `sandbox_setup:`
+line that copies a binary out of `/home/runner` fails the whole lifecycle
+before the harness starts.
+
+So a tool the agent needs has to land in a system location, which carries
+across verbatim: `/opt/hostedtoolcache/...` for `nu`,
+`/nix/var/nix/profiles/default/bin` for `nix`, and `/usr/local/bin` for
+`cargo-insta` and `cargo-nextest`, which `tend-setup` `sudo install`s there
+after building them in the runner's home. Only `pre-commit` still comes from
+`.config/tend.yaml`'s `sandbox_setup:`, because it installs into the sandbox's
+own home and reads nothing runner-owned to do it. The block's closing probe
+asserts every tool on both routes.
+
+A system location gets the *binary* across, not what it talks to. `nix`
+resolves on the agent's PATH but cannot reach the daemon: the sandbox blocks
+`socket(AF_UNIX, …)`, so the weekly `flake.lock` refresh needs an upstream
+lever (max-sixty/tend#1197). `command -v` can't see that distinction, which is
+why the probe stays green while the weekly job would not.
## Build environment
@@ -102,6 +116,13 @@ different keys and miss each other's caches.
It hashes the vars **visible at its own step**, so a var exported by a later
step is invisible and a var the writers don't set poisons the key. ci.yaml and
nightly.yaml carry theirs in a workflow-level `env:` block, always in place
-first; the generated `tend-*.yaml` files can't, so `tend-setup` sets the same
-three vars in a step above its cache step. A miss is silent — the step
-succeeds having restored nothing — so drift here shows up only as slow jobs.
+first. A miss is silent — the step succeeds having restored nothing — so drift
+here shows up only as slow jobs.
+
+The `tend-*.yaml` workflows are out of this scheme entirely. They can't carry a
+workflow-level `env:` block, and from tend 0.2.5 there is nothing for one to
+serve: the agent builds in a disposable `/tmp` clone, so a cache restored into
+the runner's checkout and home is both unreachable and at the wrong path.
+`tend-setup` therefore restores nothing and sets none of the three vars, and
+tend sessions compile cold until max-sixty/tend#1198 gives the agent's own tree
+a supported way to warm.
diff --git a/.github/actions/tend-setup/action.yaml b/.github/actions/tend-setup/action.yaml
index 84c0e0556..5e6134744 100644
--- a/.github/actions/tend-setup/action.yaml
+++ b/.github/actions/tend-setup/action.yaml
@@ -1,5 +1,5 @@
name: tend setup
-description: Install cargo tools, Rust cache, and test shells for the tend workflows
+description: Install cargo tools, test shells, and Nix for the tend workflows
inputs:
install-cargo-tools:
@@ -12,22 +12,24 @@ inputs:
runs:
using: composite
steps:
- # Above the cache step on purpose: rust-cache hashes the CARGO*/RUST* vars
- # visible at its own step into the key, so these have to be set first, and
- # have to match what ci.yaml's workflow `env:` block gives the jobs that
- # write the shared cache (see "Build environment" in .github/CLAUDE.md).
- - name: Set build environment
- shell: bash
- run: |
- echo "CARGO_TERM_COLOR=always" >> "$GITHUB_ENV"
- echo "CARGO_INCREMENTAL=0" >> "$GITHUB_ENV"
- echo "RUSTFLAGS=-C debuginfo=0" >> "$GITHUB_ENV"
+ # No rust-cache step here, and so no CARGO*/RUST* env block above one to
+ # match its key. From tend 0.2.5 the agent works in a disposable /tmp clone
+ # instead of the runner's checkout, and the sandbox denies reads under the
+ # runner's home, so a restored `~/.cargo` and `<runner checkout>/target`
+ # are both unreachable and at the wrong path — the restore warmed nothing
+ # and cost the download in all eight workflows. Tend sessions build cold
+ # until there is a supported way to warm the agent's own tree
+ # (max-sixty/tend#1198). Restoring here again needs that to land first.
- # `.config/tend.yaml`'s `sandbox_setup:` copies both binaries out of
- # `$HOME/.cargo-install/<crate>/bin` — the root this action hardcodes — so
- # the sandboxed agent can reach them (it can't see the runner's home on its
- # PATH). Swapping this action for one with a different layout, or dropping
- # these steps, breaks every tend workflow at that copy; update both sides.
+ # The cargo tools reach the agent through `/usr/local/bin`, not through the
+ # runner's home: these `cargo-install` steps write
+ # `$HOME/.cargo-install/<crate>/bin` — the root this action hardcodes — and
+ # the sandbox denies that whole subtree, so `.config/tend.yaml` can no
+ # longer copy them across from `sandbox_setup:`. A system location crosses
+ # verbatim instead, the route `nu` and `nix` already take (see "Sandbox
+ # toolchain" in .github/CLAUDE.md). Swapping these steps for an action with
+ # a different layout, or dropping the publish step below, breaks every tend
+ # workflow at `.config/tend.yaml`'s probe; update both sides.
- name: Install cargo-insta
if: inputs.install-cargo-tools == 'true'
uses: baptiste0928/cargo-install@v3
@@ -42,18 +44,15 @@ runs:
crate: cargo-nextest
version: "=0.9.143"
- - name: "\U0001F4B0 Cache"
- uses: Swatinem/rust-cache@v2
- with:
- # Restore the shared cache `test-setup`'s jobs publish from main; never
- # save (tend jobs would deposit single-use entries against the 10 GB
- # repo cap). Each field has to match what those jobs compute or the
- # restore silently misses, as the old `hashFiles('Cargo.lock')` prefix
- # and job-name shared-key did.
- cache-bin: false
- prefix-key: v1-rust
- shared-key: shared
- save-if: false
+ - name: Publish the cargo tools to a system location
+ if: inputs.install-cargo-tools == 'true'
+ shell: bash
+ # `sudo` is what makes this a runner-side step: the agent has none, which
+ # is why it cannot do this hand-off for itself.
+ run: |
+ for crate in cargo-insta cargo-nextest; do
+ sudo install -m755 "$HOME/.cargo-install/$crate/bin/$crate" /usr/local/bin/
+ done
- name: Install uv
uses: astral-sh/[email protected]
@@ -108,8 +107,17 @@ runs:
# The multi-user daemon install is what carries it across, so the ~1 s
# `nixbuild/nix-quick-install-action` is no substitute: it hands /nix to
# the runner and puts only $HOME/.nix-profile/bin on $GITHUB_PATH, which
- # the /home/runner rewrite drops. Here root owns /nix and the sandbox user
- # reaches the store through the daemon.
+ # the /home/runner rewrite drops. Here root owns /nix and the store is
+ # reached through the daemon.
+ #
+ # Reaching the daemon is what the agent can no longer do. From tend 0.2.5
+ # the sandbox blocks `socket(AF_UNIX, …)` outright, so connecting to
+ # /nix/var/nix/daemon-socket/socket fails with EPERM and the weekly job's
+ # `nix flake update` cannot run — it needs an upstream lever
+ # (max-sixty/tend#1197). `command -v nix` still resolves, so the probe
+ # below stays green and the gap surfaces only in that one job. The install
+ # stays because it is the half of the route this repo owns, and because
+ # `nix` still works for anything running as `runner`.
#
# Caching doesn't apply. Of the 4 s, the binary tarball is about half; the
# rest creates the nixbld users, /etc/nix and the daemon unit, which no
diff --git a/.github/workflows/tend-ci-fix.yaml b/.github/workflows/tend-ci-fix.yaml
index 5fba0ce35..61c77fc61 100644
--- a/.github/workflows/tend-ci-fix.yaml
+++ b/.github/workflows/tend-ci-fix.yaml
@@ -1,4 +1,4 @@
-# Generated by tend 0.2.0. Regenerate with: uvx tend@latest init
+# Generated by tend 0.2.5. Regenerate with: uvx tend@latest init
#
# Do not edit this file directly — it will be overwritten on regeneration.
# To customize behavior, edit the relevant skill (for example,
@@ -15,7 +15,7 @@ on:
jobs:
fix-ci:
- if: github.repository_owner == 'max-sixty' && github.event.workflow_run.conclusion == 'failure'
+ if: github.repository_owner == 'max-sixty' && contains(fromJSON('["failure", "cancelled"]'), github.event.workflow_run.conclusion)
concurrency:
# A red branch fails every push that follows, each on its own commit, so
# one session per branch — not per commit — is what collapses the burst.
@@ -112,7 +112,7 @@ jobs:
- uses: ./.github/actions/tend-setup
if: steps.tend_enabled.outputs.enabled == 'true'
- - uses: max-sixty/tend/[email protected]
+ - uses: max-sixty/tend/[email protected]
if: steps.tend_enabled.outputs.enabled == 'true'
with:
github_token: ${{ secrets.TEND_BOT_TOKEN }}
@@ -120,14 +120,15 @@ jobs:
anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}
bot_name: worktrunk-bot
model: opus
+ checkout_mode: base
+ base_branch: ${{ github.event.repository.default_branch }}
sandbox_setup: |2
mkdir -p ~/.local/bin
- install -m755 /home/runner/.cargo-install/cargo-insta/bin/cargo-insta ~/.local/bin/
- install -m755 /home/runner/.cargo-install/cargo-nextest/bin/cargo-nextest ~/.local/bin/
uv tool install --quiet pre-commit
for t in cargo-insta cargo-nextest pre-commit nu nix; do command -v "$t" >/dev/null || { echo "::error::tend sandbox is missing $t; see Sandbox toolchain in .github/CLAUDE.md"; exit 1; }; done
prompt: |2
/tend-ci-runner:ci-fix ${{ github.event.workflow_run.id }}
- Run URL: ${{ github.event.workflow_run.html_url }}
+ - Conclusion: ${{ github.event.workflow_run.conclusion }}
- Commit: ${{ github.event.workflow_run.head_sha }}
- Commit message: ${{ github.event.workflow_run.head_commit.message }}
diff --git a/.github/workflows/tend-mention.yaml b/.github/workflows/tend-mention.yaml
index 3fe2b066e..6cbdab26e 100644
--- a/.github/workflows/tend-mention.yaml
+++ b/.github/workflows/tend-mention.yaml
@@ -1,4 +1,4 @@
-# Generated by tend 0.2.0. Regenerate with: uvx tend@latest init
+# Generated by tend 0.2.5. Regenerate with: uvx tend@latest init
#
# Do not edit this file directly — it will be overwritten on regeneration.
# To customize behavior, edit the relevant skill (for example,
@@ -576,22 +576,6 @@ jobs:
- uses: ./.github/actions/tend-setup
if: steps.tend_enabled.outputs.enabled == 'true'
- - name: Check out PR branch
- if: |
- steps.tend_enabled.outputs.enabled == 'true' &&
- ((github.event_name == 'issue_comment' && github.event.issue.pull_request.url != '') ||
- github.event_name == 'repository_dispatch')
- run: |
- PR_STATE=$(gh pr view "$PR_NUMBER" --json state --jq '.state')
- if [ "$PR_STATE" = "OPEN" ]; then
- gh pr checkout "$PR_NUMBER"
- else
- echo "::warning::PR is $PR_STATE — staying on default branch"
- fi
- env:
- GITHUB_TOKEN: ${{ secrets.TEND_BOT_TOKEN }}
- PR_NUMBER: ${{ github.event_name == 'issue_comment' && github.event.issue.number || github.event.client_payload.pr }}
-
- name: Compute queue delay
id: delay
if: steps.tend_enabled.outputs.enabled == 'true'
@@ -607,7 +591,7 @@ jobs:
# the API record — the dispatch payload never carries one to spoof.
EVENT_TS: ${{ github.event.comment.updated_at || needs.verify.outputs.ts || github.event.issue.updated_at }}
- - uses: max-sixty/tend/[email protected]
+ - uses: max-sixty/tend/[email protected]
if: steps.tend_enabled.outputs.enabled == 'true'
with:
github_token: ${{ secrets.TEND_BOT_TOKEN }}
@@ -615,10 +599,10 @@ jobs:
anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}
bot_name: worktrunk-bot
model: opus
+ checkout_mode: mention
+ base_branch: ${{ github.event.repository.default_branch }}
sandbox_setup: |2
mkdir -p ~/.local/bin
- install -m755 /home/runner/.cargo-install/cargo-insta/bin/cargo-insta ~/.local/bin/
- install -m755 /home/runner/.cargo-install/cargo-nextest/bin/cargo-nextest ~/.local/bin/
uv tool install --quiet pre-commit
for t in cargo-insta cargo-nextest pre-commit nu nix; do command -v "$t" >/dev/null || { echo "::error::tend sandbox is missing $t; see Sandbox toolchain in .github/CLAUDE.md"; exit 1; }; done
prompt: >-
@@ -643,15 +627,6 @@ jobs:
|| format('A user commented on an issue/PR where you previously participated ({0}). Read the full context. Only respond if the comment is directed at you, asks a question you can help with, or requests changes you can make. If the conversation is between other participants, exit silently.', github.event.comment.html_url)
}}
- - name: Restore local setup actions for POST cleanup
- if: |
- always()
- && (steps.tend_enabled.outputs.enabled == 'true')
- run: |
- dir=.github/actions/tend-setup
- git checkout "$GITHUB_SHA" -- "$dir" ||
- echo "::warning::could not restore $dir from $GITHUB_SHA; POST cleanup of the local action may fail"
-
- name: Remove the eyes reaction
if: |
always()
diff --git a/.github/workflows/tend-nightly.yaml b/.github/workflows/tend-nightly.yaml
index bdaab1cbf..d6bf5ab71 100644
--- a/.github/workflows/tend-nightly.yaml
+++ b/.github/workflows/tend-nightly.yaml
@@ -1,4 +1,4 @@
-# Generated by tend 0.2.0. Regenerate with: uvx tend@latest init
+# Generated by tend 0.2.5. Regenerate with: uvx tend@latest init
#
# Do not edit this file directly — it will be overwritten on regeneration.
# To customize behavior, edit the relevant skill (for example,
@@ -103,7 +103,7 @@ jobs:
- uses: ./.github/actions/tend-setup
if: steps.tend_enabled.outputs.enabled == 'true'
- - uses: max-sixty/tend/[email protected]
+ - uses: max-sixty/tend/[email protected]
if: steps.tend_enabled.outputs.enabled == 'true'
with:
github_token: ${{ secrets.TEND_BOT_TOKEN }}
@@ -111,10 +111,10 @@ jobs:
anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}
bot_name: worktrunk-bot
model: opus
+ checkout_mode: base
+ base_branch: ${{ github.event.repository.default_branch }}
sandbox_setup: |2
mkdir -p ~/.local/bin
- install -m755 /home/runner/.cargo-install/cargo-insta/bin/cargo-insta ~/.local/bin/
- install -m755 /home/runner/.cargo-install/cargo-nextest/bin/cargo-nextest ~/.local/bin/
uv tool install --quiet pre-commit
for t in cargo-insta cargo-nextest pre-commit nu nix; do command -v "$t" >/dev/null || { echo "::error::tend sandbox is missing $t; see Sandbox toolchain in .github/CLAUDE.md"; exit 1; }; done
prompt: |2
diff --git a/.github/workflows/tend-notifications.yaml b/.github/workflows/tend-notifications.yaml
index c3ef633fe..457f9aa2e 100644
--- a/.github/workflows/tend-notifications.yaml
+++ b/.github/workflows/tend-notifications.yaml
@@ -1,4 +1,4 @@
-# Generated by tend 0.2.0. Regenerate with: uvx tend@latest init
+# Generated by tend 0.2.5. Regenerate with: uvx tend@latest init
#
# Do not edit this file directly — it will be overwritten on regeneration.
# To customize behavior, edit the relevant skill (for example,
@@ -298,7 +298,7 @@ jobs:
- uses: ./.github/actions/tend-setup
if: (steps.tend_enabled.outputs.enabled == 'true') && (steps.check.outputs.count != '0' || steps.check.outputs.conflict_count != '0' || github.event_name == 'workflow_dispatch')
- - uses: max-sixty/tend/[email protected]
+ - uses: max-sixty/tend/[email protected]
if: (steps.tend_enabled.outputs.enabled == 'true') && (steps.check.outputs.count != '0' || steps.check.outputs.conflict_count != '0' || github.event_name == 'workflow_dispatch')
with:
github_token: ${{ secrets.TEND_BOT_TOKEN }}
@@ -306,10 +306,10 @@ jobs:
anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}
bot_name: worktrunk-bot
model: opus
+ checkout_mode: base
+ base_branch: ${{ github.event.repository.default_branch }}
sandbox_setup: |2
mkdir -p ~/.local/bin
- install -m755 /home/runner/.cargo-install/cargo-insta/bin/cargo-insta ~/.local/bin/
- install -m755 /home/runner/.cargo-install/cargo-nextest/bin/cargo-nextest ~/.local/bin/
uv tool install --quiet pre-commit
for t in cargo-insta cargo-nextest pre-commit nu nix; do command -v "$t" >/dev/null || { echo "::error::tend sandbox is missing $t; see Sandbox toolchain in .github/CLAUDE.md"; exit 1; }; done
prompt: |2
diff --git a/.github/workflows/tend-review-runs.yaml b/.github/workflows/tend-review-runs.yaml
index caeb7ea8d..8ceba0c78 100644
--- a/.github/workflows/tend-review-runs.yaml
+++ b/.github/workflows/tend-review-runs.yaml
@@ -1,4 +1,4 @@
-# Generated by tend 0.2.0. Regenerate with: uvx tend@latest init
+# Generated by tend 0.2.5. Regenerate with: uvx tend@latest init
#
# Do not edit this file directly — it will be overwritten on regeneration.
# To customize behavior, edit the relevant skill (for example,
@@ -103,7 +103,7 @@ jobs:
- uses: ./.github/actions/tend-setup
if: steps.tend_enabled.outputs.enabled == 'true'
- - uses: max-sixty/tend/[email protected]
+ - uses: max-sixty/tend/[email protected]
if: steps.tend_enabled.outputs.enabled == 'true'
with:
github_token: ${{ secrets.TEND_BOT_TOKEN }}
@@ -111,10 +111,10 @@ jobs:
anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}
bot_name: worktrunk-bot
model: opus
+ checkout_mode: base
+ base_branch: ${{ github.event.repository.default_branch }}
sandbox_setup: |2
mkdir -p ~/.local/bin
- install -m755 /home/runner/.cargo-install/cargo-insta/bin/cargo-insta ~/.local/bin/
- install -m755 /home/runner/.cargo-install/cargo-nextest/bin/cargo-nextest ~/.local/bin/
uv tool install --quiet pre-commit
for t in cargo-insta cargo-nextest pre-commit nu nix; do command -v "$t" >/dev/null || { echo "::error::tend sandbox is missing $t; see Sandbox toolchain in .github/CLAUDE.md"; exit 1; }; done
prompt: |2
diff --git a/.github/workflows/tend-review.yaml b/.github/workflows/tend-review.yaml
index c2f563c36..dc2c35cc0 100644
--- a/.github/workflows/tend-review.yaml
+++ b/.github/workflows/tend-review.yaml
@@ -1,4 +1,4 @@
-# Generated by tend 0.2.0. Regenerate with: uvx tend@latest init
+# Generated by tend 0.2.5. Regenerate with: uvx tend@latest init
#
# Do not edit this file directly — it will be overwritten on regeneration.
# To customize behavior, edit the relevant skill (for example,
@@ -108,9 +108,9 @@ jobs:
TARGET: issues/${{ github.event.pull_request.number }}
GITHUB_TOKEN: ${{ secrets.TEND_BOT_TOKEN }}
- # Two checkouts: `setup:` runs against the base tree, and the PR's own
- # tree lands after it. Setup executes as the runner user, outside the
- # containment the harness builds for the contributor's code.
+ # The runner checkout remains on the reviewed base tree for local setup
+ # actions and their POST chains. The harness creates and selects the PR
+ # topology in an independent disposable clone.
- uses: actions/checkout@v7
if: steps.tend_enabled.outputs.enabled == 'true'
with:
@@ -121,35 +121,7 @@ jobs:
- uses: ./.github/actions/tend-setup
if: steps.tend_enabled.outputs.enabled == 'true'
- # GitHub only materializes refs/pull/N/merge for mergeable PRs — on
- # conflicting PRs it 404s and every downstream step cascades as skipped.
- # Probe first and fall back to /head so review always runs; on fallback
- # the review sees the PR branch in isolation rather than the post-merge
- # tree.
- - name: Resolve PR checkout ref
- id: pr_ref
- if: steps.tend_enabled.outputs.enabled == 'true'
- env:
- GITHUB_TOKEN: ${{ secrets.TEND_BOT_TOKEN }}
- PR: ${{ github.event.pull_request.number }}
- run: |
- if gh api "repos/${{ github.repository }}/git/ref/pull/$PR/merge" --silent 2>/dev/null; then
- echo "ref=refs/pull/$PR/merge" >> "$GITHUB_OUTPUT"
- else
- echo "ref=refs/pull/$PR/head" >> "$GITHUB_OUTPUT"
- echo "::notice::refs/pull/$PR/merge unavailable (likely merge conflict); falling back to /head"
- fi
- - uses: actions/checkout@v7
- if: steps.tend_enabled.outputs.enabled == 'true'
- with:
- ref: ${{ steps.pr_ref.outputs.ref }}
- allow-unsafe-pr-checkout: true
- clean: false
- fetch-depth: 0
- fetch-tags: true
- token: ${{ secrets.TEND_BOT_TOKEN }}
-
- - uses: max-sixty/tend/[email protected]
+ - uses: max-sixty/tend/[email protected]
if: steps.tend_enabled.outputs.enabled == 'true'
with:
github_token: ${{ secrets.TEND_BOT_TOKEN }}
@@ -157,24 +129,15 @@ jobs:
anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}
bot_name: worktrunk-bot
model: opus
+ checkout_mode: review
+ base_branch: ${{ github.event.pull_request.base.ref }}
sandbox_setup: |2
mkdir -p ~/.local/bin
- install -m755 /home/runner/.cargo-install/cargo-insta/bin/cargo-insta ~/.local/bin/
- install -m755 /home/runner/.cargo-install/cargo-nextest/bin/cargo-nextest ~/.local/bin/
uv tool install --quiet pre-commit
for t in cargo-insta cargo-nextest pre-commit nu nix; do command -v "$t" >/dev/null || { echo "::error::tend sandbox is missing $t; see Sandbox toolchain in .github/CLAUDE.md"; exit 1; }; done
prompt: |2
/tend-ci-runner:review ${{ github.event.pull_request.number }}
- - name: Restore local setup actions for POST cleanup
- if: |
- always()
- && (steps.tend_enabled.outputs.enabled == 'true')
- run: |
- dir=.github/actions/tend-setup
- git checkout "$GITHUB_SHA" -- "$dir" ||
- echo "::warning::could not restore $dir from $GITHUB_SHA; POST cleanup of the local action may fail"
-
- name: Remove the eyes reaction
if: |
always()
diff --git a/.github/workflows/tend-triage.yaml b/.github/workflows/tend-triage.yaml
index 9b40ddfc3..ee1c3489c 100644
--- a/.github/workflows/tend-triage.yaml
+++ b/.github/workflows/tend-triage.yaml
@@ -1,4 +1,4 @@
-# Generated by tend 0.2.0. Regenerate with: uvx tend@latest init
+# Generated by tend 0.2.5. Regenerate with: uvx tend@latest init
#
# Do not edit this file directly — it will be overwritten on regeneration.
# To customize behavior, edit the relevant skill (for example,
@@ -116,7 +116,7 @@ jobs:
- uses: ./.github/actions/tend-setup
if: steps.tend_enabled.outputs.enabled == 'true'
- - uses: max-sixty/tend/[email protected]
+ - uses: max-sixty/tend/[email protected]
if: steps.tend_enabled.outputs.enabled == 'true'
with:
github_token: ${{ secrets.TEND_BOT_TOKEN }}
@@ -124,10 +124,10 @@ jobs:
anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}
bot_name: worktrunk-bot
model: opus
+ checkout_mode: base
+ base_branch: ${{ github.event.repository.default_branch }}
sandbox_setup: |2
mkdir -p ~/.local/bin
- install -m755 /home/runner/.cargo-install/cargo-insta/bin/cargo-insta ~/.local/bin/
- install -m755 /home/runner/.cargo-install/cargo-nextest/bin/cargo-nextest ~/.local/bin/
uv tool install --quiet pre-commit
for t in cargo-insta cargo-nextest pre-commit nu nix; do command -v "$t" >/dev/null || { echo "::error::tend sandbox is missing $t; see Sandbox toolchain in .github/CLAUDE.md"; exit 1; }; done
prompt: |2
diff --git a/.github/workflows/tend-weekly.yaml b/.github/workflows/tend-weekly.yaml
index 183e06e64..4ca8b5090 100644
--- a/.github/workflows/tend-weekly.yaml
+++ b/.github/workflows/tend-weekly.yaml
@@ -1,4 +1,4 @@
-# Generated by tend 0.2.0. Regenerate with: uvx tend@latest init
+# Generated by tend 0.2.5. Regenerate with: uvx tend@latest init
#
# Do not edit this file directly — it will be overwritten on regeneration.
# To customize behavior, edit the relevant skill (for example,
@@ -103,7 +103,7 @@ jobs:
- uses: ./.github/actions/tend-setup
if: steps.tend_enabled.outputs.enabled == 'true'
- - uses: max-sixty/tend/[email protected]
+ - uses: max-sixty/tend/[email protected]
if: steps.tend_enabled.outputs.enabled == 'true'
with:
github_token: ${{ secrets.TEND_BOT_TOKEN }}
@@ -111,10 +111,10 @@ jobs:
anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}
bot_name: worktrunk-bot
model: opus
+ checkout_mode: base
+ base_branch: ${{ github.event.repository.default_branch }}
sandbox_setup: |2
mkdir -p ~/.local/bin
- install -m755 /home/runner/.cargo-install/cargo-insta/bin/cargo-insta ~/.local/bin/
- install -m755 /home/runner/.cargo-install/cargo-nextest/bin/cargo-nextest ~/.local/bin/
uv tool install --quiet pre-commit
for t in cargo-insta cargo-nextest pre-commit nu nix; do command -v "$t" >/dev/null || { echo "::error::tend sandbox is missing $t; see Sandbox toolchain in .github/CLAUDE.md"; exit 1; }; done
prompt: |2