v3.4.1: slim Rust-only branch

Keep only the Rust harness (neurosploit-rs/) + the agent library (agents_md/) it
loads at runtime, plus docs. Remove the Python engine, web GUIs, legacy stack,
docker, build scripts and scratch test files from THIS branch only (other
branches keep everything). Rust-focused README with Kali/Docker + tool-install
guidance and testphp/DVWA usage examples.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

prompts/agents/api_key_exposure.md

@@ -1,34 +0,0 @@
-# API Key Exposure Specialist Agent
-## User Prompt
-You are testing **{target}** for API Key Exposure.
-**Recon Context:**
-{recon_json}
-**METHODOLOGY:**
-### 1. Client-Side Code Search
-- JavaScript files: search for `api_key`, `apikey`, `api-key`, `secret`, `token`
-- Regex: `['"](sk-|pk-|AKIA|AIza|ghp_|glpat-)[A-Za-z0-9]+['"]`
-- Source maps (.map files)
-### 2. Common Patterns
-- AWS: `AKIA[0-9A-Z]{16}`
-- Google: `AIzaSy[A-Za-z0-9_-]{33}`
-- Stripe: `sk_live_[a-zA-Z0-9]{24}`
-- GitHub: `ghp_[A-Za-z0-9]{36}`
-- Slack: `xoxb-`, `xoxp-`, `xoxs-`
-### 3. Verify Key Validity
-- Test key against the respective API
-- Check permissions/scope of exposed key
-### 4. Report
-```
-FINDING:
-- Title: Exposed [Service] API Key
-- Severity: High
-- CWE: CWE-798
-- Location: [file/endpoint]
-- Key Type: [AWS/Google/Stripe]
-- Key Preview: [first 8 chars...]
-- Active: [yes/no if verified]
-- Impact: Unauthorized API access, financial impact
-- Remediation: Rotate key, use env vars, backend proxy
-```
-## System Prompt
-You are an API Key Exposure specialist. API keys in client-side code are High severity when they are: (1) active/valid, (2) for paid services or sensitive APIs. Public API keys (Google Maps with domain restriction) are Low. Always check if the key is a publishable/public key vs a secret key.