Feed public meetup pages from Events Management

AGENTS.md

@@ -7,7 +7,7 @@
 
 ## Architecture
 
-- **Astro 6.4.2** static site, deployed to GitHub Pages via `.github/workflows/deploy.yml`
+- **Astro 7.1.5** static site, deployed to GitHub Pages via `.github/workflows/deploy.yml`
 - Content collections in `src/content.config.ts` with YAML data files in `content/<name>/`
   - Partners: `content/partners/*.yaml`
   - Admins: `content/admins/*.yaml`

README.md

@@ -38,6 +38,24 @@ All commands are run from the root of the project, from a terminal:
 | `pnpm astro ...`       | Run CLI commands like `astro add`, `astro check` |
 | `pnpm astro -- --help` | Get help using the Astro CLI                     |
 
+## Meetup data
+
+The homepage and meetup pages are generated from the Events Management public
+meetup feed during each static build:
+
+```txt
+https://em.devcongress.org/api/public/meetups
+```
+
+The adapter validates the versioned public response before generating routes.
+If the feed is unreachable, times out, returns an error, or fails validation,
+the build uses `content/meetups/*.yaml` instead. This keeps the public site
+deployable during a temporary upstream incident without exposing organizer
+credentials or connecting the browser directly to the operational system.
+
+Pushes to `main`, manual workflow runs, and the existing Monday/Thursday
+scheduled builds refresh the static meetup snapshot.
+
 ## Cloudflare Workers deployment
 
 This site remains fully static. `wrangler.jsonc` publishes Astro's `dist/` output through Cloudflare Workers Static Assets; it does not add a server entrypoint, API routes, authentication, or database bindings.

package.json

@@ -14,10 +14,10 @@
     "astro": "astro"
   },
   "dependencies": {
-    "astro": "^6.4.2",
+    "astro": "^7.1.5",
     "zod": "^4.4.3"
   },
   "devDependencies": {
-    "wrangler": "^4.107.1"
+    "wrangler": "^4.115.0"
   }
 }