skills(running-tend): move outage recovery upstream into tend

[worktrunk-bot]

Removes the Outage Recovery section from the overlay; the guidance now lives in tend's bundled review-runs skill, proposed in max-sixty/tend#851.

Why upstream. Nothing in the section was worktrunk-specific: the tend-outage issue shape, the pull_request_target-only trigger that makes a dead tend-review unrecoverable, the session-log message that names the quota limit, and the scheduled-vs-event-triggered split are all properties of tend itself. Every consumer running tend-review loses reviews the same way. That was already the disposition in max-sixty/tend#816 (Gap 2), which the upstream PR closes out.

What changed from the original PR. This branch first carried a three-line correction naming the second subscription limit. That correction is folded into the upstream section instead, so the net diff here is the removal.

Sequencing. Merging this before #851 lands leaves a window with no drain guidance in either place. The window costs one daily sweep at most, and the outage issue accumulates rather than losing data, so it's a maintainer call whether to hold this until upstream merges.

[max-sixty]

this whole section seems like it should be in tend rather than worktrunk? if so, put a small PR into tend and remove from worktrunk

[worktrunk-bot]

Agreed — nothing in it was worktrunk-specific. Opened max-sixty/tend#851, which adds the section to tend's bundled review-runs skill (end of Step 1, where failed runs are already being classified), generalized off worktrunk's names and condensed per tend's skill-authoring rules. It closes out Gap 2 of max-sixty/tend#816, which the upstream PR for Gap 1 (#818) explicitly left open.

This PR now just deletes the section — the three-line correction it originally carried is folded into the upstream text. One sequencing note: merging here before #851 lands leaves a gap with no drain guidance in either place, costing at most one daily sweep (the outage issue accumulates rather than losing rows), so holding this until upstream merges is the safer order if you'd rather not have the window.