fix template, remove okr, use casan.*

packages/casan-devkit/templates/domain-pack/input/requirement.md

@@ -1,17 +1,16 @@
-# <Project> Requirement (template)
+# __PROJECT_NAME__ Requirements
 
-> Replace this with your domain's requirements. The **FR-xx table below drives the
-> traceability gate** (Plan-10): every `FR-xx` must map to ≥1 code file + ≥1 test in
-> `traceability-map.json`. Keep the `| FR-xx | ... |` table format.
+The scaffold contains only an operational health contract. Replace or extend this document with
+approved product requirements before implementing domain behavior. Every `FR-xx` must map to code
+and test evidence in `traceability-map.json`.
 
 ## Functional Requirements
 
 | ID | Requirement |
-|------|-------------|
-| FR-01 | Example: user can log in and receive a session token |
-| FR-02 | Example: user can create a primary domain entity |
-| FR-03 | Example: user can update entity progress |
+|---|---|
+| FR-01 | The backend exposes a deterministic health status for runtime and deployment probes. |
 
-## Notes
-- Add use cases, constraints, and UI expectations as normal prose below.
-- Secrets/credentials must NOT appear here (H4 input scan will block them).
+## Constraints
+
+- Do not place secrets or credentials in requirements.
+- Product behavior must not be invented from the scaffold placeholder UI.