paperclip-bot/redis-gui-foundation
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs(project): refresh baseline verification artifacts

Browse Source 
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>
This commit is contained in:
Senior Frontend Engineer
2026-03-31 10:15:39 +00:00
parent 9c404d54a0
commit b6cbe5a47e
30 changed files with 1619 additions and 44 deletions
Download Patch File Download Diff File Expand all files Collapse all files

13
plans/2026-03-28-frontend-smoke-validation.md
View File

@@ -14,8 +14,9 @@ Revalidate the current desktop frontend and packaging path against the repositor
2. Passed: `pnpm run desktop:build`
3. Passed: `./scripts/redis-fixture/start.sh`
4. Passed: `./scripts/redis-fixture/seed.sh`
5. Passed: `./scripts/redis-fixture/stop.sh`
6. Partial pass: `pnpm run desktop:tauri:build`
5. Passed: `pnpm run desktop:tauri:build`
6. Passed: `./scripts/redis-fixture/stop.sh`
7. Partial pass: `pnpm run desktop:tauri:build:all`
## Artifact Evidence
@@ -24,17 +25,17 @@ Revalidate the current desktop frontend and packaging path against the repositor
## Packaging Outcome
- Tauri build completed the Linux release binary and produced `.deb` and `.rpm` artifacts.
- The same run failed in the AppImage step with `io: Connection reset by peer (os error 104)`.
- The standard Linux packaging path now completes successfully: `pnpm run desktop:tauri:build` produces `.deb` and `.rpm` artifacts.
- The separate full-bundle path `pnpm run desktop:tauri:build:all` still fails in the AppImage step because `linuxdeploy` aborts.
## Remaining Gaps
- No saved Tauri-window screenshots or interaction logs exist yet for live browse, edit, TTL, or command flows.
- macOS and Windows package evidence remains absent.
- AppImage packaging needs a separate rerun or targeted investigation if that bundle format is required.
- AppImage packaging still needs a separate rerun or targeted investigation if that bundle format is required.
- This environment currently has no `DISPLAY`, `xvfb-run`, or desktop screenshot utility, so real-window visual evidence cannot be captured from this session alone.
- The desktop shell now includes a copyable QA snapshot so smoke context can still be recorded as text when screenshots are unavailable.
## Frontend Conclusion
The current repository is beyond shell-only validation: backend tests, browser build, Redis fixture bootstrapping, and Linux package generation all succeed in this environment. The next frontend validation step should happen in a launchable Tauri desktop session so QA can capture visual evidence for the live bridge workflows.
The current repository is beyond shell-only validation: backend tests, browser build, Redis fixture bootstrapping, and the standard Linux `.deb`/`.rpm` package path all succeed in this environment. The next frontend validation step should happen in a launchable Tauri desktop session so QA can capture visual evidence for the live bridge workflows while AppImage remains a separate packaging investigation.