chore: update tend workflows (0.1.13 → 0.1.14)

[worktrunk-bot]

Automated nightly regeneration of tend's workflow files.

tend version: 0.1.13 → 0.1.14

Notable changes

• Jobs now name the tend environment with deployment: false (workflows: name the environment with deployment: false tend#852), so GitHub stops filing a deployment record per run and posting it on the pull request. This is what the current tend check flags as environment-deployments (tend check: configuration drift on max-sixty/worktrunk #3729) — regenerating clears it, and check: refuse a job that names the environment and files a deployment tend#853 makes check refuse the old shape going forward.
• id-token: write dropped from every tend job — a side effect of removing the claude-smoke workflow and its tend-manual environment (Remove claude-smoke and the tend-manual environment it required tend#820). None of the remaining jobs use OIDC, so the permission was unused.
• tend-mention counts bot engagement outside jq (fix(mention): count bot engagement outside jq so --paginate can't split it tend#840). gh api --paginate applies --jq once per page, so | length emitted one count per page; past 100 comments the shell variable held 100\n7, the numeric test errored, and the bot fell through to should_run=false — going quiet on exactly its most-engaged threads.
• Review and triage skill fixes — the review-record guards now ignore synthetic reply containers (fix(review): ignore synthetic reply containers in all three review-record guards tend#835), /code-review is ported into a tend-owned skill (fix(review): port /code-review into a tend-owned skill tend#819), and triage substitutes the real issue number into its PR-body templates instead of leaving a placeholder (fix(triage): substitute the issue number into the PR-body templates tend#844).
• Outage reporting is more robust — a stranded outage row now names the trigger it points at (fix(report-failure): name the trigger a stranded outage row points at tend#823), and marking a notification read tolerates a transient run-metadata fetch failure (fix(mark-notification-read): tolerate a transient run-metadata fetch failure tend#843).

Full compare: max-sixty/tend@0.1.13...0.1.14