Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

UX Flow Coverage Report

This document tracks end-to-end UX coverage for Aura's runtime harness scenarios across TUI and web surfaces.

Coverage Boundary Statement

UX flow coverage validates user-visible behavior and interaction wiring through runtime harness scenarios. It does not replace protocol conformance, theorem proofs, or differential parity lanes. Use this report for UI/product flow traceability and regression targeting.

Summary Metrics

MetricCount
Harness UX Scenarios13
Parity-Critical Scenarios (TUI + Web)11
Mixed-Runtime Scenarios (TUI + Web distinct keys)2
Auxiliary Coverage Scenarios8
Core UX Flow Domains11

Canonical UX Scenario Set

ScenarioFilePrimary Flow
Scenario 1scenarios/harness/scenario1-invitation-chat-e2e.tomlInvitation acceptance + shared channel + bidirectional chat
Scenario 2scenarios/harness/scenario2-social-topology-e2e.tomlSocial topology and neighborhood operations
Scenario 3scenarios/harness/scenario3-irc-slash-commands-e2e.tomlSlash command lifecycle and moderation commands
Scenario 4scenarios/harness/scenario4-global-nav-and-help-e2e.tomlGlobal navigation and help modal behavior
Scenario 5scenarios/harness/scenario5-chat-modal-and-retry-e2e.tomlChat wizard/modals and retry actions
Scenario 6scenarios/harness/scenario6-contacts-lan-and-contact-lifecycle-e2e.tomlContacts, LAN scan, contact removal
Scenario 7scenarios/harness/scenario7-neighborhood-keypath-parity-e2e.tomlNeighborhood keypath parity and detail navigation
Scenario 8scenarios/harness/scenario8-settings-devices-authority-e2e.tomlSettings: profile, devices, authority panels
Scenario 9scenarios/harness/scenario9-guardian-and-mfa-ceremonies-e2e.tomlGuardian and MFA ceremony flows
Scenario 10scenarios/harness/scenario10-recovery-and-notifications-e2e.tomlRecovery request and notifications surfaces
Scenario 11scenarios/harness/scenario11-demo-full-tui-flow-e2e.tomlFull end-to-end demo-grade TUI flow
Scenario 12scenarios/harness/scenario12-mixed-device-enrollment-removal-e2e.tomlMixed TUI/Web device enrollment + removal
Scenario 13scenarios/harness/scenario13-mixed-contact-channel-message-e2e.tomlMixed TUI/Web contact invite + channel messaging

UX Flow Matrix

Flow DomainMain CoverageSecondary CoverageRuntime Context
Invitation create/acceptScenario 1Scenarios 2, 5, 6, 9, 11, 13TUI + Web
Contact lifecycleScenario 6Scenarios 1, 2, 5, 9, 13TUI + Web
Chat channel + messagingScenario 1Scenarios 3, 5, 11, 13TUI + Web
Slash commands and moderationScenario 3moderation-and-modal-coverage.toml, moderator-assign.tomlTUI-heavy
Global navigation/helpScenario 4Scenario 11TUI + Web
Neighborhood/home operationsScenario 2Scenarios 7, 11, home-roles.tomlTUI + Web
Settings panelsScenario 8Scenarios 9, 10, 12TUI + Web
Device add/removeScenario 12Scenario 8Mixed runtime
Guardian/MFA ceremoniesScenario 9Scenario 10TUI + Web
Recovery + notificationsScenario 10Scenario 8TUI + Web
Mixed-device and mixed-user interoperabilityScenarios 12 and 13cross-authority-contact.tomlMixed runtime

Auxiliary Scenario Coverage

These scenarios are maintained as focused supplements and smoke checks:

Scenario FileFocus
local-discovery-smoke.tomlLocal discovery smoke coverage
mixed-topology-smoke.tomlMixed-topology connectivity smoke
mixed-topology-agent.tomlAgent-level mixed topology behavior
moderation-and-modal-coverage.tomlModeration + modal interaction sweep
moderator-assign.tomlModerator assignment and kick operations
access-override.tomlAccess override modal flow
shared-storage.tomlShared-storage user flow
cross-authority-contact.tomlCross-authority contact + neighborhood path

Coverage Expectations

PR Gate Expectations

  1. Changes to global navigation, settings, chat, contacts, neighborhood, or ceremonies should have at least one impacted canonical scenario updated or re-validated.
  2. Changes that affect both TUI and web behavior should be validated against parity-critical scenarios (1-11) in both runtimes.
  3. Changes to mixed-instance behavior should include scenario 12 and/or 13 coverage.

CI Enforcement

Fast CI runs scripts/check/ux-flow-coverage.sh (just ci-ux-flow-coverage) to enforce that flow-relevant source changes are paired with scenario updates or an update to this report.

Residual Risk Areas

AreaCurrent RiskMitigation Direction
Long-tail modal sequencingMediumAdd focused scenario fragments for rare wizard branch paths
Toast timing/race windowsMediumPrefer persistent-state assertions over toast-only checks
Cross-topology regressionsMediumKeep mixed-topology smoke scenarios in scheduled lanes

References