add initial model tests; update agents.md

.gitignore

@@ -2,4 +2,7 @@
 .claude/
 
 ## test output
-output.md
+output.md
+
+## node status
+nodes.md

AGENTS.md

@@ -30,10 +30,12 @@ target: 5–50 users at launch, growing by invite only.
 - no premium tier. no donor badges. no class hierarchy in the app.
 - no manifesto, no political iconography on any user-facing surface.
 - `is_event` flag on posts for bulletin board. not a separate entity.
+- posters: anyone can post. three post types, single required tag: `event` | `fundraiser` | `current affairs`. auto-archives 1 day after `event_ends_at`. layout: 2-column grid, infinite scroll, paginated fetch.
 - reactions: poster defines up to 5 emoji + open picker fallback. stored as user + post + emoji + timestamp.
 - save/bookmark: optional, toggled by poster at compose. default off.
 - story interactions: no replies. "witnessed" metadata only, private, 24h.
 - comments: flat, chronological, on posts only.
+- surveys: admin-only creation. multiple choice only. 36h expiry. injected as slot-1 feed card (not a real post), drops per-user after response. `/feedback` always has free text field regardless of active survey.
 
 **ux**
 - users should never be asked to understand anything instagram doesn't ask them to understand.

model-tests/01-architectural-risk.md

@@ -0,0 +1,9 @@
+tests: critical reasoning, constraint awareness
+context: AGENTS.md
+version: 1
+
+---
+
+read @AGENTS.md. you are a senior backend engineer reviewing this project's architectural decisions before the first line of code is written.
+
+identify up to three decisions that carry the most technical risk or hidden complexity. for each one: name the decision, explain the specific risk, and suggest one mitigation. be direct — this is a pre-build review, not a validation exercise.

model-tests/02-flutter-folder-structure.md

@@ -1,11 +1,10 @@
-{
-you are helping design the frontend of eutopic — a
-photo-first social app for small, invite-only
-communities. it runs on flutter (dart). it has five
-main screens: home feed, posters (bulletin board),
-compose (center tab), stories, and profile. it also
-has secondary screens for onboarding, settings, and
-feedback. here's specs:
+tests: instruction-following, feature-first structure, domain accuracy
+context: DESIGN.md excerpt (screens + navigation)
+version: 2
+
+---
+
+you are helping design the frontend of eutopic — a photo-first social app for small, invite-only communities. it runs on flutter (dart). it has five main screens: home feed, posters (bulletin board), compose (center tab), stories, and profile. it also has secondary screens for onboarding, settings, and feedback. here's specs:
 
 ---
 
@@ -124,20 +123,11 @@ RSVP interaction model: open question, not designed yet. see OPEN-QUESTIONS.md.
 
 ---
 
-eutopic has no notifications, no DMs (chat), and no push
-alerts. do not include any notification-related files
-or widgets.
+eutopic has no notifications, no DMs (chat), and no push alerts. do not include any notification-related files or widgets.
 
 use feature-first structure. example:
 lib/features/feed/feed_screen.dart
 lib/features/feed/widgets/post_card.dart
 lib/shared/models/user.dart
 
-draw an ASCII tree diagram of the flutter frontend
-folder and file structure. include lib/ as the root.
-show actual filenames (*.dart), not just folder names.
-}
-
-{
-read @AGENTS.md and @docs/ROADMAP.md. given the stack choices and the team size (1-2 people), does the feature scope for v0 and v1 feel right-sized, or is it too ambitious? focus on scope, not timeline.
-}
+draw an ASCII tree diagram of the flutter frontend folder and file structure. include lib/ as the root. show actual filenames (*.dart), not just folder names.

model-tests/03-roadmap-scope.md

@@ -0,0 +1,7 @@
+tests: technical judgment, scope reasoning, team-size awareness
+context: AGENTS.md + ROADMAP.md
+version: 1
+
+---
+
+read @AGENTS.md and @docs/ROADMAP.md. given the stack choices and the team size (1-2 people), does the feature scope for v0 and v1 feel right-sized, or is it too ambitious? focus on scope, not timeline.

model-tests/04-elysia-basic-server.md

@@ -0,0 +1,13 @@
+tests: coding ability, elysia/bun knowledge, route handling
+context: none
+version: 1
+
+---
+
+write a minimal elysia (bun) http server in a single file. it should have three routes:
+
+GET /health — returns { status: "ok" }
+GET /users — returns a hardcoded array of 2-3 user objects with id, name, and email fields
+POST /users — accepts a JSON body with name and email, logs the received data to console, and returns { received: true }
+
+no database, no auth, no external dependencies beyond elysia itself. the file should be runnable with `bun run index.ts`.