chore: starter template

e2e/tests/features/auth.feature

@@ -0,0 +1,8 @@
+@auth @smoke
+Feature: Authentication
+  Users sign in with email + password; the session is cookie-based.
+
+  Scenario: a registered user signs in through the login form
+    Given a test account exists
+    When "the user" signs in through the login form
+    Then they land on the app

e2e/tests/features/pages.feature

@@ -0,0 +1,10 @@
+@pages @smoke
+Feature: Every page loads
+  Signed in, every static route must render without an HTTP error, a failed or
+  5xx app API call, an uncaught exception, or a console error. This is the
+  baseline reliability gate — extend it with per-domain behaviour features as
+  the app grows (create/edit/list flows, permissions, etc.).
+
+  Scenario: all pages load cleanly when signed in
+    Given "the user" is signed in
+    Then every page loads without errors