lifecycle — start, stop, reset, destroy

Four verbs control a clone after it's been spun. All take a clone id and fail with CLONE_NOT_FOUND if it doesn't exist.

resetCopy Anchor Link

hone env reset <id>

Returns a clone to a clean, seeded state without a rebuild — the fastest way to start the next trial from identical input.

It drops the database (terminating live connections), recreates it, re-runs all migrations, restarts the backend to rebind its connection pool, waits for health (90s), and re-applies the clone's last seed if it had one.

  ✓ reset slack-a1b2 (dropped, re-migrated, re-seeded)

startCopy Anchor Link

hone env start <id>

Starts a previously stopped clone. Runs docker compose up -d with the clone's saved ports and marks it running. Silent on success.

stopCopy Anchor Link

hone env stop <id>

Stops a running clone without destroying its data. Runs docker compose stop (volumes preserved) and marks it stopped. Silent on success. Bring it back with start.

destroyCopy Anchor Link

hone env destroy <id>

Tears a clone down completely: docker compose down -v (containers + volumes), drops the database, frees its ports, and removes it from the registry.

  ✓ destroyed slack-a1b2

How they relateCopy Anchor Link

  spin ──▶ [running] ──stop──▶ [stopped] ──start──▶ [running]
              │                                          │
              │◀───────────────── reset ─────────────────┤  (clean + re-seed)
              │                                          │
              └──────────────── destroy ────────────────┘  (gone)