Demo mode. These are captured runs of the real scenarios against a deliberately broken store and a fixed one. All data is synthetic.
Compare runs
MT-REG-008. A failure counts as resolved only when the same scenario version ran again and passed. A scenario that did not run is reported as not executed, never as fixed.
- Resolved 1
- Unchanged 6
| Scenario | Before: user filter missing | After: user filter restored | Change |
|---|---|---|---|
Cross-user isolation MT-ISO-001 | FAIL | PASS | Resolved |
Deletion visibility MT-DEL-003 | PASS | PASS | Unchanged |
Memory integrity MT-INT-006 | PASS | PASS | Unchanged |
Controlled memory poisoning MT-POISON-007 | SKIPPED | SKIPPED | Unchanged |
Session isolation MT-SES-005 | PASS | PASS | Unchanged |
Stale memory MT-STALE-004 | PASS | PASS | Unchanged |
Cross-tenant isolation MT-TEN-002 | PASS | PASS | Unchanged |
Configuration differences
These runs were not configured identically. A changed result can come from configuration rather than code.
- adapter.faults: ignore_user_scope → none
- configuration fingerprint changed