CyberSecurityUPandClaude Opus 4.8 2dd717492e fix(web): resolve run-id to live job UUID when reopening a running run ...

Opening a running run from the sidebar attached the live view with the
run-id (ns-…), but harness jobs are keyed by their own UUID — so
/api/exploit/<run-id> 404'd and the activity log stayed empty even though
recon/exploitation was running normally in the backend.

Add resolveJobId(run): maps a run-id to the owning live job via
/api/exploit (matching job.runId), falling back to the static detail view
when no live job exists. openRun now resolves before attaching.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

2026-10-15 14:27:30 -03:00

..

vendor

feat(web): xterm.js terminal dock + front-end QA pass

2026-09-07 13:33:16 -03:00

app.js

fix(web): resolve run-id to live job UUID when reopening a running run

2026-10-15 14:27:30 -03:00

index.html

feat: key verification, category filter, installer deps/run, UI polish

2026-10-14 20:09:32 -03:00

logo.svg

v4.3.0: web console parity + report redaction + per-finding wire evidence & re-test

2026-10-14 19:42:16 -03:00

style.css

feat: key verification, category filter, installer deps/run, UI polish

2026-10-14 20:09:32 -03:00