vers run-commit <commit-key>                     # by commit ID (UUID)
vers run-commit <repo>:<tag>                     # by repo:tag reference (org-local)
vers run-commit <org>/<repo>:<tag>               # by public repo reference (cross-org)
vers run-commit <org>/<repo>                     # shorthand for <org>/<repo>:latest
vers run-commit <commit-key> --vm-alias web-server
vers run-commit my-app:latest --wait

vers run-commit c123456789abcdef
Sending request to start environment from commit c123456789abcdef...
Environment started successfully from commit c123456789abcdef with root vm 'vm-abc123'.
HEAD now points to: vm-abc123 (from commit c123456789abcdef)

vers run-commit c123456789abcdef --vm-alias web-server
Sending request to start environment from commit c123456789abcdef...
Environment started successfully from commit c123456789abcdef with root vm 'vm-abc123'.
HEAD now points to: web-server (from commit c123456789abcdef)

vers run-commit my-app:latest --vm-alias dev
Sending request to start VM from commit my-app:latest...
VM 'vm-abc123' started successfully from commit my-app:latest.
HEAD now points to: dev (from commit my-app:latest)

vers run-commit acme/ubuntu:latest --vm-alias my-env

# equivalent shorthand (defaults to :latest)
vers run-commit acme/ubuntu --vm-alias my-env

vers commit
Commit created successfully
Commit ID: c234567890abcdef

# Later, recreate this exact state
vers run-commit c234567890abcdef

# Team member shares their commit key
vers run-commit c345678901abcdef  # Exact same environment state

vers run-commit invalid-commit-key
Error: failed to start environment: commit not found

vers run-commit
Error: accepts 1 arg(s), received 0

vers run-commit c123456789abcdef
Environment started successfully...
Warning: .vers directory not found. Run 'vers init' first.

# Start environment from a known good commit
vers run-commit c123456789abcdef
vers connect
# Environment is exactly as it was at commit time

# Team member shares commit key
vers run-commit c234567890abcdef
# Now you have the exact same environment state

# Start from specific commit
vers run-commit c345678901abcdef
vers connect
# Debug in the exact environment where issue occurred

# Use commit key from automated commits
vers run-commit $COMMIT_KEY --vm-alias ci-test-$BUILD_ID
# Run tests in reproduced environment

# From a plain tag
vers run-commit production --vm-alias prod-hotfix

# From a repo tag
vers run-commit my-app:latest --vm-alias staging

VM=$(vers run-commit "$INCIDENT_COMMIT" --wait --format json | jq -r .root_vm_id)
vers execute "$VM" -- journalctl --no-pager -u my-service -n 200
vers kill -y "$VM"

# CI job: boot the exact commit that was green in last week's smoke test
vers run-commit "$KNOWN_GOOD_COMMIT" --wait