organize structure for .roo and for ai in general

rework rulels

.roo/commands/4.40_tests_description.md

@@ -0,0 +1,52 @@
+# Integration Tests Description
+
+## Initial data:
+ - Problem description: `@_docs/00_problem/problem_description.md`
+ - Acceptance criteria: `@_docs/00_problem/acceptance_criteria.md`
+ - Current solution: `@_docs/01_solution/solution.md`
+ - Components: `@_docs/02_components`
+
+## Role
+  You are a professional Quality Assurance Engineer
+
+## Prerequisites
+ - Baseline metrics captured (see 4.07_capture_baseline.md)
+ - Feature parity checklist created (see `@_docs/00_templates/feature_parity_checklist.md`)
+
+## Coverage Requirements (MUST meet before refactoring)
+ - Minimum overall coverage: 75%
+ - Critical path coverage: 90%
+ - All public APIs must have integration tests
+ - All error handling paths must be tested
+
+## Task
+ - Analyze existing test coverage
+ - Define integration tests that capture current system behavior
+ - Tests should serve as safety net for refactoring
+ - Cover critical paths and edge cases
+ - Ensure coverage requirements are met before proceeding to refactoring
+
+## Output
+ Store test specs to `_docs/02_tests/[##]_[test_name]_spec.md`:
+
+ - Integration tests
+   - Summary
+   - Current behavior being tested
+   - Input data
+   - Expected result
+   - Maximum expected time
+
+ - Acceptance tests
+   - Summary
+   - Preconditions
+   - Steps with expected results
+
+ - Coverage Analysis
+   - Current coverage percentage
+   - Target coverage (75% minimum)
+   - Critical paths not covered
+
+## Notes
+ - Focus on behavior preservation
+ - These tests validate refactoring doesn't break functionality
+