style(design): apply Minimal Dark Mode design system\n\n- Switched to complete Dark Mode (OLED-friendly)\n- Established standard color palette matching modern technical aesthetics\n- Changed font to Plus Jakarta Sans for increased legibility\n- Enforced dark mode as default in App.tsx\n- Fixed several React cascading render (setState in useEffect) warnings

2026-04-28 03:49:34 -03:00
1 parent b80531f8a8
commit bac7b5591e
@@ -1,21 +1,21 @@
-## ADDED Requirements
-### Requirement: Use Drizzle ORM for Internal Database
-The system SHALL use Drizzle ORM to access the internal database (`cloud_accounts.db`) and provide type constraints through schema.
-
-#### Scenario: Read cloud account list
- **WHEN** the system reads the `accounts` table
- **THEN** returned data SHALL match Drizzle schema types
-
-### Requirement: Keep Compatibility and Validation for External IDE Database
-The system SHALL preserve compatibility logic and runtime validation when accessing the external IDE database (`ItemTable`).
-
-#### Scenario: Read ItemTable key
- **WHEN** reading a specific key from `ItemTable`
- **THEN** data that fails validation SHALL be logged as warning and skipped
-
-### Requirement: Maintain Database Connection Stability
-The system SHALL preserve existing WAL, `busy_timeout`, and transaction strategies to avoid migration regressions.
-
-#### Scenario: Transactional write consistency
- **WHEN** executing write operations
- **THEN** related updates SHALL be committed within the same transaction
+## ADDED Requirements
+### Requirement: Use Drizzle ORM for Internal Database
+The system SHALL use Drizzle ORM to access the internal database (`cloud_accounts.db`) and provide type constraints through schema.
+
+#### Scenario: Read cloud account list
+- **WHEN** the system reads the `accounts` table
+- **THEN** returned data SHALL match Drizzle schema types
+
+### Requirement: Keep Compatibility and Validation for External IDE Database
+The system SHALL preserve compatibility logic and runtime validation when accessing the external IDE database (`ItemTable`).
+
+#### Scenario: Read ItemTable key
+- **WHEN** reading a specific key from `ItemTable`
+- **THEN** data that fails validation SHALL be logged as warning and skipped
+
+### Requirement: Maintain Database Connection Stability
+The system SHALL preserve existing WAL, `busy_timeout`, and transaction strategies to avoid migration regressions.
+
+#### Scenario: Transactional write consistency
+- **WHEN** executing write operations
+- **THEN** related updates SHALL be committed within the same transaction