Feature/implement e2e tests with mock third party services

.github/dependabot.yml

@@ -5,14 +5,10 @@ updates:
     versioning-strategy: "increase"
     schedule:
       interval: "weekly"
-    open-pull-requests-limit: 20
+    open-pull-requests-limit: 4
     labels:
       - "type: dependencies 🔗"
       - "automerge 🤞"
-      # Ignore list: pin packages that should not be updated automatically
-    ignore:
-      - dependency-name: "zod"
-        update-types: ["version-update:semver-patch", "version-update:semver-minor", "version-update:semver-major"]
   - package-ecosystem: "github-actions"
     directory: "/"
     schedule:

.github/workflows/build-and-test.yml

@@ -20,7 +20,6 @@ jobs:
 
     # Define environment variables once at the job level
     # These will be available to ALL steps in this job
-    # @TODO: Same issue with type-check.yml. These are real keys set on GitHub. But the production build only occurs on Vercel, and it's the only place that needs real keys. Once we set up a test framework using Docker containers for Suprabase, Upstash, etc., we should replace these keys with test keys.
     env:
       CONVERTKIT_API_KEY: ${{ secrets.CONVERTKIT_API_KEY }}
       CONVERTKIT_FORM_ID: ${{ secrets.CONVERTKIT_FORM_ID }}
@@ -94,6 +93,9 @@ jobs:
       - name: Start Supabase stack
         run: npm run containers:supabase:start
 
+      - name: Apply Supabase migrations
+        run: npm run containers:supabase:db-push
+
       - name: Run Playwright E2E tests
         run: npx playwright test
         env:

.vscode/settings.json

@@ -44,6 +44,7 @@
     "Joomla",
     "jscoverage",
     "Karamov",
+    "keyup",
     "KHTML",
     "koko",
     "labelledby",
@@ -69,9 +70,11 @@
     "oklch",
     "Onest",
     "optin",
+    "PGRST",
     "pids",
     "pleroma",
     "Poslovski",
+    "Postg",
     "Qualys",
     "registrator",
     "repost",

@types/window.d.ts

@@ -52,6 +52,11 @@ declare global {
      */
     isPlaywrightControlled?: boolean
 
+    /**
+     * Allows Playwright tests to disable PWA service worker registration
+     */
+    __disableServiceWorkerForE2E?: boolean
+
     /**
      * Snapshot of environment-client results for Playwright assertions
      */

README.md

@@ -36,6 +36,40 @@ git push -u origin feature/your-feature-name
 - Branch name must follow conventions
 - Cannot commit directly to main
 
+### Local Development Server
+
+Use the helper script below to start Astro with `.env.development` automatically loaded:
+
+```bash
+npm run dev:env
+```
+
+The underlying `npm run dev` command remains unchanged for CI and Vercel; `dev:env` is just a convenience for local shells so API routes that depend on `process.env` (cron handlers, email providers, etc.) behave the same way they do in production.
+
+## Supabase Production Initialization
+
+Provisioning the hosted Supabase project uses the same SQL migrations that back local development. When you need to initialize (or update) the production database:
+
+1. Authenticate the Supabase CLI (only required once per machine):
+
+  ```bash
+  npx supabase login
+  ```
+
+1. Link the CLI to the production project (replace the placeholder reference):
+
+  ```bash
+  npx supabase link --project-ref your-production-project-ref --workdir suprabase
+  ```
+
+1. Apply the latest migrations and RLS policies:
+
+  ```bash
+  npm run supabase:db:push
+  ```
+
+The `supabase:db:push` script runs `supabase db push` against the linked project, ensuring every table, index, and policy in `suprabase/migrations` is kept in sync with production.
+
 ## Coding Standards
 
 ### Component Architecture