vjt

Full deploy pipeline — test, typecheck, deploy to HAOS, smoke test

End-of-session protocol — push, checkpoint, CHANGELOG, docs, todo

Session start protocol — workflow gates, pending work, status report

Structured investigation — HA logs, API trace, code trace. No code changes until approved.

Bump version, publish to PyPI, create GitHub release, update HACS manifest

Dispatch 8 parallel agents for full codebase review (line-level + architecture)

Babysit a sibling Claude Code session in another tmux pane through a long-running plan. On every idle, ask the session if /clear is useful; if yes, sibling Writes its self-contained next-prompt body to /tmp/orchestrate-next.txt, orchestrator runs /clear and tells sibling to Read+execute that file (no paste-buffer). Halt on design questions or unexpected deviations. On every /orchestrate invocation it FIRST reads the handoff doc /srv/grappa/.orchestrate/orchestrator-resume.md (the persistent brain) then reconciles against the per-pane daemon state — so /orchestrate alone resumes with zero extra instruction; user can /clear freely to save tokens.

Dispatch parallel codebase or architecture review agents per docs/reviewing.md

End-of-session protocol — push, checkpoint, docs, story episode

Session start protocol — workflow gates, pending work, status report

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.

Poll open ha-eisenberg GitHub issues for reporter replies (esp. debug logs), then analyze and report. Use to (re)start issue monitoring — after /clear, at session start, or when waiting on a reporter's log.

Full deploy pipeline — test, typecheck, deploy to HAOS, smoke test

Bump version, publish to PyPI, create GitHub release

End-of-session protocol — push, checkpoint, docs, story episode

Session start protocol — workflow gates, pending work, status report

Session start protocol — pending work, git status, review gate

End-of-session protocol — push, update docs and memories, report