1.5 KiB
1.5 KiB
issueRef, version, updatedBy, updatedAt
| issueRef | version | updatedBy | updatedAt | ||||
|---|---|---|---|---|---|---|---|
| #155 | 9 |
|
1786037927509 |
2026-08-06 — Reopened from user validation on AppImage
- User reports that clipboard paste in the custom CLI chat still does not work in practice.
- Suspected historical scope was around #154/#155; this cycle treats #155 as the user-visible clipboard UX bug and keeps the #154 attachment foundation dependency in view.
- Scope for this cycle: verify whether the regression is frontend paste interception, attachment import, backend routing, or AppImage/runtime mismatch; restore end-to-end paste of clipboard image/file into the custom chat composer.
- Main reopened the ticket and assigned frontend/backend ownership before architecture arbitration.
2026-08-06 — Implementation + QA
- DevBackend verified that no backend contract change was required: clipboard bytes already flow through the #154 attachment pipeline (
contentBase64/sourceKind=clipboard-> Tauri command -> attachment store import). - DevFrontend expanded paste handling to cover images exposed through
clipboardData.files, while keeping the structured attachment send path (attachments, no prompt hack). - Unit/integration tests passed across frontend, application, infrastructure, and app-tauri DTO layers.
- QA verdict: partial. The logic is green in targeted tests, but this environment cannot validate a native OS/Tauri/AppImage clipboard paste e2e. Manual AppImage verification remains the closure point for the user-visible bug.