Record who schedules wakeups and starts cron runs, and run them for that person

[alex-clickhouse]

What

Nerve records who scheduled a wakeup or a deferred message and who started a cron run, and a cron run that a person starts runs for that person. Scheduled work follows the session cause model (#515): the agent's work in a session, including a wakeup's turn, is for the session's cause.

How

• Migration v057 adds session_wakeups.created_by_actor_id, session_wakeups.caused_by_actor_id, cron_logs.actor_id and cron_logs.caused_by_actor_id. They are nullable foreign keys to actor_refs, with no backfill. The attribution column registry lists them.
• "Run later" records the person on the wakeup row.
• A wakeup that the agent sets (the Claude CLI's ScheduleWakeup, or the schedule_wakeup tool) records the system actor and the session's cause.
• A wakeup fires in its session, so its turn (tool changes and, in external mode, model requests) is for the session's cause.
• Cron:
  • Scheduled, catch-up and missed runs log the system actor, and their sessions have the system actor as cause.
  • A run that a person starts (the web UI, or POST /api/cron/jobs/{id}/trigger) logs the person. A session that the run creates (an isolated run, or a new persistent generation) has that person as cause.
  • A workflow-run job that a person starts this way starts its run for that person.
• API and UI:
  • GET /api/cron/logs rows carry actor_id and caused_by_actor_id.
  • Sidebar session rows and the session_running event carry pending_wakeup_created_by_actor_id and pending_wakeup_caused_by_actor_id.
  • For a session that waits on a wakeup, the sidebar tooltip names who scheduled it: "by Alice", "by Nerve for Bob" or "by Nerve".

Why

The principal on a model request decides who pays for it, and that principal is the session's cause. A manual cron run must create its session for the person who started it; otherwise it counts as the agent's own work.

Approximations

• A deferred message or a wakeup in an existing session is attributed to that session's cause, also when another person deferred it.
• A persistent cron session that a person's "Run now" created stays attributed to that person for later scheduled runs, until it rotates.

Behaviour changes

• The trigger route resolves the caller's identity and passes it to the run.
• A cron run ID is now the start second plus eight random hex digits (for example cron:nightly:20260102-030405-ac21b72a), so two runs started in the same second get separate sessions. The usage report reads both the old and the new shape.

Testing

• New tests for every path. The external-mode tests check that a fired wakeup in Alice's session names Alice, that a "Run now" session names the person who clicked, and that two people who trigger one job in the same second get separate sessions and headers. Every commit passes its tests.
• Full suite on this branch (the top of the stack): 5931 passed, 39 skipped. Web: build ok, 740 tests passed.

Stack

1. Record each session's cause and who changes a task #515 Actor and cause plumbing; task attribution (base main)
2. Name the session's cause on each model request in external mode #516 Model requests name the session's cause
3. Record who changes a session, and who deletes it #517 Session change attribution
4. Record who answers notifications and reviews plans #518 Notification answers, plan reviews and approval decisions
5. Record who starts, kills and decides workflow runs and review loops #519 Workflow runs and review loops
6. Record who schedules wakeups and starts cron runs, and run them for that person #520 (this PR): Schedules: run-now, run-later and wakeups

🤖 Generated with Claude Code