← ClaudeAtlas

test-as-selflisted

Deploy the current instar dist into a throwaway agent home and verify the deploy is healthy — clean evidence instead of post-hoc log forensics. Use BEFORE shipping a change that touches the deploy/lifeline/server path; AFTER landing such a change; or to reproduce a crash observed in the wild.
JKHeadley/instar · ★ 64 · AI & Automation · score 80
Install: claude install-skill JKHeadley/instar
# /test-as-self — Throwaway-Deploy Harness (Part 2.1) > Spec: `docs/specs/SELF-PROPAGATION-HARNESS-SPEC.md` + the Track F section of `docs/specs/MULTI-MACHINE-BOOTSTRAP-ROBUSTNESS-SPEC.md`. Part 1 (the structural poll-ownership lease) ships alongside. Part 2.1 folded the manual recipe below into a single command — use that first; the manual recipe is the fallback for fine-grained control. ## The one-button path (Part 2.1 — use this first) ```bash instar test-as-self --no-roundtrip # deploy + verify only (no bot) instar test-as-self --bot-token <secret-drop-id> # + a real Telegram round-trip instar test-as-self --keep # leave it running for inspection ``` The command runs the seven gated steps automatically (bot-acquire via Secret Drop / target-prep with Bob+canonical-home guards / dist-deploy / process-start + wait for /health + lease / Telegram-Bot-HTTP-API round-trip / `verify.mjs` / signal-safe teardown) and emits a single JSON report; exit 0 = all PASS. Structural guards make it impossible to target your real agent home or Bob, and it refuses a raw bot token on the command line (Secret Drop only). The round-trip uses the Telegram Bot HTTP API directly (not Playwright) — no browser, no flake. Fall back to the manual recipe below only when you need step-by-step control or to debug a single step. ## When to use - **Verifying Part 1 of the spec** — does the server actually auto-demote to send-only when the lifeline owns the