agenttwin 0.3.7 → 0.3.9

package/README.md

@@ -45,10 +45,13 @@ Sign in with `npx agenttwin login`. For an operator-managed API, you can instead
 export AGENTTWIN_API_URL=https://your-agenttwin-api.example.com
 export AGENTTWIN_TOKEN=your_individual_token
 npx agenttwin run --runtime hosted --file agenttwin-example/agenttwin.world.json
+npx agenttwin run --runtime hosted --file agenttwin-example/agenttwin.world.json --fault timeout-after-write
 npx agenttwin run --runtime hosted --file agenttwin-example/safe.world.json
 ```
 
-The first run should fail: a write commits but its response is delayed, and an unsafe retry creates two tickets. The safe version reuses an idempotency key and passes. Both execute real application code against a custom ticket API and a bounded Slack adapter. Every run starts from fresh seeds and credentials, then deletes its sandbox. These are examples you can replace, not a refund-specific product.
+The first run is clean and should pass. The second opts into `--fault timeout-after-write` and should fail: a write commits but its response is delayed, and an unsafe retry creates two tickets. The safe version reuses an idempotency key and passes. Both execute real application code against a custom ticket API and a bounded Slack adapter. Every run starts from fresh seeds and credentials, then deletes its sandbox. These are examples you can replace, not a refund-specific product.
+
+`run --fault none` disables an active fault. `--fault configured` uses the existing active fault; a named `faults` preset (or the active fault type) opts into its declared target and parameters. Unknown selections fail before execution; AgentTwin never guesses a target. Presets alone inject nothing. For `verify`, pass the same `--fault` selection as the original run, or verify against the effective `world.json` saved beside the receipt. Replay uses that saved effective world automatically. Seed matrices also honor the selection.
 
 `run --json` emits a receipt with source/spec hashes, application output, ordered service events, initial/final service state, assertions, fault activation, runner details and Git metadata when available. Evidence stays in `.agenttwin/runs/`. Exit codes: 0 passed; 1 failed/error; 2 incomplete/blocked; 3 invalid input. An unsupported adapter operation or an untriggered requested fault makes the run incomplete.