docs(project): refresh baseline verification artifacts

Check in the PM product requirements, refreshed QA acceptance evidence, shared execution split plans, and current-phase status notes so the repo matches the current delivery baseline.

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

plans/2026-03-28-hac-19-local-smoke-assist.md

@@ -0,0 +1,34 @@
+# HAC-19 Local Smoke Assist Surface
+
+Date: 2026-03-28 UTC
+Owner: Senior Frontend Engineer
+Issue: HAC-19
+
+## Goal
+
+Reduce QA and engineer friction during local desktop smoke runs by exposing the existing Redis fixture path and its expected verification actions directly in the desktop shell.
+
+## Selected Scope
+
+- add one bounded utility-rail surface for the local Redis smoke fixture
+- surface the seeded fixture target and expected keys without changing backend contracts
+- add quick actions that switch to the fixture profile and prefill common smoke inputs such as `smoke:` search and safe read commands
+- keep the rest of the desktop shell behavior, backend calls, and destructive boundaries unchanged
+
+## Non-Goals
+
+- no new backend or Tauri commands
+- no fixture lifecycle control from the UI
+- no destructive Redis execution path
+- no visual redesign outside the current workspace language
+
+## Verification Plan
+
+- `pnpm --filter @redis-gui/desktop test`
+- `pnpm run desktop:build`
+
+## Expected User Impact
+
+- QA can move from runbook to in-app validation with less manual typing
+- smoke sessions become easier to reproduce because the fixture path is visible inside the shell
+- browser demo mode and live desktop smoke mode remain clearly separated