tasks ready 1

.opencode/command/speckit.tasks.md

@@ -173,3 +173,29 @@ Before finalizing `tasks.md`, verify that:
 - no task text schedules a rejected path
 - story tasks remain executable within the actual Python/Svelte project structure
 - at least one explicit verification task protects against rejected-path regression
+
+### Fixture Materialization Tasks
+
+If `/speckit.plan` generated canonical fixtures in `specs/<feature>/fixtures/`, create materialization tasks that copy them into the repo-native test directories before writing test code:
+
+**Backend fixtures:**
+```text
+- [ ] TXXX [P] [US1] Materialize fixtures from specs/<feature>/fixtures/api/ into backend/tests/fixtures/<domain>/
+      Source: fixtures/api/auth_login_*.json
+      Target: backend/tests/fixtures/auth/
+      Each fixture → one JSON file. Do NOT modify fixture content — copy as-is.
+```
+
+**Frontend fixtures:**
+```text
+- [ ] TXXX [P] [US1] Materialize fixtures from specs/<feature>/fixtures/model/ into frontend/src/lib/models/__fixtures__/<model>/
+      Source: fixtures/model/migration_*.json
+      Target: frontend/src/lib/models/__fixtures__/migration/
+```
+
+**Rules:**
+- Materialization tasks are [P] (parallel, different directories)
+- Materialize BEFORE test-writing tasks — tests import fixtures
+- Fixtures are copied as-is from canonical source — no adaptation at this stage
+- If canonical fixture shape doesn't match test framework expectations, create a separate adapter task
+- Every fixture in `manifest.md` gets exactly one materialization task