fix

.specify/templates/tasks-template.md

@@ -94,11 +94,24 @@ Examples of foundational tasks (adjust based on your project):
 - [ ] T014 [P] [US1] Define TypeScript types in frontend/src/types/[feature].ts (DTOs matching backend Pydantic schemas)
 - [ ] T015 [P] [US1] Create [ScreenName]Model in frontend/src/lib/models/[ScreenName]Model.svelte.ts
 - [ ] T016 [P] [US1] Create [Entity] model in backend/src/models/[entity].py
-- [ ] T017 [US1] Implement [Service] in backend/src/services/[service].py
-- [ ] T018 [US1] Implement [endpoint/feature] in backend/src/api/[file].py
-- [ ] T019 [US1] Create [Component] as thin rendering layer in frontend/src/routes/[...] (binds to model via @RELATION BINDS_TO -> [ModelId])
-- [ ] T020 [US1] Add @INVARIANT validation in model actions
-- [ ] T021 [US1] Add belief-runtime instrumentation in model actions for C4/C5 flows
+- [ ] T017 [US1] Implement [function_name] in backend/src/api/[file].py
+      @PRE: [precondition 1], [precondition 2]
+      @POST: [output guarantee]
+      @DATA_CONTRACT: [InputDTO] → [OutputDTO]
+      @TEST_EDGE: [scenario→outcome], [scenario→outcome]
+- [ ] T018 [US1] Implement [Service.action] in backend/src/services/[service].py
+      @PRE: [guard conditions]
+      @POST: [post state]
+      @SIDE_EFFECT: [external calls, DB writes]
+      @TEST_EDGE: [scenario→outcome]
+- [ ] T019 [US1] Implement [Model.action] in frontend/src/lib/models/[Model].svelte.ts
+      @ACTION [action_name](params): [description]
+      @POST: [state guarantee]
+      @SIDE_EFFECT: [API call, store mutation]
+      @TEST_EDGE: [scenario→outcome]
+- [ ] T020 [US1] Create [Component] in frontend/src/routes/[...] (bind to model via @RELATION BINDS_TO -> [ModelId])
+- [ ] T021 [US1] Add @INVARIANT validation in model actions
+- [ ] T022 [US1] Add belief-runtime instrumentation in model actions for C4/C5 flows
 
 **Checkpoint**: At this point, User Story 1 should be fully functional and testable independently
 
@@ -161,6 +174,9 @@ Examples of foundational tasks (adjust based on your project):
 - [ ] TXXX [P] Additional unit tests (if requested) in tests/unit/
 - [ ] TXXX Security hardening
 - [ ] TXXX Run quickstart.md validation
+- [ ] TXXX [P] **Attention compliance audit**: verify ATTN_1 (first-line density), ATTN_2 (hierarchical IDs), ATTN_3 (`@SEMANTICS` keyword consistency across same-domain contracts), ATTN_4 (contract ≤150 lines, module ≤400 lines) per `semantics-core` §VIII
+- [ ] TXXX [P] **Semantic index rebuild**: `axiom_semantic_index rebuild rebuild_mode="full"` — 0 parse warnings required
+- [ ] TXXX [P] **Orphan audit**: `axiom_semantic_context workspace_health` — confirm no new orphans from this feature
 
 ---
 
@@ -255,6 +271,7 @@ With multiple developers:
 - Stop at any checkpoint to validate story independently
 - Avoid: vague tasks, same file conflicts, cross-story dependencies that break independence
 - Derive implementation tasks from semantic contracts in `contracts/modules.md`, especially `@PRE`, `@POST`, `@SIDE_EFFECT`, `@DATA_CONTRACT`, and UI `@UX_*` tags
+- **For C3+ functions with pre-generated contracts: inline @PRE/@POST/@SIDE_EFFECT/@DATA_CONTRACT/@TEST_EDGE directly into the task description** (see format above at T017-T019). This eliminates cross-file navigation — the implementing agent sees the contract in the task line.
 - For Complexity 4/5 Python modules, include tasks for belief-state logging paths with `logger.reason()`, `logger.reflect()`, and `belief_scope` where required
 - For Complexity 5 or explicitly test-governed contracts, include tasks that cover `@TEST_CONTRACT`, `@TEST_SCENARIO`, `@TEST_FIXTURE`, `@TEST_EDGE`, and `@TEST_INVARIANT`
 - Never create tasks from legacy `@TIER` alone; complexity is the primary execution signal