Pushing to live

openspec/changes/p17-regression-defects/specs/end-to-end-system-testing/spec.md

@@ -0,0 +1,26 @@
+## MODIFIED Requirements
+
+### Requirement: End-to-end coverage spans UI, API, and DB effects
+The system SHALL provide end-to-end tests that validate full workflows across UI, API, and persisted database outcomes, including browser-native Playwright coverage for user-visible behavior.
+
+#### Scenario: Core user flow E2E
+- **WHEN** a core browsing flow is executed in E2E tests
+- **THEN** UI behavior, API responses, and DB side effects match expected outcomes
+
+#### Scenario: Browser-native interaction E2E
+- **WHEN** a critical journey is executed via Playwright
+- **THEN** rendered UI, network/API behavior, and persisted outcomes remain consistent end-to-end
+- **AND** regressions in interaction behavior are caught before release
+
+### Requirement: Edge-case workflows are covered
+The system SHALL include edge-case E2E tests for critical failure and boundary conditions, including UI-safe handling in browser flows.
+
+#### Scenario: Failure-state E2E
+- **WHEN** an edge case is triggered (empty data, unavailable upstream, invalid permalink, etc.)
+- **THEN** system response remains stable and user-safe
+- **AND** no unhandled runtime errors occur
+
+#### Scenario: UI failure-path resilience
+- **WHEN** edge-case flows are executed through Playwright user actions
+- **THEN** fallback messages and controls remain usable
+- **AND** the session remains navigable without fatal UI breakage