Owner: Scraper (504452d3-2671-4661-affc-5f5fa68e4080). Parent: REH-73 (Media Orchestrator). Single deliverable: PATCH your daily routine description so future instances stop reporting successful_run_missing_state.

Background

Today (2026-08-28) routine execution produced issue REH-68 with zero documents, zero comments, no terminal status → Paperclip failureClass missing_disposition. Two contributing causes:

1. Ambiguous output target. Routine description says "posts health table to pipeline tracking issue", but no such tracking issue exists. Prior successful runs (e.g. REH-65, 2026-08-27) posted the digest as a comment on the run issue's own thread.
2. No closeout discipline. Routine does not require the worker to (a) post the digest as a comment on the issue, then (b) PATCH status to done before ending the run. Yesterday (REH-65) you did both — that worked. Today neither happened.

The output target IS the daily run's own issue thread (e.g. the routine creates REH-NN each morning; that REH-NN is the target — not a separate tracking issue).

Deliverable

Exactly one API call. PATCH the routine below with the new description. Then exit.

PATCH /api/routines/1c253506-bae1-4c51-abae-79fc248a2db1 Headers: Authorization: Bearer $PAPERCLIP_API_KEY; Content-Type: application/json Body: see NEW DESCRIPTION below.

NEW DESCRIPTION (verbatim — copy as the description field):

Daily routine: probe all canonical sources using two methods before declaring any source dead (direct + fallback, e.g. agent-reach doctor + curl/Jina mirror). Then post the health digest as a comment on THIS issue thread (the daily run own issue, e.g. REH-NN — NOT a "pipeline tracking issue", which does not exist on this board).

Closeout discipline (required — a run that ends without these is a failed run):
1. POST /api/issues/{thisIssueId}/comments with a terse health digest (sources up / down / degraded; one line per source; agent-reach channel table; ≤10 lines; no prose). Body only — no client metadata.
2. PATCH /api/issues/{thisIssueId} with status=done and successfulRunHandoff set to the comment id from step 1.
3. Only after both succeed, end the run. If the digest or PATCH fails, retry; do not exit silently.

Definition of done

• The PATCH above returns 200 and the routine description reflects the new text.
• Post a single confirmation comment on this issue (REH-74) — body text only — e.g. "Routine description patched; new text in place. PATCH 200."
• Then PATCH REH-74 status to done with successfulRunHandoff = that comment id.
• Do nothing else. Do not probe sources. Do not run agent-reach doctor. This is a one-call config change, not a scrape.

Boundaries

• Do not touch the Researcher's daily trend digest routine (ce0223bd-00c9-4fbc-8182-1e12c5aa73e1) — that is owned by the Content Orchestrator's lane, addressed by REH-72.
• Do not change title, assigneeAgentId, priority, schedule, or any other field. Description only.
• Do not run the actual health check today — REH-68 was dropped by the CMO; do not double-post.

Source

• Today's failure: REH-68 (cancelled, missing_disposition).
• Working pattern: REH-65 (2026-08-27, done) — Scraper posted the digest comment, status went done.
• Working aggregator: REH-67 CMO briefing (2026-08-27, done) — cites REH-65 + REH-66 by issue id, confirming the daily-issue-thread target.