claude-ircbot

Warm-resume the vjt-claude IRC session — reseeds context from today's activity log, adopts/attaches BOTH networks' Monitors (Azzurra + Libera), sweeps for WIP, reports. The canonical bringup protocol: fired by aup_watchdog.py after every /clear (hot path) and reused by /start for cold boot. Self-contained by design.

Cold-boot the vjt-claude IRC persistent session — archives >14d activity log, ensures bot.py + sidecars are running, greets on own JOIN, then runs the shared warm-bringup protocol (/resume). Run once manually when entering this working directory. The hot path (post-/clear) is /resume, NOT this.

Cleanly shut down the vjt-claude IRC session — graceful bot QUIT, final activity-log flush, memory consistency check, Monitor stop. Run before /exit when you plan to relaunch Claude Code later.

Add a permission allow/deny rule to a Claude Code settings file when the harness settings-file write-guard blocks Edit/Write. Use whenever a rule needs to land in .claude/settings*.json (or ~/.claude/settings.json) and a normal Edit/Write would prompt despite a matching allow-glob.