workflows update

2026-02-28 00:04:55 +03:00
parent 8fa951fc93
commit 442d0e0ac2
25 changed files with 92796 additions and 91258 deletions
--- a/.kilocode/workflows/audit-test.md
+++ b/.kilocode/workflows/audit-test.md
@@ -0,0 +1,103 @@
+---
+description: Audit AI-generated unit tests. Your goal is to aggressively search for "Test Tautologies", "Logic Echoing", and "Contract Negligence". You are the final gatekeeper. If a test is meaningless, you MUST reject it.
+---
+
+**ROLE:** Elite Quality Assurance Architect and Red Teamer.
+**OBJECTIVE:** Audit AI-generated unit tests. Your goal is to aggressively search for "Test Tautologies", "Logic Echoing", and "Contract Negligence". You are the final gatekeeper. If a test is meaningless, you MUST reject it.
+
+**INPUT:**
+1. SOURCE CODE (with GRACE-Poly `[DEF]` Contract: `@PRE`, `@POST`, `@TEST_CONTRACT`, `@TEST_FIXTURE`, `@TEST_EDGE`, `@TEST_INVARIANT`).
+2. GENERATED TEST CODE.
+
+### I. CRITICAL ANTI-PATTERNS (REJECT IMMEDIATELY IF FOUND):
+
+1. **The Tautology (Self-Fulfilling Prophecy):**
+   - *Definition:* The test asserts hardcoded values against hardcoded values without executing the core business logic, or mocks the actual function being tested.
+   - *Example of Failure:* `assert 2 + 2 == 4` or mocking the class under test so that it returns exactly what the test asserts.
+
+2. **The Logic Mirror (Echoing):**
+   - *Definition:* The test re-implements the exact same algorithmic logic found in the source code to calculate the `expected_result`. If the original logic is flawed, the test will falsely pass.
+   - *Rule:* Tests must assert against **static, predefined outcomes** (from `@TEST_FIXTURE`, `@TEST_EDGE`, `@TEST_INVARIANT` or explicit constants), NOT dynamically calculated outcomes using the same logic as the source.
+
+3. **The "Happy Path" Illusion:**
+   - *Definition:* The test suite only checks successful executions but ignores the `@PRE` conditions (Negative Testing).
+   - *Rule:* Every `@PRE` tag in the source contract MUST have a corresponding test that deliberately violates it and asserts the correct Exception/Error state.
+
+4. **Missing Post-Condition Verification:**
+   - *Definition:* The test calls the function but only checks the return value, ignoring `@SIDE_EFFECT` or `@POST` state changes (e.g., failing to verify that a DB call was made or a Store was updated).
+
+5. **Missing Edge Case Coverage:**
+   - *Definition:* The test suite ignores `@TEST_EDGE` scenarios defined in the contract.
+   - *Rule:* Every `@TEST_EDGE` in the source contract MUST have a corresponding test case.
+
+6. **Missing Invariant Verification:**
+   - *Definition:* The test suite does not verify `@TEST_INVARIANT` conditions.
+   - *Rule:* Every `@TEST_INVARIANT` MUST be verified by at least one test that attempts to break it.
+
+7. **Missing UX State Testing (Svelte Components):**
+   - *Definition:* For Svelte components with `@UX_STATE`, the test suite does not verify state transitions.
+   - *Rule:* Every `@UX_STATE` transition MUST have a test verifying the visual/behavioral change.
+   - *Check:* `@UX_FEEDBACK` mechanisms (toast, shake, color) must be tested.
+   - *Check:* `@UX_RECOVERY` mechanisms (retry, clear input) must be tested.
+
+### II. SEMANTIC PROTOCOL COMPLIANCE
+
+Verify the test file follows GRACE-Poly semantics:
+
+1. **Anchor Integrity:**
+   - Test file MUST start with `[DEF:__tests__/test_name:Module]`
+   - Test file MUST end with `[/DEF:__tests__/test_name:Module]`
+
+2. **Required Tags:**
+   - `@RELATION: VERIFIES -> <path_to_source>` must be present
+   - `@PURPOSE:` must describe what is being tested
+
+3. **TIER Alignment:**
+   - If source is `@TIER: CRITICAL`, test MUST cover all `@TEST_CONTRACT`, `@TEST_FIXTURE`, `@TEST_EDGE`, `@TEST_INVARIANT`
+   - If source is `@TIER: STANDARD`, test MUST cover `@PRE` and `@POST`
+   - If source is `@TIER: TRIVIAL`, basic smoke test is acceptable
+
+### III. AUDIT CHECKLIST
+
+Evaluate the test code against these criteria:
+1. **Target Invocation:** Does the test actually import and call the function/component declared in the `@RELATION: VERIFIES` tag?
+2. **Contract Alignment:** Does the test suite cover 100% of the `@PRE` (negative tests) and `@POST` (assertions) conditions from the source contract?
+3. **Test Contract Compliance:** Does the test follow the interface defined in `@TEST_CONTRACT`?
+4. **Data Usage:** Does the test use the exact scenarios defined in `@TEST_FIXTURE`?
+5. **Edge Coverage:** Are all `@TEST_EDGE` scenarios tested?
+6. **Invariant Coverage:** Are all `@TEST_INVARIANT` conditions verified?
+7. **UX Coverage (if applicable):** Are all `@UX_STATE`, `@UX_FEEDBACK`, `@UX_RECOVERY` tested?
+8. **Mocking Sanity:** Are external dependencies mocked correctly WITHOUT mocking the system under test itself?
+9. **Semantic Anchor:** Does the test file have proper `[DEF]` and `[/DEF]` anchors?
+
+### IV. OUTPUT FORMAT
+
+You MUST respond strictly in the following JSON format. Do not add markdown blocks outside the JSON.
+
+{
+  "verdict": "APPROVED" | "REJECTED",
+  "rejection_reason": "TAUTOLOGY" | "LOGIC_MIRROR" | "WEAK_CONTRACT_COVERAGE" | "OVER_MOCKED" | "MISSING_EDGES" | "MISSING_INVARIANTS" | "MISSING_UX_TESTS" | "SEMANTIC_VIOLATION" | "NONE",
+  "audit_details": {
+    "target_invoked": true/false,
+    "pre_conditions_tested": true/false,
+    "post_conditions_tested": true/false,
+    "test_fixture_used": true/false,
+    "edges_covered": true/false,
+    "invariants_verified": true/false,
+    "ux_states_tested": true/false,
+    "semantic_anchors_present": true/false
+  },
+  "coverage_summary": {
+    "total_edges": number,
+    "edges_tested": number,
+    "total_invariants": number,
+    "invariants_tested": number,
+    "total_ux_states": number,
+    "ux_states_tested": number
+  },
+  "tier_compliance": {
+    "source_tier": "CRITICAL" | "STANDARD" | "TRIVIAL",
+    "meets_tier_requirements": true/false
+  },
+  "feedback": "Strict, actionable feedback for the test generator agent. Explain exactly which anti-pattern was detected and how to fix it."
+}
--- a/.kilocode/workflows/speckit.implement.md
+++ b/.kilocode/workflows/speckit.implement.md
@@ -117,7 +117,11 @@ You **MUST** consider the user input before proceeding (if not empty).
   - **Validation checkpoints**: Verify each phase completion before proceeding

 7. Implementation execution rules:
-   - **Strict Adherence**: Apply `.ai/standards/semantics.md` rules - every file must start with [DEF] header, include @TIER, and define contracts.
+   - **Strict Adherence**: Apply `.ai/standards/semantics.md` rules:
+     - Every file MUST start with a `[DEF:id:Type]` header and end with a closing `[/DEF:id:Type]` anchor.
+     - Include `@TIER` and define contracts (`@PRE`, `@POST`).
+     - For Svelte components, use `@UX_STATE`, `@UX_FEEDBACK`, `@UX_RECOVERY`, and explicitly declare reactivity with `@UX_REATIVITY: State: $state, Derived: $derived`.
+     - **Molecular Topology Logging**: Use prefixes `[EXPLORE]`, `[REASON]`, `[REFLECT]` in logs to trace logic.
   - **CRITICAL Contracts**: If a task description contains a contract summary (e.g., `CRITICAL: PRE: ..., POST: ...`), these constraints are **MANDATORY** and must be strictly implemented in the code using guards/assertions (if applicable per protocol).
   - **Setup first**: Initialize project structure, dependencies, configuration
   - **Tests before code**: If you need to write tests for contracts, entities, and integration scenarios
--- a/.kilocode/workflows/speckit.plan.md
+++ b/.kilocode/workflows/speckit.plan.md
@@ -73,13 +73,13 @@ You **MUST** consider the user input before proceeding (if not empty).
   - Entity name, fields, relationships, validation rules.

 2. **Design & Verify Contracts (Semantic Protocol)**:
-   - **Drafting**: Define [DEF] Headers and Contracts for all new modules based on `.ai/standards/semantics.md`.
+   - **Drafting**: Define `[DEF:id:Type]` Headers, Contracts, and closing `[/DEF:id:Type]` for all new modules based on `.ai/standards/semantics.md`.
   - **TIER Classification**: Explicitly assign `@TIER: [CRITICAL|STANDARD|TRIVIAL]` to each module.
-   - **CRITICAL Requirements**: For all CRITICAL modules, define full `@PRE`, `@POST`, and (if UI) `@UX_STATE` contracts.
+   - **CRITICAL Requirements**: For all CRITICAL modules, define full `@PRE`, `@POST`, and (if UI) `@UX_STATE` contracts. **MUST** also define testing contracts: `@TEST_CONTRACT`, `@TEST_FIXTURE`, `@TEST_EDGE`, and `@TEST_INVARIANT`.
   - **Self-Review**:
-     - *Completeness*: Do `@PRE`/`@POST` cover edge cases identified in Research?
+     - *Completeness*: Do `@PRE`/`@POST` cover edge cases identified in Research? Are test contracts present for CRITICAL?
     - *Connectivity*: Do `@RELATION` tags form a coherent graph?
-     - *Compliance*: Does syntax match `[DEF:id:Type]` exactly?
+     - *Compliance*: Does syntax match `[DEF:id:Type]` exactly and is it closed with `[/DEF:id:Type]`?
   - **Output**: Write verified contracts to `contracts/modules.md`.

 3. **Simulate Contract Usage**:
--- a/.kilocode/workflows/speckit.tasks.md
+++ b/.kilocode/workflows/speckit.tasks.md
@@ -121,8 +121,8 @@ Every task MUST strictly follow this format:

 2. **From Contracts (CRITICAL TIER)**:
   - Identify components marked as `@TIER: CRITICAL` in `contracts/modules.md`.
-   - For these components, **MUST** append the summary of `@PRE`, `@POST`, and `@UX_STATE` contracts directly to the task description.
-   - Example: `- [ ] T005 [P] [US1] Implement Auth (CRITICAL: PRE: token exists, POST: returns User) in src/auth.py`
+   - For these components, **MUST** append the summary of `@PRE`, `@POST`, `@UX_STATE`, and test contracts (`@TEST_FIXTURE`, `@TEST_EDGE`) directly to the task description.
+   - Example: `- [ ] T005 [P] [US1] Implement Auth (CRITICAL: PRE: token exists, POST: returns User, TESTS: 2 edges) in src/auth.py`
   - Map each contract/endpoint → to the user story it serves
   - If tests requested: Each contract → contract test task [P] before implementation in that story's phase

--- a/.kilocode/workflows/speckit.test.md
+++ b/.kilocode/workflows/speckit.test.md
@@ -20,7 +20,7 @@ Execute full testing cycle: analyze code for testable modules, write tests with

 1. **NEVER delete existing tests** - Only update if they fail due to bugs in the test or implementation
 2. **NEVER duplicate tests** - Check existing tests first before creating new ones
-3. **Use TEST_DATA fixtures** - For CRITICAL tier modules, read @TEST_DATA from .ai/standards/semantics.md
+3. **Use TEST_FIXTURE fixtures** - For CRITICAL tier modules, read @TEST_FIXTURE from .ai/standards/semantics.md
 4. **Co-location required** - Write tests in `__tests__` directories relative to the code being tested

 ## Execution Steps
@@ -52,8 +52,8 @@ Determine:

 Create coverage matrix:

-| Module | File | Has Tests | TIER | TEST_DATA Available |
-|--------|------|-----------|------|-------------------|
+| Module | File | Has Tests | TIER | TEST_FIXTURE Available |
+|--------|------|-----------|------|----------------------|
 | ... | ... | ... | ... | ... |

 ### 4. Write Tests (TDD Approach)
@@ -61,7 +61,7 @@ Create coverage matrix:
 For each module requiring tests:

 1. **Check existing tests**: Scan `__tests__/` for duplicates
-2. **Read TEST_DATA**: If CRITICAL tier, read @TEST_ from semantics header
+2. **Read TEST_FIXTURE**: If CRITICAL tier, read @TEST_FIXTURE from semantics header
 3. **Write test**: Follow co-location strategy
   - Python: `src/module/__tests__/test_module.py`
   - Svelte: `src/lib/components/__tests__/test_component.test.js`
@@ -102,6 +102,7 @@ describe('Component UX States', () => {
  // @UX_RECOVERY: Retry on error
  it('should allow retry on error', async () => { ... });
 });
+// [/DEF:__tests__/test_Component:Module]
 ```

 ### 5. Test Documentation
@@ -170,7 +171,7 @@ Generate test execution report:

 - [ ] Fix failed tests
 - [ ] Add more coverage for [module]
- [ ] Review TEST_DATA fixtures
+- [ ] Review TEST_FIXTURE fixtures
 ```

 ## Context for Testing