chore: update tend workflows (0.2.14 → 0.2.15)

[worktrunk-bot]

Regenerates the nine tend-*.yaml workflows with tend 0.2.15 (from 0.2.14). The version bump and the astral-sh/setup-uv pin (v10.1.0 → v10.2.0, in the tend-mention and tend-notifications preflight jobs) are mechanical; one step actually moves, in tend-mention.yaml.

tend-mention measures its queue delay before checkout and setup. The "Compute queue delay" step used to run after actions/checkout and ./.github/actions/tend-setup, so the number it recorded was the wait for the job to start plus the several minutes this repo's setup action takes to install the Rust toolchain and sandbox tools. It now runs first, and the delay reports the queue wait alone (max-sixty/tend#1365).

Behavior that arrives inside the action rather than in these files, and that shows up in what the bot posts here:

• PR reviews lead with a finding. A review body now opens with something actionable instead of restating the verdict GitHub already renders in its own header (max-sixty/tend#1362), and a follow-up review scopes itself to what the latest push changed while still reading the whole PR (max-sixty/tend#1368).
• Fewer self-directed fix rounds on bot PRs. On a PR with no human author the review session applies its own findings; each further round now has to clear a higher bar, so a bot PR stops accumulating marginal follow-up commits (max-sixty/tend#1366).
• AGENTS.override.md joins the pinned instruction paths. Codex reads it in preference to AGENTS.md, so on a PR-derived checkout it is now restored from the base commit alongside CLAUDE.md, AGENTS.md, .claude/, and .agents/ — a fork can no longer reach the session through that filename. The same release makes a restrict-updates ruleset a tend check requirement; this repo already satisfies it (tend check passes every line today) (max-sixty/tend#1367).

Full comparison: 0.2.14...0.2.15.