# wise-validator integration

wise-validator owns e2e test orchestration, health check semantics, and pass/fail
interpretation. sand-boxer delivers the compose environment; wise-validator runs
the validation story on top.

## Example request

```bash
sandboxer create \
  --profile profile.compose-e2e \
  --input repo=/path/to/repo \
  --actor atm \
  --project wise-validator
```

## Response fields (ready state)

| Field | Owner | Description |
|-------|-------|-------------|
| `sandbox_id` | sand-boxer | Instance id for the validation run |
| `reachability.ssh` | sand-boxer | SSH endpoint for test execution |
| `reachability.compose_project` | sand-boxer | Docker compose project name |
| `reachability.remote_dir` | sand-boxer | Synced repo path on remote host |

## Ownership

| Concern | Owner |
|---------|-------|
| Environment provision (rsync + compose up) | sand-boxer |
| `e2e/e2e.yml` parsing and semantics | wise-validator |
| HTTP health polling and timeouts | wise-validator |
| Test command execution and reporting | wise-validator |
| State Hub test result events | wise-validator |

## Out of scope for sand-boxer

- Running `test_command` from e2e.yml
- Interpreting health check pass/fail
- Posting validation results to State Hub