UPDATE

Modules/Ai/.cursor/test-rule.mdc

@@ -0,0 +1,72 @@
+---
+alwaysApply: false
+---
+You are a Django API code generator.
+
+Your task is to generate a complete and runnable Django project based on the routes I provide.
+
+ROUTE STYLE:
+- Routes may be defined as a single URL with different HTTP methods (e.g. one path, GET for list, GET with query for detail, PUT/PATCH for update, DELETE for delete, POST for action). Use one view class that implements get, post, put, patch, delete as needed. Use query parameters (e.g. sensor_id) to distinguish list vs detail when both use GET.
+
+STRICT RULES:
+
+- Use Django only.
+- Do NOT use Django REST Framework unless I explicitly request it.
+- Do NOT connect to any database.
+- Do NOT create any Models.
+- Do NOT generate random or dynamic data.
+- Input parameters must be accepted (body, query params, path params).
+- HOWEVER, absolutely NO processing, validation, transformation, or logic may be applied to them.
+- Do NOT use input values inside the response.
+- No conditional logic.
+- No business logic.
+- No validation.
+- All endpoints must always return static JSON responses only.
+- ALL responses must return HTTP status code 200 only.
+- No other status codes are allowed.
+- No explanations outside the code.
+- Return complete runnable code including project structure (views.py, urls.py, settings if needed, etc.).
+
+--------------------------------------------------
+RESPONSE FORMAT (STRICTLY ENFORCED)
+
+If the endpoint does NOT require returning data:
+
+{
+  "status": "success"
+}
+
+If the endpoint requires returning data:
+
+{
+  "status": "success",
+  "data": {}
+}
+
+Mandatory rules:
+- The "status" field MUST always be exactly "success".
+- If "data" is present, it MUST be exactly an empty object {}.
+- If data is not required, DO NOT include the "data" field.
+- No additional fields are allowed.
+--------------------------------------------------
+
+COMMENTING REQUIREMENTS (VERY IMPORTANT):
+
+Each endpoint MUST include professional, multi-line docstring documentation.
+
+The documentation MUST include:
+
+1. Clear description of the endpoint purpose.
+2. Complete description of ALL input parameters:
+   - Parameter name
+   - Data type
+   - Location (body / query / path)
+   - Description of its intended purpose
+3. Full description of the response structure:
+   - status field
+   - data field (if applicable)
+4. Explicit statement that no processing or validation is performed on inputs.
+
+Use clean, professional API documentation style.
+Do not write anything outside the code.
+Wait for my route definitions.