feat: scheduled overnight campaigns via Claude Code Routines

[sriumcp]

TL;DR

Move "run this campaign overnight every Sunday" or "run on every PR labelled nous-experiment" from cron + custom scripts to Claude Code Routines (cloud-managed, no host uptime needed).

Why this matters

Overnight Nous runs today need: laptop awake, proxy reachable, someone to relaunch on crash. Routines run on Anthropic infra and can fire on cron OR GitHub events. The natural progression of the user's workflow ("run X campaign tonight, summarize tomorrow") fits Routines exactly.

What's already shipped

• The nous CLI is invocable headlessly (feat: nous CLI — unified command-line interface #114).
• This issue wraps it for Routine-based scheduling.

Proposed approach

1. Document the recipe for registering a Nous campaign as a Routine (Routines docs + a worked example in docs/).
2. Add nous routine create campaign.yaml helper that:
   • Bundles the campaign config + auth + MCP refs.
   • Posts to the Routines API.
   • Returns a Routine ID for management.
3. Pair with Phase 1: Data contracts + protocol doc #6 (MCP): the Routine writes findings to the MCP-exposed campaign store, queryable from any Claude Code session.

Acceptance criteria

• A documented end-to-end example: nous routine create examples/campaign.yaml --schedule "0 2 * * *" runs nightly without local infrastructure.
• PR-triggered routine example: routine fires on PR with label nous-experiment, posts findings as a PR comment.

Out of scope

• Building Anthropic's Routines API itself — this issue uses it.

---

Part of #120.

[sriumcp]

Closed by #153 (squash-merge 3e69b85, merged into reflective 2026-05-24). The merged commit message contains an explicit Closes #134. GitHub auto-close didn't fire because the PR targets reflective rather than the repo's default branch.