Starting state

Starting state defines the world your test sees before its first provider call. Keep it explicit so a failed run can be reproduced exactly.

Prefer a curated sample

Each environment has five versioned samples:

archal sample list github
archal sample show github.small-project.v1
archal sample show github.small-project.v1 --raw > github-state.json

The CLI checks the artifact byte count and SHA-256 hash before printing raw state. Every environment page explains the sample purpose, state size, first read, representative mutation, expected diff, reset behavior, and limitations.

Validate custom state

archal state validate github github-state.json
archal state validate supabase schema-and-fixtures.sql

JSON is accepted by all 22 current environments. Supabase samples use guarded SQL. Do not assume SQL is accepted elsewhere.

Load during creation

archal session create github \
  --state github=github-state.json

State loaded during creation becomes the reset baseline.

Replace state later

archal state load <session-id> github github-state.json

This replaces current state and establishes a new baseline. It can erase existing records. Capture the current state and get explicit approval before using it on any sandbox that is not newly created and disposable.

Do not put production data, credentials, or personal information into a sample. State artifacts are test inputs and should remain safe to inspect, store, and reproduce.

⌘I

​Prefer a curated sample

​Validate custom state

​Load during creation

​Replace state later

Prefer a curated sample

Validate custom state

Load during creation

Replace state later