e2e-caseslisted

# e2e-cases · Synchronize and Execute Real-Device E2E Test Cases After **any guard logic, protocol, or wiring change** passes unit tests and the verification matrix, this skill synchronizes changes into real-device test cases and **executes physical verification to collect evidence** (paired with `design-sync`: one governs specifications, one governs testing). ## Trigger Scenarios - Guard kernel changes (`classify`/`gate`/`config`): adding blocked command surfaces, exemptions, or closing logic gaps. - Protocol or wiring changes (`platform`/`wire`/`pi`/`index`): encoding, payload extraction, config file placement, or hook commands. ## Steps 1. **Assess Impact Scope**: Map affected clients according to the modified layer: | Modified Layer | Affected Clients | |---|---| | `classify`/`gate`/`config`/`i18n` (Guard kernel) | **All 6 clients** (share the `evaluateCommand` core) | | `platform.ts` (Encoding / Payload extraction) | Corresponding platform files (`claude`/`codex`/`opencode`/`antigravity`) | | `pi.ts` / `index.ts` (In-process integration) | `pi` / `dsh` | | `wire.ts` (Configuration file drop-in) | Corresponding stdin-hook clients | 2. **Synchronize `docs/e2e/<client>.md`**: Add or update test cases under the unified case ID system (`<CLIENT>-A*` Deny / `B*` Allow / `C*` Wire / `D*` Platform-Specific). Specify commands, prerequisite branches, expectations, and key assertion criteria. If changes involve new command families, add cases to `scripts/test