refactor(cursor-rules): reorganize rules into logical directory structure

Restructure .cursor/rules from flat organization to hierarchical categories:
- app/: application-specific rules (timesafari, architectural decisions)
- database/: database-related rules (absurd-sql, legacy dexie)
- development/: development workflow rules
- docs/: documentation standards and markdown rules
- features/: feature-specific implementation rules (camera)
- workflow/: version control and workflow rules

Add base_context.mdc for shared context across all rule categories.
Improves maintainability and discoverability of cursor rules.

.cursor/rules/docs/documentation.mdc

@@ -0,0 +1,14 @@
+---
+alwaysApply: true
+---
+# Directive for Documentation Generation
+
+1. Produce a **small, focused set of documents** rather than an overwhelming volume.
+2. Ensure the content is **maintainable and worth preserving**, so that humans
+are motivated to keep it up to date.
+3. Prioritize **educational value**: the documents must clearly explain the
+workings of the system.
+4. Avoid **shallow, generic, or filler explanations** often found in
+AI-generated documentation.
+5. Aim for **clarity, depth, and usefulness**, so readers gain genuine understanding.
+6. Always check the local system date to determine current date.