M-3: harness scenarios S-DIAG-001..009 in both transport modes (UQ-5) #114

Open
opened 2026-05-12 19:37:07 +00:00 by KofTwentyTwo · 0 comments
KofTwentyTwo commented 2026-05-12 19:37:07 +00:00 (Migrated from github.com)

Goal

File harness scenarios S-DIAG-001..009 covering Diagnostics surface; all in both transport modes.

Scope

  • 9 scenarios
  • Both transport modes per UQ-5
  • Includes single-writer HUD assertion, banner queue invariants, replay 1:1, hardBlock path

Files

  • packages/Harness/Tests/HarnessTests/DiagnosticsScenarioTests.swift (new)

Acceptance

  • 9 scenarios filed
  • All run in both transport modes
  • All green
  • bash scripts/check-no-modal-presentation.sh + behavioral single-writer-HUD gates green

Test

swift test --package-path packages/Harness --filter DiagnosticsScenarioTests green.

Parent epic

#7

Source

.planning/architecture/JARVIS-API-MIGRATION-PLAN.md §2.4 (M-3.6)

## Goal File harness scenarios S-DIAG-001..009 covering Diagnostics surface; all in both transport modes. ## Scope - 9 scenarios - Both transport modes per UQ-5 - Includes single-writer HUD assertion, banner queue invariants, replay 1:1, hardBlock path ## Files - `packages/Harness/Tests/HarnessTests/DiagnosticsScenarioTests.swift` (new) ## Acceptance - [ ] 9 scenarios filed - [ ] All run in both transport modes - [ ] All green - [ ] `bash scripts/check-no-modal-presentation.sh` + behavioral single-writer-HUD gates green ## Test `swift test --package-path packages/Harness --filter DiagnosticsScenarioTests` green. ## Parent epic #7 ## Source `.planning/architecture/JARVIS-API-MIGRATION-PLAN.md` §2.4 (M-3.6)
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: KofTwentyTwo/Jarvis#114