chore: update tend workflows (0.1.22 → 0.1.24)

[prql-bot]

Nightly regeneration of the tend workflow files (uvx tend@latest init).

tend version: 0.1.22 → 0.1.24

Notable changes

• max-sixty/tend#1108 — tend-notifications now also boots when a bot-authored PR looks conflicted, so a conflicted bot PR gets rebased on the frequent poll instead of waiting for the nightly sweep. This is most of the diff in tend-notifications.yaml: a GraphQL scan for non-MERGEABLE bot PRs feeds a new conflict_count output that gates the checkout and agent steps.
• max-sixty/tend#1103 — the generator emits multi-line prompts as a block scalar, replacing the format(...) one-liner in tend-review.yaml.
• max-sixty/tend#1095 — the generator writes the concurrency.queue actionlint ignore itself, so the entry chore: update tend workflows (0.1.20 → 0.1.22) #6252 added by hand is dropped here (see below).
• max-sixty/tend#1087, #1080, #1104, #1107 — review-skill behavior: APPROVE is gated on the author stating the PR is ready rather than just the draft flag, the code-review pass becomes its own step gated at submit, and the posting checks move into a preflight script bound to the outward action.
• max-sixty/tend#1109, #1110 — uv is provisioned for agent sessions, and an experimental Gist-backed memory is available.

Full compare: max-sixty/tend@0.1.22...0.1.24

The actionlint entry

tend init appended its own **/.github/workflows/tend-*.yaml ignore alongside the .github/workflows/tend-*.yaml one #6252 added by hand yesterday — two entries for the same rule. This PR keeps the generated one and drops ours, retaining the comment that explains why the ignore exists at all.

Verification

Checked with actionlint v1.7.12 (the version pinned in .pre-commit-config.yaml) inside the regeneration worktree:

• With no ignore at all, tend-review.yaml:22 fails with unexpected key "queue" for "concurrency" section, so the rule is still live upstream.
• With only the generated **/-prefixed entry, that error is suppressed — the glob does match the root-level path, so dropping the hand-written entry loses nothing.
• actionlint over the whole repo exits 0 with the deduped config.
• prettier@3.9.6 --check is clean; it normalizes the generated entry's single quotes to double quotes, and a second tend init recognizes the normalized key and leaves it alone, so this doesn't churn on the next nightly.

No test accompanies this change — the workflow files are generated, and their behavior is exercised by the tend runs themselves.

[prql-bot]

Nightly regeneration of the tend workflow files (uvx tend@latest init).

tend version: 0.1.22 → 0.1.24

Notable changes

• max-sixty/tend#1108 — tend-notifications now also boots when a bot-authored PR looks conflicted, so a conflicted bot PR gets rebased on the frequent poll instead of waiting for the nightly sweep. This is most of the diff in tend-notifications.yaml: a GraphQL scan for non-MERGEABLE bot PRs feeds a new conflict_count output that gates the checkout and agent steps.
• max-sixty/tend#1103 — the generator emits multi-line prompts as a block scalar, replacing the format(...) one-liner in tend-review.yaml.
• max-sixty/tend#1095 — the generator writes the concurrency.queue actionlint ignore itself, so the entry chore: update tend workflows (0.1.20 → 0.1.22) #6252 added by hand is dropped here (see below).
• max-sixty/tend#1087, #1080, #1104, #1107 — review-skill behavior: APPROVE is gated on the author stating the PR is ready rather than just the draft flag, the code-review pass becomes its own step gated at submit, and the posting checks move into a preflight script bound to the outward action.
• max-sixty/tend#1109, #1110 — uv is provisioned for agent sessions, and an experimental Gist-backed memory is available.

Full compare: max-sixty/tend@0.1.22...0.1.24

The actionlint entry

tend init appended its own **/.github/workflows/tend-*.yaml ignore alongside the .github/workflows/tend-*.yaml one #6252 added by hand yesterday — two entries for the same rule. This PR keeps the generated one and drops ours, retaining the comment that explains why the ignore exists at all.

Verification

Checked with actionlint v1.7.12 (the version pinned in .pre-commit-config.yaml) inside the regeneration worktree:

• With no ignore at all, tend-review.yaml:22 fails with unexpected key "queue" for "concurrency" section, so the rule is still live upstream.
• With only the generated **/-prefixed entry, that error is suppressed — the glob does match the root-level path, so dropping the hand-written entry loses nothing.
• actionlint over the whole repo exits 0 with the deduped config.
• prettier@3.9.6 --check is clean; it normalizes the generated entry's single quotes to double quotes, and a second tend init recognizes the normalized key and leaves it alone, so this doesn't churn on the next nightly.

No test accompanies this change — the workflow files are generated, and their behavior is exercised by the tend runs themselves.

[prql-bot]

Nightly regeneration of the tend workflow files (uvx tend@latest init).

tend version: 0.1.22 → 0.1.24

Notable changes

• max-sixty/tend#1108 — tend-notifications now also boots when a bot-authored PR looks conflicted, so a conflicted bot PR gets rebased on the frequent poll instead of waiting for the nightly sweep. This is most of the diff in tend-notifications.yaml: a GraphQL scan for non-MERGEABLE bot PRs feeds a new conflict_count output that gates the checkout and agent steps.
• max-sixty/tend#1103 — the generator emits multi-line prompts as a block scalar, replacing the format(...) one-liner in tend-review.yaml.
• max-sixty/tend#1095 — the generator writes the concurrency.queue actionlint ignore itself, so the entry chore: update tend workflows (0.1.20 → 0.1.22) #6252 added by hand is dropped here (see below).
• max-sixty/tend#1087, #1080, #1104, #1107 — review-skill behavior: APPROVE is gated on the author stating the PR is ready rather than just the draft flag, the code-review pass becomes its own step gated at submit, and the posting checks move into a preflight script bound to the outward action.
• max-sixty/tend#1109, #1110 — uv is provisioned for agent sessions, and an experimental Gist-backed memory is available.

Full compare: max-sixty/tend@0.1.22...0.1.24

The actionlint entry

tend init appended its own **/.github/workflows/tend-*.yaml ignore alongside the .github/workflows/tend-*.yaml one #6252 added by hand yesterday — two entries for the same rule. This PR keeps the generated one and drops ours, retaining the comment that explains why the ignore exists at all.

Verification

Checked with actionlint v1.7.12 (the version pinned in .pre-commit-config.yaml) inside the regeneration worktree:

• With no ignore at all, tend-review.yaml:22 fails with unexpected key "queue" for "concurrency" section, so the rule is still live upstream.
• With only the generated **/-prefixed entry, that error is suppressed — the glob does match the root-level path, so dropping the hand-written entry loses nothing.
• actionlint over the whole repo exits 0 with the deduped config.
• prettier@3.9.6 --check is clean; it normalizes the generated entry's single quotes to double quotes, and a second tend init recognizes the normalized key and leaves it alone, so this doesn't churn on the next nightly.

No test accompanies this change — the workflow files are generated, and their behavior is exercised by the tend runs themselves.

[prql-bot]

Nightly regeneration of the tend workflow files (uvx tend@latest init).

tend version: 0.1.22 → 0.1.24

Notable changes

• max-sixty/tend#1108 — tend-notifications now also boots when a bot-authored PR looks conflicted, so a conflicted bot PR gets rebased on the frequent poll instead of waiting for the nightly sweep. This is most of the diff in tend-notifications.yaml: a GraphQL scan for non-MERGEABLE bot PRs feeds a new conflict_count output that gates the checkout and agent steps.
• max-sixty/tend#1103 — the generator emits multi-line prompts as a block scalar, replacing the format(...) one-liner in tend-review.yaml.
• max-sixty/tend#1095 — the generator writes the concurrency.queue actionlint ignore itself, so the entry chore: update tend workflows (0.1.20 → 0.1.22) #6252 added by hand is dropped here (see below).
• max-sixty/tend#1087, #1080, #1104, #1107 — review-skill behavior: APPROVE is gated on the author stating the PR is ready rather than just the draft flag, the code-review pass becomes its own step gated at submit, and the posting checks move into a preflight script bound to the outward action.
• max-sixty/tend#1109, #1110 — uv is provisioned for agent sessions, and an experimental Gist-backed memory is available.

Full compare: max-sixty/tend@0.1.22...0.1.24

The actionlint entry

tend init appended its own **/.github/workflows/tend-*.yaml ignore alongside the .github/workflows/tend-*.yaml one #6252 added by hand yesterday — two entries for the same rule. This PR keeps the generated one and drops ours, retaining the comment that explains why the ignore exists at all.

Verification

Checked with actionlint v1.7.12 (the version pinned in .pre-commit-config.yaml) inside the regeneration worktree:

• With no ignore at all, tend-review.yaml:22 fails with unexpected key "queue" for "concurrency" section, so the rule is still live upstream.
• With only the generated **/-prefixed entry, that error is suppressed — the glob does match the root-level path, so dropping the hand-written entry loses nothing.
• actionlint over the whole repo exits 0 with the deduped config.
• prettier@3.9.6 --check is clean; it normalizes the generated entry's single quotes to double quotes, and a second tend init recognizes the normalized key and leaves it alone, so this doesn't churn on the next nightly.

No test accompanies this change — the workflow files are generated, and their behavior is exercised by the tend runs themselves.

[prql-bot]

Nightly regeneration of the tend workflow files (uvx tend@latest init).

tend version: 0.1.22 → 0.1.24

Notable changes

• max-sixty/tend#1108 — tend-notifications now also boots when a bot-authored PR looks conflicted, so a conflicted bot PR gets rebased on the frequent poll instead of waiting for the nightly sweep. This is most of the diff in tend-notifications.yaml: a GraphQL scan for non-MERGEABLE bot PRs feeds a new conflict_count output that gates the checkout and agent steps.
• max-sixty/tend#1103 — the generator emits multi-line prompts as a block scalar, replacing the format(...) one-liner in tend-review.yaml.
• max-sixty/tend#1095 — the generator writes the concurrency.queue actionlint ignore itself, so the entry chore: update tend workflows (0.1.20 → 0.1.22) #6252 added by hand is dropped here (see below).
• max-sixty/tend#1087, #1080, #1104, #1107 — review-skill behavior: APPROVE is gated on the author stating the PR is ready rather than just the draft flag, the code-review pass becomes its own step gated at submit, and the posting checks move into a preflight script bound to the outward action.
• max-sixty/tend#1109, #1110 — uv is provisioned for agent sessions, and an experimental Gist-backed memory is available.

Full compare: max-sixty/tend@0.1.22...0.1.24

The actionlint entry

tend init appended its own **/.github/workflows/tend-*.yaml ignore alongside the .github/workflows/tend-*.yaml one #6252 added by hand yesterday — two entries for the same rule. This PR keeps the generated one and drops ours, retaining the comment that explains why the ignore exists at all.

Verification

Checked with actionlint v1.7.12 (the version pinned in .pre-commit-config.yaml) inside the regeneration worktree:

• With no ignore at all, tend-review.yaml:22 fails with unexpected key "queue" for "concurrency" section, so the rule is still live upstream.
• With only the generated **/-prefixed entry, that error is suppressed — the glob does match the root-level path, so dropping the hand-written entry loses nothing.
• actionlint over the whole repo exits 0 with the deduped config.
• prettier@3.9.6 --check is clean; it normalizes the generated entry's single quotes to double quotes, and a second tend init recognizes the normalized key and leaves it alone, so this doesn't churn on the next nightly.

No test accompanies this change — the workflow files are generated, and their behavior is exercised by the tend runs themselves.

[prql-bot]

Nightly regeneration of the tend workflow files (uvx tend@latest init).

tend version: 0.1.22 → 0.1.24

Notable changes

• max-sixty/tend#1108 — tend-notifications now also boots when a bot-authored PR looks conflicted, so a conflicted bot PR gets rebased on the frequent poll instead of waiting for the nightly sweep. This is most of the diff in tend-notifications.yaml: a GraphQL scan for non-MERGEABLE bot PRs feeds a new conflict_count output that gates the checkout and agent steps.
• max-sixty/tend#1103 — the generator emits multi-line prompts as a block scalar, replacing the format(...) one-liner in tend-review.yaml.
• max-sixty/tend#1095 — the generator writes the concurrency.queue actionlint ignore itself, so the entry chore: update tend workflows (0.1.20 → 0.1.22) #6252 added by hand is dropped here (see below).
• max-sixty/tend#1087, #1080, #1104, #1107 — review-skill behavior: APPROVE is gated on the author stating the PR is ready rather than just the draft flag, the code-review pass becomes its own step gated at submit, and the posting checks move into a preflight script bound to the outward action.
• max-sixty/tend#1109, #1110 — uv is provisioned for agent sessions, and an experimental Gist-backed memory is available.

Full compare: max-sixty/tend@0.1.22...0.1.24

The actionlint entry

tend init appended its own **/.github/workflows/tend-*.yaml ignore alongside the .github/workflows/tend-*.yaml one #6252 added by hand yesterday — two entries for the same rule. This PR keeps the generated one and drops ours, retaining the comment that explains why the ignore exists at all.

Verification

Checked with actionlint v1.7.12 (the version pinned in .pre-commit-config.yaml) inside the regeneration worktree:

• With no ignore at all, tend-review.yaml:22 fails with unexpected key "queue" for "concurrency" section, so the rule is still live upstream.
• With only the generated **/-prefixed entry, that error is suppressed — the glob does match the root-level path, so dropping the hand-written entry loses nothing.
• actionlint over the whole repo exits 0 with the deduped config.
• prettier@3.9.6 --check is clean; it normalizes the generated entry's single quotes to double quotes, and a second tend init recognizes the normalized key and leaves it alone, so this doesn't churn on the next nightly.

No test accompanies this change — the workflow files are generated, and their behavior is exercised by the tend runs themselves.

[prql-bot]

Nightly regeneration of the tend workflow files (uvx tend@latest init).

tend version: 0.1.22 → 0.1.24

Notable changes

• max-sixty/tend#1108 — tend-notifications now also boots when a bot-authored PR looks conflicted, so a conflicted bot PR gets rebased on the frequent poll instead of waiting for the nightly sweep. This is most of the diff in tend-notifications.yaml: a GraphQL scan for non-MERGEABLE bot PRs feeds a new conflict_count output that gates the checkout and agent steps.
• max-sixty/tend#1103 — the generator emits multi-line prompts as a block scalar, replacing the format(...) one-liner in tend-review.yaml.
• max-sixty/tend#1095 — the generator writes the concurrency.queue actionlint ignore itself, so the entry chore: update tend workflows (0.1.20 → 0.1.22) #6252 added by hand is dropped here (see below).
• max-sixty/tend#1087, #1080, #1104, #1107 — review-skill behavior: APPROVE is gated on the author stating the PR is ready rather than just the draft flag, the code-review pass becomes its own step gated at submit, and the posting checks move into a preflight script bound to the outward action.
• max-sixty/tend#1109, #1110 — uv is provisioned for agent sessions, and an experimental Gist-backed memory is available.

Full compare: max-sixty/tend@0.1.22...0.1.24

The actionlint entry

tend init appended its own **/.github/workflows/tend-*.yaml ignore alongside the .github/workflows/tend-*.yaml one #6252 added by hand yesterday — two entries for the same rule. This PR keeps the generated one and drops ours, retaining the comment that explains why the ignore exists at all.

Verification

Checked with actionlint v1.7.12 (the version pinned in .pre-commit-config.yaml) inside the regeneration worktree:

• With no ignore at all, tend-review.yaml:22 fails with unexpected key "queue" for "concurrency" section, so the rule is still live upstream.
• With only the generated **/-prefixed entry, that error is suppressed — the glob does match the root-level path, so dropping the hand-written entry loses nothing.
• actionlint over the whole repo exits 0 with the deduped config.
• prettier@3.9.6 --check is clean; it normalizes the generated entry's single quotes to double quotes, and a second tend init recognizes the normalized key and leaves it alone, so this doesn't churn on the next nightly.

No test accompanies this change — the workflow files are generated, and their behavior is exercised by the tend runs themselves.

[prql-bot]

Nightly regeneration of the tend workflow files (uvx tend@latest init).

tend version: 0.1.22 → 0.1.24

Notable changes

• max-sixty/tend#1108 — tend-notifications now also boots when a bot-authored PR looks conflicted, so a conflicted bot PR gets rebased on the frequent poll instead of waiting for the nightly sweep. This is most of the diff in tend-notifications.yaml: a GraphQL scan for non-MERGEABLE bot PRs feeds a new conflict_count output that gates the checkout and agent steps.
• max-sixty/tend#1103 — the generator emits multi-line prompts as a block scalar, replacing the format(...) one-liner in tend-review.yaml.
• max-sixty/tend#1095 — the generator writes the concurrency.queue actionlint ignore itself, so the entry chore: update tend workflows (0.1.20 → 0.1.22) #6252 added by hand is dropped here (see below).
• max-sixty/tend#1087, #1080, #1104, #1107 — review-skill behavior: APPROVE is gated on the author stating the PR is ready rather than just the draft flag, the code-review pass becomes its own step gated at submit, and the posting checks move into a preflight script bound to the outward action.
• max-sixty/tend#1109, #1110 — uv is provisioned for agent sessions, and an experimental Gist-backed memory is available.

Full compare: max-sixty/tend@0.1.22...0.1.24

The actionlint entry

tend init appended its own **/.github/workflows/tend-*.yaml ignore alongside the .github/workflows/tend-*.yaml one #6252 added by hand yesterday — two entries for the same rule. This PR keeps the generated one and drops ours, retaining the comment that explains why the ignore exists at all.

Verification

Checked with actionlint v1.7.12 (the version pinned in .pre-commit-config.yaml) inside the regeneration worktree:

• With no ignore at all, tend-review.yaml:22 fails with unexpected key "queue" for "concurrency" section, so the rule is still live upstream.
• With only the generated **/-prefixed entry, that error is suppressed — the glob does match the root-level path, so dropping the hand-written entry loses nothing.
• actionlint over the whole repo exits 0 with the deduped config.
• prettier@3.9.6 --check is clean; it normalizes the generated entry's single quotes to double quotes, and a second tend init recognizes the normalized key and leaves it alone, so this doesn't churn on the next nightly.

No test accompanies this change — the workflow files are generated, and their behavior is exercised by the tend runs themselves.