feat(desktop): add redis gui foundation baseline

Co-Authored-By: Paperclip <noreply@paperclip.ing>

docs/qa/test-strategy.md

@@ -0,0 +1,46 @@
+# QA Test Strategy
+
+Date: 2026-03-27
+Owner: QA Engineer
+
+## Test Objectives
+
+- Validate Redis GUI V1 against explicit acceptance criteria, not against "it runs on my machine".
+- Cover both happy paths and failure paths for connection, browsing, editing, TTL, console, and destructive actions.
+- Keep release blocking conditions visible before packaging and launch week.
+
+## Test Layers
+
+| Layer | Purpose | Expected Automation | Exit Signal |
+| --- | --- | --- | --- |
+| Unit | Validate pure logic, parsing, serialization, and state transitions | High | Deterministic CI pass |
+| Integration | Validate Redis protocol handling, repository layer, seed setup, and persistence boundaries | Medium | Seeded Redis scenarios pass |
+| UI smoke | Validate launch, connect, browse, edit, TTL, console, dangerous-action confirmation | Medium | One repeatable smoke flow per OS passes |
+| Regression | Validate previously broken paths and high-risk areas before release | Mixed | No open critical regressions |
+| Release readiness | Validate artifact, install, uninstall, and basic recovery behavior | Low to medium | Checklist complete with evidence |
+
+## Environments
+
+- Linux: current local environment available to QA.
+- macOS: required for release acceptance, currently not provisioned in this repository.
+- Windows: required for release acceptance, currently not provisioned in this repository.
+
+## Test Data Strategy
+
+- Maintain one documented seed dataset for predictable keys, TTL, and value shapes.
+- Track Redis version used for QA evidence.
+- Ensure cleanup steps return the environment to a known state.
+
+## Evidence Standard
+
+- Every pass or fail must cite the command, artifact, or screenshot used.
+- "Blocked" is valid only when the missing prerequisite is named.
+- "Not run" is distinct from "Pass" and must remain visible in checklists.
+
+## Current Gaps On 2026-03-27
+
+- Product shell exists as a visible desktop workspace baseline with shell-level validation and empty-state handling, but not as a complete Redis feature surface.
+- No seed dataset or local Redis automation.
+- No smoke harness, installer path, or CI workflow.
+- Tauri packaging evidence is not currently present in the repository.
+- Backend automated coverage is limited to foundation-model tests in `crates/redis-core`.