Verify and harden the reviewer digest delivery to mobile

[schmug]

Task

The entire "stop drowning in PRs" goal depends on the reviewer Routine's escalation digest actually reaching the owner's phone. The reviewer prompt assumes the run's final message "surfaces as a Claude mobile app notification" — this is unverified. Verify whether a headless Routine run pushes a mobile notification; if it does not, change the reviewer to deliver the digest through a channel the owner reliably sees on mobile (e.g. Slack, Telegram, or updating a single pinned GitHub issue).

Context

Routines research indicated observability is per-session at claude.ai/code with no documented push mechanism. If the digest only lives in a session the owner must open, the pipeline does not solve the stated problem. From the post-#306 gap review.

Pointers

• scripts/routine-pipeline/routine-reviewer.md — step 5 (digest delivery)
• docs/routine-pipeline.md — digest channel
• Ledger issue Routine pipeline ledger #304 (a pinned-issue delivery could reuse this pattern)

Constraints

• Delivery must work from a headless Routine (no interactive session).
• Prefer a channel requiring zero owner action to receive (push, not pull).
• No secrets committed; use existing connected integrations.

Acceptance criteria

• Documented finding: does a Routine final message push to mobile? (yes/no, with evidence).
• If no: reviewer delivers the ranked digest via a verified push channel; a test escalation is confirmed received on mobile.
• docs/routine-pipeline.md updated with the actual mechanism.

Out of scope

• The ranking/format of the digest (already specified).

[schmug]

Triage: Bucket C — needs live verification before implementation

This issue requires confirming whether a headless Routine's final message actually reaches mobile (a push notification) or only appears in the session transcript. That can't be verified without running a real Routine and checking a phone, so no implementation is safe until the finding is documented.

Proposed spec (await owner confirmation before any code):

1. Investigation step: Run a headless Routine with a clearly identifiable final message. Check:

   • Does it appear as a push notification on the owner's phone (claude.ai app)?
   • Or is it only visible by opening the session in the UI?

2. If notifications do NOT reach mobile (expected based on Routines research):

   • Update scripts/routine-pipeline/routine-reviewer.md step 5 (digest delivery) to post the digest to a verified push channel instead.
   • Preferred channel (no new secrets): update a single pinned GitHub issue (issue Routine pipeline ledger #304, the ledger) with the digest. The owner can subscribe to issue notifications on mobile for a pull-based check.
   • Alternative: Slack message via existing integration (if configured).
   • Update docs/routine-pipeline.md with the actual delivery mechanism.

3. If notifications DO reach mobile: document that finding in docs/routine-pipeline.md and close this issue.

Blocked on: owner running the verification step and reporting the result here. Once confirmed, this becomes a straightforward Bucket A (doc update + possibly a 1-line prompt change).

---

Generated by Claude Code

[schmug]

Spec draft — delivery channel investigation (bucket C)

Blocker before implementation: The acceptance criteria require empirical evidence about whether a headless Routine's final message pushes to mobile. That evidence determines what gets built. Three realistic outcomes:

Option A — Headless final message already pushes (no code change needed)

If claude.ai/code Routine sessions fire a push notification to the connected mobile app when the session ends, the existing digest format is sufficient. Implementation: zero code, just document the finding in docs/routine-pipeline.md.

Option B — No push; use a pinned GitHub issue (reuses ledger pattern from #304)

The reviewer Routine posts/updates a single pinned issue (schmug/dmarcheck/issues/304 or a dedicated "digest" issue) with the ranked escalation list. The owner subscribes to GitHub notifications for that issue (email/mobile push via the GitHub app). Implementation: update routine-reviewer.md step 5 to call gh issue comment <digest-issue> --body "..." instead of relying on the session final message.

Option C — No push; use Slack DM (if a Slack integration exists)

If a Slack workspace is connected, post the digest to a private DM or #alerts channel. Implementation: update routine-reviewer.md step 5 to call the Slack MCP tool (already wired in the session) to send a DM.

---

Proposed default (to unblock implementation): If no push notification evidence can be gathered, proceed with Option B (pinned GitHub issue / ledger pattern). It requires zero new integrations, reuses the existing #304 ledger, and the GitHub mobile app delivers issue-comment notifications as push by default.

Owner action needed to unblock: Confirm (a) whether you see a mobile push when a Routine session ends naturally, and (b) whether Option B or C is preferred if the answer is no.

Reclassifying as bucket C until the owner confirms the channel choice.

---

Generated by Claude Code

[schmug]

Triaged as bucket C — implementation can't proceed until the empirical question is answered.

Clarifying question: Does a headless Routine's final message produce a mobile push notification on the Claude mobile app? Existing docs suggest sessions are per-tab at claude.ai/code with no documented push mechanism.

Proposed default (if no push): Deliver the ranked digest by appending it to pinned ledger issue #304 as a comment (same channel as the existing ledger line, but with full digest content). This is pull (owner must open GitHub) rather than push — if that's not acceptable, a Slack or Telegram webhook is the next option.

To unblock: Please confirm the finding (does the Routine final message reach your phone — yes/no with evidence) and indicate the preferred fallback channel if no push. Once confirmed, the implementation is a 2–3 line change to scripts/routine-pipeline/routine-reviewer.md step 5.

Needs-spec label applied pending owner response.

---

Generated by Claude Code

[schmug]

Spec question before implementation: does a Routine final message push to mobile?

The acceptance criteria requires a documented finding on this first, then (if push doesn't work) choosing a delivery channel. Before any code change I need to know:

1. Does a headless Routine run surface its final message as a push notification on the Claude mobile app? Based on available Claude Code documentation, Routines are scheduled sessions at claude.ai/code — their session output is visible when you open the session, but there is no documented push/notification mechanism to a mobile device. The assumption in step 5 of routine-reviewer.md ("this surfaces as the Claude mobile app notification/session") appears to be aspirational, not guaranteed.

2. If push doesn't work, which channel should the reviewer use? The issue suggests Slack, Telegram, or a pinned GitHub issue. The ledger issue Routine pipeline ledger #304 already exists as a pinned GitHub issue. Options:

   • Option A: Update a single pinned GitHub issue (like Routine pipeline ledger #304) with the digest — requires no secrets, works headlessly, but is pull not push (owner must check GitHub)
   • Option B: Post to a Slack channel — requires SLACK_WEBHOOK_URL secret in the Routine env; gives push notification on mobile
   • Option C: Accept that mobile notification is not guaranteed and rely on the daily sweep at github.com

My proposed default: Option A (update the pinned ledger issue #304 with the escalation digest). It requires no new secrets, works purely via gh, and the owner already checks that issue. If you want push (Option B), please confirm the Slack webhook is configured.

Labelling as needs-spec and leaving open pending your direction. Once you confirm the channel, implementation is a 2-line change to routine-reviewer.md step 5.

---

Generated by Claude Code