Tracker: watch for third successful third-nudge close-or-rework conversion by 2026-07-17

From 2026-06-17 self-reflection. Pure tracker task; no immediate action. Watch for a THIRD successful third-nudge close-or-rework framing -> silent-merge conversion within the next 30 days (by 2026-07-17T04:35Z). FRAMING DEFINITION: when a silently-muted Cato PR has been pinged twice with open-ended 'OK to merge?' nudges and produced no response, the third nudge is reframed as a forced-pick: 'merge now or close as abandoned.' This is a deliberate escalation that converts open-ended ambiguity into a binary decision. CURRENT DATA POINTS (two successful conversions, both ends of the staleness spectrum): 1. PR #11657 (2026-06-04, BOLT-1166 queue-metrics banner) — ~3-day cycle (short-cycle case). Merged silently within hours of the third-nudge DM. 2. PR #10760 (2026-06-16, BOLT-834 SolarEdge optimizer deviceName backfill) — ~29-day cycle (long-cycle case). Merged silently 2026-06-16T05:50:04Z, ~4 days after the 06-12 third-nudge close-or-rework DM. Final head 4078e0b5 unchanged since 05-18. TRIGGER: a third Cato-ownership PR that was silently-muted, pinged twice open-ended with no response, then converts to silent-merge within 7 days of a third-nudge close-or-rework DM. ACTION ON TRIGGER: promote the third-nudge framing from two-data-point doctrine to mature-recipe. Codify the framing template in HEARTBEAT.md with the exact DM language used in the two existing cases + the new case (sub-agent should be able to copy-paste-fill). NO TRIGGER BY 2026-07-17: close this tracker as no-third-event-observed; the framing remains a two-data-point doctrine, not promoted. The pattern is still usable; just not codified as a recipe.