CyberSecurityUPandClaude Sonnet 5 3dcfeb7377 feat(web): require an engagement name before launch ...

Wizard's Asset step now opens with a required 'Engagement name' field
(validated before advancing or launching). The name isn't a harness/CLI
concept, so it's persisted server-side as runId -> name in
.neurosploit/web-engagement-names.json (keyed off the CLI's own run id,
captured from its 'run id : ns-...' log line) so the sidebar, live run
header, and run detail can label a run by name instead of the raw
target/run-id, surviving a server restart.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0129WdYHccPsH27k5GGuwijd

2026-08-23 14:20:34 -03:00

..

app.js

feat(web): require an engagement name before launch

2026-08-23 14:20:34 -03:00

index.html

feat(web): require an engagement name before launch

2026-08-23 14:20:34 -03:00

style.css

feat(web): engagement wizard, model/auth picker, Auth & Keys menu, attack-path graph

2026-08-23 14:16:46 -03:00