Feature request: deep-link URL scheme to open a specific scheduled task run

Summary

When a scheduled task completes, the in-app notification links directly to that run. But there's no way to include that same deep link in an external notification (Slack DM, email, etc.) because no public URL scheme exists for it.

Use case

I have a daily scheduled task (smirk-daily-snapshot) that posts a Slack DM when it finishes. I want that message to include a link that opens Claude directly to that run — the same way the completion notification does.

What exists today

• claude://app — opens the app, no specific destination
• claude://cowork/shared-artifact?uuid=… — links to a specific Cowork artifact
• claude://resume?session=<UUID> — appears in the app binary and navigates to a session by UUID (discovered by searching the app bundle), but requires knowing the UUID

The claude://resume?session=<UUID> route works, but it's undocumented and requires the task to discover its own session UUID at runtime (e.g. by finding the newest .jsonl in ~/.claude/projects/<slug>/). That's fragile.

Requested

A stable, documented URL scheme for linking to scheduled task runs, e.g.:

• claude://scheduled-tasks/<task-name>/latest — opens the most recent run of a named task
• Or document claude://resume?session=<UUID> and provide the session UUID to the task at runtime (e.g. as an env var CLAUDE_SESSION_UUID)

Either would let external notifications link directly to the run without fragile filesystem hacks.

Impact

This enables a common pattern: run a scheduled task, post a summary to Slack/email, include a one-tap link back to the full interactive session in Claude.