Revive

revive — the fleet comes back on its own

What this is not for

This skill owns one thing nothing else owns: what restarts a fleet that has stopped, and what proves it should be restarted at all. Everything around it already has an owner. Route there.

The stance

A schedule may not decide what to do; it may only decide when to look.

The cadence is dumb — two crontab entries, always the same, gated on nothing. Every decision lives in a committed manifest and in facts measured at the moment the tick fires. That split is the whole design, and it is what makes the mechanism survive the two-day gap it exists for: a handoff written on Saturday and fired on Monday describes a fleet that has moved, and a status written into a file reads identically whether it is current or six hours old.

So the manifest stores the assignment and a not-before instant, and never a status. campaign refuses a stored status for the same reason (ADR-0113); this is that rule applied to the second file that could carry one, and revival-manifest-check.sh refuses status, state and progress at any depth rather than at the top level, because the field people actually add is a note inside a role row.

The five preconditions, in order

A launch happens only when all five hold. The order is the substance: each channel after the first cannot report its own absence.

digraph revive {
  rankdir=LR;
  bridge   [label="1. RC bridge up\n(pid + procStart + socket)", shape=box];
  health   [label="2. fleet-health.sh", shape=box];
  when     [label="3. not_before passed", shape=box];
  work     [label="4. campaign has open items", shape=box];
  absent   [label="5. coordinator absent\nfrom the daemon roster", shape=box];
  launch   [label="relaunch the coordinator", shape=doublecircle];
  refuse   [label="refuse, naming which\nprecondition failed", shape=box, style=filled, fillcolor="#ffcccc"];

  bridge -> health -> when -> work -> absent -> launch;
  bridge -> refuse [label="exit 4"];
  health -> refuse [label="exit 2 / 3"];
  when   -> refuse [label="exit 0"];
  work   -> refuse [label="exit 0"];
  absent -> refuse [label="exit 0 / 1"];
}

1. The bridge, because a session launched without it is unreachable, unlistable and unstoppable. Checked as pid plus procStart plus a control socket — a pid alone is reused within hours on a busy host, and a liveness test that reads only the number passes forever.
2. The daemon, via fleet-health.sh, whose 2 and 3 are forwarded unchanged. Without this, step 5 is meaningless: a registry outlives the daemon that served it, and on 2026-08-19 five dead sessions rendered as ordinary for eight hours (M-0014, ADR-0072).
3. The not-before, read from the manifest. A weekly limit, a maintenance window or a deliberate pause is a fact about the work, so it lives with the work.
4. Open items, from the campaign engine. Its undetermined is forwarded, never collapsed into "nothing to do" — those are different sentences.
5. Absence, from the daemon's roster. Never from the session's own state: a wedged session reports running, and a dead one reports whatever the registry last knew.

Why only the coordinator

A cron job that also launched workers would be a second actor provisioning worktrees and reserving identifiers for the same items — the collision successor Phase 1 exists to prevent, arriving from a new direction. So an absent worker is a finding, reported for the coordinator to act on, and the coordinator revives its own fleet the way it always would.

The commands

bash .claude/scripts/fleet-revive.sh --dry-run     # what would happen, launching nothing
bash .claude/scripts/fleet-revive.sh               # the decision, for real
bash .claude/scripts/fleet-heartbeat.sh --once     # one line appended; decides nothing
bash .claude/scripts/revival-manifest-check.sh     # the manifest is a plan, not a status
bash .claude/scripts/revival-cron.sh status        # armed? and what would a tick do?
bash .claude/scripts/revival-cron.sh install       # two entries; idempotent
bash .claude/scripts/revival-cron.sh remove        # exactly what install wrote, and nothing else

Exit codes are the interface, so a caller greps nothing:

The record

One JSON manifest per campaign under .claude/docs/revival/<slug>.json, committed. What it holds, field by field, and what it deliberately does not: revival-record.md.

What the heartbeat is for

It decides nothing and launches nothing. It appends one line per tick — the instant, the bridge verdict, the live session ids, the open-item count — because after the 12h36m gap that produced this skill, nobody could say when the fleet went quiet. Every channel that could have answered was a snapshot of the present, and a snapshot cannot date an absence. A count it could not obtain is written ?, never 0: an invented zero reads as a finished campaign.

Red flags

Quick reference