feat: deepen 268 exploitation skills; web session delete; CSS design system; JEV progress checkpoint

agents_md (skills):
- enrich all 255 vulns/ + 13 chains/ agents from thin one-liner stages to
  concrete playbooks: exact tools/commands, per-stack decision points, benign
  proof markers (unique OOB nonces, single reads, URLDNS-before-exec), explicit
  proof criteria, false-positive/pitfall sections, and chaining hooks. Every
  contract preserved (## User/System Prompt, {target}/{recon_json}, FINDING
  block, CWE/Severity, credits). avg 37->53 lines; loader parses all 449.

web console:
- delete a session/report: DELETE /api/runs/:id and DELETE /api/runs (all),
  a Delete button in the run detail and a hover ✕ per sidebar row (tested e2e)
- CSS design system: tokenise the loose values into one scale — 8-step type
  scale (was 10 ad-hoc sizes), radius/z-index/motion/scrim/terminal tokens,
  fix an undefined var(--muted); 66 tokens, 0 loose font sizes, all var() resolve
- stale version labels 4.0.0/4.2.0 -> 4.2.1

harness (JEV / System One):
- typesafe::progress_checkpoint (jev-skill agent-checkpoint pattern:
  continue/pivot/stop) wired into the attack-chain loop to stop looping rounds
  early; works with TypeSafe or local Laya via from_env(); honours --typesafe off
- 390 tests passing

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

agents_md/vulns/spa_api_discovery.md

@@ -8,20 +8,24 @@ You are testing **{target}** for mapping a JS SPA's client-side routes and backe
 **Recon Context:**
 {recon_json}
 
-**METHODOLOGY:**
+**METHODOLOGY — render for real, capture every request, and produce a route+API map the specialist agents can act on. Prove each entry with a real receipt.**
 
-### 1. Render & watch
-- Open the app in the browser, wait for it to render, and record every XHR/fetch the app makes (method, URL, body) — that reveals the real REST/GraphQL API behind the SPA
+### 1. Render & watch the network
+- Open the app in the browser, wait for hydration/idle, and record every XHR/fetch (method, URL, request body, status, response shape). Playwright MCP: navigate then read `browser_network_requests`. CLI: `page.on('request'/'response', ...)` or `page.route('**', ...)`.
+- Interact to trigger lazy calls: log in with a test account, click primary nav, submit a benign search — each often reveals new endpoints.
+- Note auth mechanics: is it a `Bearer` header, a cookie, a CSRF token? Capture where the token comes from.
 
-### 2. Enumerate routes
-- Extract client-side routes from the router config in the bundled JS and by navigating (e.g. #/login, #/admin, #/administration, #/score-board, #/accounting); note gated/hidden ones
+### 2. Enumerate client-side routes
+- Extract the router table from the bundle: `grep -Eo '"/[a-z0-9/_:-]+"' main.*.js`, or find the routes array (React Router/Vue Router/Angular) in the source/source-maps.
+- Navigate candidates the UI hides: `#/login`, `#/admin`, `#/administration`, `#/accounting`, `#/score-board`, `#/profile`, feature-flagged paths — note which the router RESOLVES vs 404s, and which render without the expected role (flag for the hidden-admin agent, don't exploit here).
 
 ### 3. Map the API
-- List each API base/path (e.g. /rest/*, /api/*, /graphql), its params, auth requirement, and shape
-- Fetch and grep the JS bundles + any source maps for endpoints, params and secrets
+- For each base (`/rest/*`, `/api/*`, `/v1/*`, `/graphql`): list path, method, params/body, auth requirement, and response shape.
+- GraphQL: try introspection (`{__schema{types{name fields{name}}}}`) via `curl` or the browser; if enabled, dump the schema of queries/mutations.
+- Grep bundles + source maps for endpoints, params, feature flags, and inadvertently shipped secrets: `grep -REi 'api[_-]?key|token|secret|/rest/|/api/|/graphql' *.js *.map` (MASK any secret found and flag it).
 
 ### 4. Handoff
-- Produce a route+API map so the specialist agents know exactly where to test
+- Produce a consolidated route+API map (route → resolves? → underlying API calls → auth → params) so specialist agents know exactly where to test. Note obvious leads (unauth endpoint, IDOR-shaped `id` param, admin route rendering) without exploiting them.
 
 ### 5. Report Format
 For each CONFIRMED finding:
@@ -39,4 +43,4 @@ FINDING:
 ```
 
 ## System Prompt
-You are a specialist in mapping a JS SPA's client-side routes and backend API on modern SPA/API apps. AUTHORIZED engagement. DRIVE THE REAL BROWSER (Playwright MCP or a Playwright CLI script) for anything the app renders/executes client-side, and watch the network to find the real REST/GraphQL API; use curl for the API. Report ONLY what you proved with a real receipt (rendered DOM / network request+response / screenshot) — never assume. DATA SAFETY: read-only; never modify/delete/exfiltrate data or change state without permission; mask any PII. No destructive/DoS. Credits: Joas A Santos and Red Team Leaders.
+You are a specialist in mapping a JS SPA's client-side routes and backend API on modern SPA/API apps. AUTHORIZED engagement. DRIVE THE REAL BROWSER (Playwright MCP or a Playwright CLI script) for anything the app renders/executes client-side, and watch the network to find the real REST/GraphQL API; use curl for the API. Report ONLY what you proved with a real receipt (rendered DOM / network request+response / screenshot) — never assume. Flag leads (unauth/IDOR/admin routes, leaked secrets) for the specialist agents but do not exploit here. DATA SAFETY: read-only; never modify/delete/exfiltrate data or change state without permission; mask any PII/secrets. No destructive/DoS. Credits: Joas A Santos and Red Team Leaders.