SSH key management UI missing from web frontend (backend-only fix shipped for #19) #47

New issue

Closed

opened 2026-08-14 03:47:22 +00:00 by Mark · 0 comments

Mark commented

2026-08-14 03:47:22 +00:00

Owner

Follow-up filed from QA probe (kanban card t_780d4ea9).

Finding

Issue #19 "Feature: SSH key management UI" was closed (2026-08-08) with two commits (eeba943, 3e55cec) that ship only the backend API. None of the 8 UI acceptance criteria were delivered, even though the issue title itself is a UI feature.

Reproduction steps

Open the devforge web frontend (services/web) and navigate to a session detail view.
Look for an SSH key management tab in the session view.
Search the frontend source: grep -ril ssh services/web/src/ -> zero matches.
List services/web/src/components/ for any SSH-related component -> none exist.

Actual behavior

No SSH key management UI exists anywhere in the web frontend. The backend API (session-scoped /sessions/{session_id}/ssh router in services/api/app/routes/ssh.py: list, generate RSA/Ed25519/FIDO2, import, delete, public key) is present, wired, and covered by tests, but there is no UI to use it.

Expected behavior

Per #19 acceptance criteria, the session view should include:

SSH key management tab in session view
List existing keys
Generate new SSH key pairs (RSA, Ed25519, FIDO2/WebAuthn)
Import existing keys
Copy public key button
Delete key confirmation
Integration with Git credentials

Evidence

Probe (run 986): "None of these UI components exist... Only the backend API was implemented. The issue was closed without the frontend deliverable."
Re-verification (run 1426, 2026-08-13): confirmed unchanged - no commit touching services/web/src/ references SSH; only web commit after Aug 8 is abd81c4 (idle auto-suspend, #10).
Original: #19 (closed with backend-only fix)

Origin

Kanban QA card t_780d4ea9 (probe of closed fixit card t_e9ba1c98).

Follow-up filed from QA probe (kanban card t_780d4ea9). ## Finding Issue #19 "Feature: SSH key management UI" was closed (2026-08-08) with two commits (eeba943, 3e55cec) that ship only the backend API. None of the 8 UI acceptance criteria were delivered, even though the issue title itself is a UI feature. ## Reproduction steps 1. Open the devforge web frontend (services/web) and navigate to a session detail view. 2. Look for an SSH key management tab in the session view. 3. Search the frontend source: `grep -ril ssh services/web/src/` -> zero matches. 4. List `services/web/src/components/` for any SSH-related component -> none exist. ## Actual behavior No SSH key management UI exists anywhere in the web frontend. The backend API (session-scoped `/sessions/{session_id}/ssh` router in services/api/app/routes/ssh.py: list, generate RSA/Ed25519/FIDO2, import, delete, public key) is present, wired, and covered by tests, but there is no UI to use it. ## Expected behavior Per #19 acceptance criteria, the session view should include: - SSH key management tab in session view - List existing keys - Generate new SSH key pairs (RSA, Ed25519, FIDO2/WebAuthn) - Import existing keys - Copy public key button - Delete key confirmation - Integration with Git credentials ## Evidence - Probe (run 986): "None of these UI components exist... Only the backend API was implemented. The issue was closed without the frontend deliverable." - Re-verification (run 1426, 2026-08-13): confirmed unchanged - no commit touching services/web/src/ references SSH; only web commit after Aug 8 is abd81c4 (idle auto-suspend, #10). - Original: https://forgejo.tail018ac4.ts.net/Mark/devforge/issues/19 (closed with backend-only fix) ## Origin Kanban QA card t_780d4ea9 (probe of closed fixit card t_e9ba1c98).