feat(desktop): add redis gui foundation baseline
Co-Authored-By: Paperclip <noreply@paperclip.ing>
This commit is contained in:
28
plans/2026-03-27-desktop-live-bridge.md
Normal file
28
plans/2026-03-27-desktop-live-bridge.md
Normal file
@@ -0,0 +1,28 @@
|
||||
# Desktop Live Bridge Plan
|
||||
|
||||
Date: 2026-03-27
|
||||
Owner: Senior Frontend Engineer
|
||||
Related issues: HAC-9, HAC-11
|
||||
|
||||
## Goal
|
||||
|
||||
Move the visible desktop shell from pure mock interaction to partial real integration by consuming the existing Tauri connection-test and command-execution commands without changing backend scope.
|
||||
|
||||
## Scope Delivered
|
||||
|
||||
1. Wire the connection test action to `test_redis_connection` in Tauri desktop mode.
|
||||
2. Wire the command tray to `execute_redis_command` in Tauri desktop mode.
|
||||
3. Keep browser-only `npm run desktop:dev` explicit about demo fallback so PM, CTO, and QA do not mistake it for live Redis behavior.
|
||||
4. Update shared docs so run paths and acceptance language distinguish shell review from desktop integration review.
|
||||
|
||||
## Constraints
|
||||
|
||||
- Do not add or alter Rust command contracts.
|
||||
- Do not present browser-shell fallback as live Redis evidence.
|
||||
- Keep key browsing, editing, and destructive actions inside current shell scope until backend feature contracts are ready.
|
||||
|
||||
## Exit Criteria
|
||||
|
||||
- `npm run desktop:build` succeeds after the bridge work.
|
||||
- The UI labels command history as live or demo.
|
||||
- Tauri desktop mode can attempt a real connection test and command execution through existing commands.
|
||||
Reference in New Issue
Block a user