32 lines
950 B
Markdown
32 lines
950 B
Markdown
# MVP E2E Contract
|
|
|
|
The L0 e2e contract is a sequence contract for future MVP tests. It is not a
|
|
heavy e2e test suite.
|
|
|
|
## DEV Endpoint
|
|
|
|
All MVP acceptance traffic targets:
|
|
|
|
```text
|
|
http://74.48.78.17:6667
|
|
```
|
|
|
|
## Minimal Flow
|
|
|
|
1. Create or select a project.
|
|
2. Start a gateway session for `hwlab-gateway` or `hwlab-gateway-simu`.
|
|
3. Register box resources and capabilities.
|
|
4. Apply a wiring config that passes topology validation.
|
|
5. Start an agent session and worker session.
|
|
6. Request a hardware operation through JSON-RPC.
|
|
7. Emit trace events as the operation is accepted, dispatched, executed, and
|
|
completed.
|
|
8. Persist an evidence record for the operation.
|
|
9. Emit audit events for mutating steps and final outcome.
|
|
|
|
## Acceptance Boundary
|
|
|
|
For L0, acceptance is limited to parseable schemas, stable contract names, and
|
|
minimal in-process validation. PROD deployment, service restarts, and full e2e
|
|
execution are explicitly out of scope.
|