chore: more cursor rules updates

.cursor/rules/timesafari.mdc

@@ -213,12 +213,20 @@ on older/simpler devices.
   - Use shared test configurations
   - Create reusable test helpers
   - Implement consistent test patterns
+  - F.I.R.S.T. (for Unit Tests)
+    F – Fast
+    I – Independent
+    R – Repeatable
+    S – Self-validating
+    T – Timely
 
 ### SOLID Principles
 
-- **Single Responsibility**: Each class/component should have only one reason to change
+- **Single Responsibility**: Each class/component should have only one reason to 
+  change
   - Components should focus on one specific feature (e.g., QR scanning, DID management)
-  - Services should handle one type of functionality (e.g., platform services, crypto services)
+  - Services should handle one type of functionality (e.g., platform services, 
+  crypto services)
   - Utilities should provide focused helper functions
 
 - **Open/Closed**: Software entities should be open for extension but closed for modification
@@ -304,19 +312,3 @@ on older/simpler devices.
 - Follow privacy-by-design principles
 - Restrict component access to necessary data
 - Implement proper authentication/authorization
-
-### Continuous Integration/Continuous Deployment (CI/CD)
-
-- Automated testing on every commit
-- Consistent build process across platforms
-- Automated deployment pipelines
-- Quality gates for code merging
-- Environment-specific configurations
-
-This expanded documentation provides:
-
-1. Clear principles for development
-2. Practical implementation guidelines
-3. Real-world examples
-4. TypeScript integration
-5. Best practices for Time Safari