hostwarden-coordinatorlisted

The operational coordinator of an operations checkout — a background session, one per checkout, that keeps the picture of which session works on which host, relays an announced disruptive step to idle writers on its radius, holds planned sequences across sessions, and watches maintenance windows. It reaches no server and approves nothing. The session start starts it by itself; run in an interactive session, the skill stops it and keeps it off, or starts it again. Use when the user says "stop the coordinator", "turn the coordinator off", "start the coordinator again", "who works where right now?", "which session is on pve1?", "stopp den Koordinator", "schalte den Koordinator ab", "starte den Koordinator wieder", "wer arbeitet gerade wo?", "welche Session ist auf pve1?". Not for announcing a step, which every session does itself (rules/coordination.md → Announce, wait, go).
hostwarden/hostwarden · ★ 2 · AI & Automation · score 61

Install: claude install-skill hostwarden/hostwarden

# hostwarden-coordinator The coordinator of `rules/coordination.md` → The coordinator. It reads the presence map, the impacts, `memory/plans/` and `claude agents --json`, and nothing else: no SSH call, no change to a host, no change to memory but its own entry. ## Which run this is 1. **Load overrides**, key `hostwarden-coordinator`, per `rules/overrides.md`. 2. **Operations checkout only.** In a development checkout or a worktree say so in one line and stop. 3. **Find this session** in `claude agents --json`: the entry whose `sessionId` is `$HOSTWARDEN_SESSION`. `"kind": "background"` is the coordinator's own run (→ The run). Anything else is a person in an interactive session (→ Stopping and starting). Where the entry is missing or the CLI is not there, it is an interactive run. ## Stopping and starting `sh bin/hostwarden-impact coordinator` prints the session of a live coordinator, or exits 1 where none runs; it marks nothing. Its `id` for `claude stop` is the one its `claude agents --json` entry shows. - **The user asks who works where:** where one runs, ask it with `SendMessage` to `hostwarden coordinator` and pass its answer on; otherwise answer from the presence map as → The picture reads it. - **One runs:** ask with the harness's question tool — stop it and keep it off, or leave it running. On stop: `claude stop <id>`, then write `Coordinator: off` under `# Preferences` in `memory/user.md`, creating the heading where it lacks one