e2e-testinglisted

# End-to-End Testing Simulate a real user interacting with the application from start to finish. E2E tests run against the actual application (browser, CLI, or API server) with real or realistic dependencies, verifying that the full user journey works. ## When to write - **New feature**: after unit and feature tests pass, verify the complete user journey works end-to-end. - **Bug fix**: reproduce the exact user scenario that triggered the bug, confirm the fix works in the real application. - **Cross-service changes**: when changes span multiple components, modules, or API endpoints, verify the full flow. ## What to test - **Complete user journey**: every step a real user would take from entry to goal completion. - **Realistic environment**: run against the actual application (local dev server, test server, or staging), not mocks. - **Data flow**: verify data persists and flows correctly through the full stack (frontend to database, API to UI, CLI to file system). - **State transitions**: confirm the application state changes correctly at each step (created, submitted, processed, completed). - **Error recovery**: verify the user can recover from errors in the real application (retry, go back, correct input). - **Cross-browser/cross-platform** (when applicable): test at least the primary browser or platform the feature targets. ## What not to test - Unit-level logic (covered by unit tests). - Implementation details or internal state. - Third-party service internals. - Ev