better-dsh 0.2.5-c → 0.2.5-e

package/docs/80_upstream-docs-and-skills/hermes-dev-skill/src/docs/user-guide/skills/optional/software-development/software-development-pr-lens.md

@@ -1,160 +0,0 @@
----
-title: "Pr Lens — Draw code changes as animated architecture/data-flow SVGs"
-sidebar_label: "Pr Lens"
-description: "Draw code changes as animated architecture/data-flow SVGs"
----
-
-{/* This page is auto-generated from the skill's SKILL.md by website/scripts/generate-skill-docs.py. Edit the source SKILL.md, not this page. */}
-
-# Pr Lens
-
-Draw code changes as animated architecture/data-flow SVGs.
-
-## Skill metadata
-
-| | |
-|---|---|
-| Source | Optional — install with `hermes skills install official/software-development/pr-lens` |
-| Path | `optional-skills/software-development/pr-lens` |
-| Version | `1.0.0` |
-| Author | Coldtea AI (adapted by Nous Research) |
-| License | MIT |
-| Platforms | linux, macos |
-| Tags | `diagrams`, `pull-requests`, `code-review`, `svg` |
-
-## Reference: full SKILL.md
-
-:::info
-The following is the complete skill definition that Hermes loads when this skill is triggered. This is what the agent sees as instructions when the skill is active.
-:::
-
-# PR Lens Skill
-
-PR Lens draws code as visually rich animated diagrams: diffs, architecture, data flows. You describe the diff or codebase as one JSON document (lanes, nodes, edges, ordered flows) and the CLI renders it as animated SVGs. There is no findings lens — PR Lens is a comprehension layer, not a review bot. There is no field for a bug, risk, or security note, and a document that invents one is rejected.
-
-## When to Use
-
-- Asked to diagram, visualise, or explain a code change or a system.
-- A pull request should carry an architecture or data-flow diagram.
-- Keywords: PR Lens, diagram, architecture, data flow, visualise, pull request.
-
-## Prerequisites
-
-- Node.js with `npx` (the CLI runs via `npx @coldtea/pr-lens-cli@latest`; no install step).
-- `gh` (GitHub CLI) — optional, only for attaching diagrams to PRs.
-- Optional canvas publishing calls the third-party service prlens.dev (see step 4b).
-
-## How to Run
-
-Run all commands with the terminal tool from the repository root.
-
-1. **Read the diff.** When representing a code change: `git diff --find-renames <base>...<head>`. The base is the merge base, not the tip of the base branch. If not expressing a diff, read the code to be visualised.
-
-2. **Write the document** to `.pr-lens/graph.json`, following `references/graph-document.md`. `references/example.graph.json` is a valid reference with three lanes, all four delta states, a hero edge, a seven-step flow, a nested drill-down tree and a six-step walkthrough. Read it before writing your first document — quicker than reading the reference.
-
-3. **Validate, and fix.**
-
-   ```bash
-   npx @coldtea/pr-lens-cli@latest validate .pr-lens/graph.json
-   ```
-
-   Fix every failure and run it again. Do not render an invalid document; do not "work around" a failure by deleting the element it names.
-
-4. **Render.**
-
-   ```bash
-   npx @coldtea/pr-lens-cli@latest render .pr-lens/graph.json --theme light
-   ```
-
-   Render light by default unless the user requests another theme. The SVGs, the manifest and `drawn.graph.json` land in `.pr-lens/`, which the CLI adds to the repository's .gitignore. Do not commit any of it — these files are rebuilt from the diff on demand. Each SVG is named after its view, theme and content hash; `manifest.json` lists them by lens and view.
-
-4b. **Canvas push — OPTIONAL, opt-in.** Only when the user explicitly asks for a shareable link. This publishes `.pr-lens/drawn.graph.json` to the third-party service prlens.dev:
-
-   ```bash
-   npx @coldtea/pr-lens-cli@latest canvas push
-   ```
-
-   It prints three links. Give the user the **view link** (`https://prlens.dev/c/{id}`): the full-screen diagram, every view on one page, no login. The **edit link** (ending in `#w=…`) lets its holder overwrite the canvas — it is a secret: leave it out of the reply unless asked, never paste it anywhere public. The embed link serves the top view as an SVG for a README. Pushing the same file again updates the same canvas, so "rename that node" is: edit, validate, render, push — the link stays the same. If the push fails, say so and tell the user where the local SVGs are and which is the top view.
-
-5. **Attach to a PR, when there is one.** Upstream documents `gh pr create/edit/comment --attach <path>`, but `--attach` arrived in GitHub CLI 2.99 — check `gh --version` first (e.g. gh 2.97 does NOT have it). With gh ≥ 2.99: write the body with a Markdown image `![alt](https://github.com/NousResearch/hermes-agent/blob/main/optional-skills/software-development/pr-lens/.pr-lens/<view>.svg)` (an HTML `<img>` is left as written and the file appended at the bottom instead; alt text is the one-line caption a reader without images gets), then repeat `--attach <path>` per referenced diagram:
-
-   ```bash
-   gh pr create --title "…" --body-file .pr-lens/body.md --attach .pr-lens/overview-light-<hash>.svg
-   ```
-
-   Without `--attach`, use a commit-free path:
-   - Upload the SVGs to a gist: `gh gist create .pr-lens/<view>.svg`, then reference the raw gist URL in the PR body/comment, or
-   - Publish via the canvas link (step 4b, with user consent) and link the view URL, or
-   - Note the local `.pr-lens/` path in the PR body so reviewers can rebuild.
-
-   Once published somewhere durable, let the CLI compose the comment markdown:
-
-   ```bash
-   npx @coldtea/pr-lens-cli@latest comment \
-     --graph .pr-lens/drawn.graph.json \
-     --manifest .pr-lens/manifest.json \
-     --asset-base-url <where you published the SVGs>
-   ```
-
-   `--graph` takes `drawn.graph.json`, not the document you wrote — the CLI refuses a document its manifest does not describe. Leave out `--asset-base-url` and the markdown points at local paths no reader can fetch. The markdown goes to stdout; posting it is your business.
-
-   Attach the views a reviewer needs and leave the rest in `.pr-lens/`: the top architecture view first, then a data flow if the change has a sequence worth following. Two diagrams usually beat four.
-
-6. **Optional automation:** `npx @coldtea/pr-lens-cli@latest analyze --base <ref>` does steps 1–2 by asking a provider (Gemini, OpenAI, or any `/chat/completions` endpoint) with a key of your own. That is the only path here that needs one; normally you author the document yourself.
-
-## What makes a document worth reading
-
-- **Include what did not change.** Unchanged neighbours a change touches are the context; mark them `delta: "unchanged"`.
-- **Lanes are the reader's mental model** (a runtime, a tier, a boundary), not the folder tree.
-- **One hero edge**, two at the outside: the connection the change is really about.
-- **Add a flow only when there is a sequence** worth animating. One good flow beats three thin ones.
-- **Attach file refs**: they become the permalinks a reviewer clicks.
-- Architecture views are a C4-inspired decision tree: system context → container → component, each child materially narrower. Skip empty or repetitive levels; keep data-flow views as separate roots; set `defaultOpen: true` on the highest useful architecture view.
-- **Walkthroughs** (2–12 steps, aim 3–7): write one for anything non-trivial. Each step = one change (added/removed/moved), headline change first, overview last. Headings ≤48 chars built from change words; bodies ≤140 chars on behaviour, required. Write for a smart twelve-year-old; no "leverages"/"orchestrates". Keep consecutive steps on the same stage. The walkthrough field needs CLI ≥ 0.4.0 (contract 0.1.1).
-- **Fixing a wrong map:** never edit the generated document — write corrections into `.github/pr-lens.yml` (see `references/config.md`), then validate it: `npx @coldtea/pr-lens-cli@latest validate .github/pr-lens.yml`. Prefer path globs over `id:` matches.
-
-## Quick Reference
-
-| Command | Purpose |
-| --- | --- |
-| `npx @coldtea/pr-lens-cli@latest validate .pr-lens/graph.json` | validate the document (also validates `.github/pr-lens.yml`) |
-| `npx @coldtea/pr-lens-cli@latest render .pr-lens/graph.json --theme light` | render SVGs + manifest into `.pr-lens/` |
-| `npx @coldtea/pr-lens-cli@latest canvas push` | OPTIONAL: publish to prlens.dev (opt-in only) |
-| `npx @coldtea/pr-lens-cli@latest comment --graph … --manifest … --asset-base-url …` | compose PR comment markdown to stdout |
-| `npx @coldtea/pr-lens-cli@latest analyze --base <ref>` | auto-author document via an LLM provider (needs API key) |
-
-Validator failure codes:
-
-| Code | What you did |
-| --- | --- |
-| `BROKEN_REFERENCE` | an edge, flow step, view or walkthrough step names an id you never declared |
-| `INVALID_DOCUMENT` | an invented field; the schemas are strict, unknown keys are rejected |
-| `DUPLICATE_ID` | two nodes, edges or views sharing an id |
-| `UNSUPPORTED_SCHEMA_VERSION` | `schemaVersion` is not the contract version installed |
-
-## Pitfalls
-
-- Six rules are parser-only, not in the JSON Schema (referential integrity, inverted line ranges, disagreeing `self` endpoints, identical patch commits, too many views for a manifest, flow-step focus on the wrong stage) — always run `validate`, structured output alone is not enough.
-- Do not commit anything in `.pr-lens/`; it is regenerated and gitignored by the CLI.
-- The `--attach` gh flag needs gh ≥ 2.99; older gh silently lacks it — check before writing a body around it.
-- The canvas edit link (`#w=…`) is a write credential — never share it unprompted or paste it publicly.
-- A stored map never carries a walkthrough; a walkthrough tells the story of one change.
-- `pr-lens render` reports corrections in `.github/pr-lens.yml` that matched nothing — that is drift worth fixing, not an error.
-
-## Verification
-
-Smoke test (live-verified 2026-09-12 with `@coldtea/pr-lens-cli` via npx, node on Linux):
-
-```bash
-cp references/example.graph.json /tmp/prlens-smoke/ && cd /tmp/prlens-smoke
-npx -y @coldtea/pr-lens-cli@latest validate example.graph.json
-# ✓ example.graph.json — graph document · 3 lanes, 10 nodes, 13 edges, 1 flow · 6 walkthrough steps
-npx -y @coldtea/pr-lens-cli@latest render example.graph.json --theme light
-# ✓ .pr-lens/manifest.json — 4 SVGs across 4 diagrams
-```
-
-Expect exit 0 on both and four `*-light-<hash>.svg` files plus `manifest.json` and `drawn.graph.json` in `.pr-lens/`.
-
----
-
-Adapted from [coldteadotai/pr-lens](https://github.com/coldteadotai/pr-lens) (packages/agent-skill, pinned 0993b4d), MIT License, Copyright (c) 2026 Coldtea AI. See LICENSE.txt.

package/docs/80_upstream-docs-and-skills/hermes-dev-skill/src/docs/user-guide/skills/optional/software-development/software-development-rest-graphql-debug.md

@@ -1,532 +0,0 @@
----
-title: "Rest Graphql Debug — Debug REST/GraphQL APIs: status codes, auth, schemas, repro"
-sidebar_label: "Rest Graphql Debug"
-description: "Debug REST/GraphQL APIs: status codes, auth, schemas, repro"
----
-
-{/* This page is auto-generated from the skill's SKILL.md by website/scripts/generate-skill-docs.py. Edit the source SKILL.md, not this page. */}
-
-# Rest Graphql Debug
-
-Debug REST/GraphQL APIs: status codes, auth, schemas, repro.
-
-## Skill metadata
-
-| | |
-|---|---|
-| Source | Optional — install with `hermes skills install official/software-development/rest-graphql-debug` |
-| Path | `optional-skills/software-development\rest-graphql-debug` |
-| Version | `1.2.0` |
-| Author | eren-karakus0 |
-| License | MIT |
-| Platforms | linux, macos, windows |
-| Tags | `api`, `rest`, `graphql`, `http`, `debugging`, `testing`, `curl`, `integration` |
-| Related skills | [`systematic-debugging`](/docs/user-guide/skills/bundled/software-development/software-development-systematic-debugging), [`test-driven-development`](/docs/user-guide/skills/bundled/software-development/software-development-test-driven-development) |
-
-## Reference: full SKILL.md
-
-:::info
-The following is the complete skill definition that Hermes loads when this skill is triggered. This is what the agent sees as instructions when the skill is active.
-:::
-
-# API Testing & Debugging
-
-Drive REST and GraphQL diagnosis through Hermes tools — `terminal` for `curl`, `execute_code` for Python `requests`, `web_extract` for vendor docs. Isolate the failing layer before guessing at the fix.
-
-## When to Use
-
-- API returns unexpected status or body
-- Auth fails (401/403 after token refresh, OAuth, API key)
-- Works in Postman but fails in code
-- Webhook / callback integration debugging
-- Building or reviewing API integration tests
-- Rate limiting or pagination issues
-
-Skip for UI rendering, DB query tuning, or DNS/firewall infra (escalate).
-
-## Core Principle
-
-**Isolate the layer, then fix.** A 200 OK can hide broken data. A 500 can mask a one-character auth typo. Walk the chain in order; never skip a step.
-
-```
-1. Connectivity   → can we reach the host at all?
-1.5 Timeouts      → connect-slow vs read-slow?
-2. TLS/SSL        → cert valid and trusted?
-3. Auth           → credentials correct and unexpired?
-4. Request format → payload shape match server expectations?
-5. Response parse → does our code accept what came back?
-6. Semantics      → does the data mean what we assume?
-```
-
-## 5-Minute Quickstart
-
-### REST via terminal
-
-```python
-# Verbose request/response exchange
-terminal('curl -v https://api.example.com/users/1')
-
-# POST with JSON
-terminal("""curl -X POST https://api.example.com/users \\
-  -H 'Content-Type: application/json' \\
-  -H "Authorization: Bearer $TOKEN" \\
-  -d '{"name":"test","email":"test@example.com"}'""")
-
-# Headers only
-terminal('curl -sI https://api.example.com/health')
-
-# Pretty-print JSON
-terminal('curl -s https://api.example.com/users | python -m json.tool')
-```
-
-### GraphQL via terminal
-
-```python
-terminal("""curl -X POST https://api.example.com/graphql \\
-  -H 'Content-Type: application/json' \\
-  -H "Authorization: Bearer $TOKEN" \\
-  -d '{"query":"{ user(id: 1) { name email } }"}'""")
-```
-
-**GraphQL gotcha:** servers often return HTTP 200 even when the query failed. Always inspect the `errors` field regardless of status code:
-
-```python
-execute_code('''
-import os, requests
-resp = requests.post(
-    "https://api.example.com/graphql",
-    json={"query": "{ user(id: 1) { name email } }"},
-    headers={"Authorization": f"Bearer {os.environ['TOKEN']}"},
-    timeout=10,
-)
-data = resp.json()
-if data.get("errors"):
-    for err in data["errors"]:
-        print(f"GraphQL error: {err['message']} (path: {err.get('path')})")
-print(data.get("data"))
-''')
-```
-
-### Python (requests) via execute_code
-
-```python
-execute_code('''
-import requests
-resp = requests.get(
-    "https://api.example.com/users/1",
-    headers={"Authorization": "Bearer <TOKEN>"},
-    timeout=(3.05, 30),  # (connect, read)
-)
-print(resp.status_code, dict(resp.headers))
-print(resp.text[:500])
-''')
-```
-
-## Layered Debug Flow
-
-### Step 1 — Connectivity
-
-```python
-terminal('nslookup api.example.com')
-terminal('curl -v --connect-timeout 5 https://api.example.com/health')
-```
-
-Failures: DNS not resolving, firewall, VPN required, proxy missing.
-
-### Step 1.5 — Timeouts
-
-Distinguish *can't reach* from *reaches but slow*:
-
-```python
-terminal('''curl -w "dns:%{time_namelookup}s connect:%{time_connect}s tls:%{time_appconnect}s ttfb:%{time_starttransfer}s total:%{time_total}s\\n" \\
-  -o /dev/null -s https://api.example.com/endpoint''')
-```
-
-In Python, always pass a tuple timeout — `requests` has no default and will hang forever:
-
-```python
-execute_code('''
-import requests
-from requests.exceptions import ConnectTimeout, ReadTimeout
-try:
-    requests.get(url, timeout=(3.05, 30))
-except ConnectTimeout:
-    print("Cannot reach host — DNS, firewall, VPN")
-except ReadTimeout:
-    print("Connected but server is slow")
-''')
-```
-
-Diagnosis: high `time_connect` is network/firewall; high `time_starttransfer` with low `time_connect` is a slow server.
-
-### Step 2 — TLS/SSL
-
-```python
-terminal('curl -vI https://api.example.com 2>&1 | grep -E "SSL|subject|expire|issuer"')
-```
-
-Failures: expired cert, self-signed, hostname mismatch, missing CA bundle. Use `-k` only for ad-hoc debug, never in code.
-
-### Step 3 — Authentication
-
-```python
-# Token validity check
-terminal('curl -s -o /dev/null -w "%{http_code}\\n" -H "Authorization: Bearer $TOKEN" https://api.example.com/me')
-
-# Decode JWT exp claim — handles base64url padding correctly
-execute_code('''
-import json, base64, os
-tok = os.environ["TOKEN"]
-payload = tok.split(".")[1]
-payload += "=" * (-len(payload) % 4)
-print(json.dumps(json.loads(base64.urlsafe_b64decode(payload)), indent=2))
-''')
-```
-
-Checklist:
-- Token expired? (`exp` claim in JWT)
-- Right scheme? Bearer vs Basic vs Token vs `X-Api-Key`
-- Right environment? Staging key on prod is a classic
-- API key in header vs query param (`?api_key=…`)?
-
-### Step 4 — Request Format
-
-```python
-terminal("""curl -v -X POST https://api.example.com/endpoint \\
-  -H 'Content-Type: application/json' \\
-  -d '{"key":"value"}' 2>&1""")
-```
-
-**Content-Type / body mismatch — the silent 415/400:**
-
-```python
-# WRONG — data= sends form-encoded, header lies
-requests.post(url, data='{"k":"v"}', headers={"Content-Type": "application/json"})
-
-# RIGHT — json= auto-sets header AND serializes
-requests.post(url, json={"k": "v"})
-
-# WRONG — Accept says XML, code calls .json()
-requests.get(url, headers={"Accept": "text/xml"})
-
-# RIGHT — let requests build multipart with boundary
-requests.post(url, files={"file": open("doc.pdf", "rb")})
-```
-
-Common: form-encoded vs JSON, missing required fields, wrong HTTP method, unencoded query params.
-
-### Step 5 — Response Parsing
-
-Always inspect content-type before calling `.json()`:
-
-```python
-execute_code('''
-import requests
-resp = requests.post(url, json=payload, timeout=10)
-print(f"status={resp.status_code}")
-print(f"headers={dict(resp.headers)}")
-ct = resp.headers.get("Content-Type", "")
-if "application/json" in ct:
-    print(resp.json())
-else:
-    print(f"unexpected content-type {ct!r}, body={resp.text[:500]!r}")
-''')
-```
-
-Failures: HTML error page where JSON expected, empty body, wrong charset.
-
-### Step 6 — Semantic Validation
-
-Parsed cleanly — but is the data *correct*?
-
-- Does `"status": "active"` mean what your code thinks?
-- ID in response matches the one requested?
-- Timestamps in expected timezone?
-- Pagination returning all results, or just page 1?
-
-## HTTP Status Playbook
-
-### 401 Unauthorized — credentials missing or invalid
-
-1. `Authorization` header actually present? (`curl -v` to confirm)
-2. Token correct and unexpired?
-3. Right auth scheme? (`Bearer` vs `Basic` vs `Token`)
-4. Some APIs use query param (`?api_key=…`) instead of header.
-
-### 403 Forbidden — authenticated but not authorized
-
-1. Token has the required scopes/permissions?
-2. Resource owned by a different account?
-3. IP allowlist blocking you?
-4. CORS in browser? (check `Access-Control-Allow-Origin`)
-
-### 404 Not Found — resource doesn't exist or URL is wrong
-
-1. Path correct? (trailing slash, typo, version prefix)
-2. Resource ID exists?
-3. Right API version (`/v1/` vs `/v2/`)?
-4. Right base URL (staging vs prod)?
-
-### 409 Conflict — state collision
-
-1. Resource already exists (duplicate create)?
-2. Stale `ETag` / `If-Match`?
-3. Concurrent modification by another process?
-
-### 422 Unprocessable Entity — valid JSON, invalid data
-
-The error body usually names the bad fields. Check:
-- Field types (string vs int, date format)
-- Required vs optional
-- Enum values inside the allowed set
-
-### 429 Too Many Requests — rate limited
-
-Check `Retry-After` and `X-RateLimit-*` headers. Exponential backoff:
-
-```python
-execute_code('''
-import time, requests
-
-def with_backoff(method, url, **kwargs):
-    for attempt in range(5):
-        resp = requests.request(method, url, **kwargs)
-        if resp.status_code != 429:
-            return resp
-        wait = int(resp.headers.get("Retry-After", 2 ** attempt))
-        time.sleep(wait)
-    return resp
-''')
-```
-
-### 5xx — server-side, usually not your fault
-
-- **500** — server bug. Capture correlation ID, file with provider.
-- **502** — upstream down. Backoff + retry.
-- **503** — overloaded / maintenance. Check status page.
-- **504** — upstream timeout. Reduce payload or raise timeout.
-
-For all 5xx: backoff with jitter, alert on persistence.
-
-## Pagination & Idempotency
-
-**Pagination.** Verify you're getting *all* results. Look for `next_cursor`, `next_page`, `total_count`. Two patterns:
-- Offset (`?limit=100&offset=200`) — simple, can skip items if data shifts.
-- Cursor (`?cursor=abc123`) — preferred for live or large datasets.
-
-**Idempotency.** For non-idempotent operations (POST), send `Idempotency-Key: <uuid>` so retries don't double-charge / double-create. Mandatory for payments and orders.
-
-## Contract Validation
-
-Catch schema drift before it hits production:
-
-```python
-execute_code('''
-import requests
-
-def validate_user(data: dict) -> list[str]:
-    errors = []
-    required = {"id": int, "email": str, "created_at": str}
-    for field, expected in required.items():
-        if field not in data:
-            errors.append(f"missing field: {field}")
-        elif not isinstance(data[field], expected):
-            errors.append(f"{field}: want {expected.__name__}, got {type(data[field]).__name__}")
-    return errors
-
-resp = requests.get(f"{BASE}/users/1", headers=HEADERS, timeout=10)
-issues = validate_user(resp.json())
-if issues:
-    print(f"contract violations: {issues}")
-''')
-```
-
-Run after API upgrades, when integrating new third parties, or in CI smoke tests.
-
-## Correlation IDs
-
-Always capture the provider's request ID — fastest path to vendor support:
-
-```python
-execute_code('''
-import requests
-resp = requests.post(url, json=payload, headers=headers, timeout=10)
-request_id = (
-    resp.headers.get("X-Request-Id")
-    or resp.headers.get("X-Trace-Id")
-    or resp.headers.get("CF-Ray")  # Cloudflare
-)
-if resp.status_code >= 400:
-    print(f"failed status={resp.status_code} req_id={request_id} ts={resp.headers.get('Date')}")
-''')
-```
-
-**Vendor bug-report template:**
-
-```
-Endpoint:    POST /api/v1/orders
-Request ID:  req_abc123xyz
-Timestamp:   2026-03-17T14:30:00Z
-Status:      500
-Expected:    201 with order object
-Actual:      500 {"error":"internal server error"}
-Repro:       curl -X POST … (auth: <REDACTED>)
-```
-
-## Regression Test Template
-
-Drop this into `tests/` and run via `terminal('pytest tests/test_api_smoke.py -v')`:
-
-```python
-import os, requests, pytest
-
-BASE_URL = os.environ.get("API_BASE_URL", "https://api.example.com")
-TOKEN    = os.environ.get("API_TOKEN", "")
-HEADERS  = {"Authorization": f"Bearer {TOKEN}"}
-
-class TestAPISmoke:
-    def test_health(self):
-        resp = requests.get(f"{BASE_URL}/health", timeout=5)
-        assert resp.status_code == 200
-
-    def test_list_users_returns_array(self):
-        resp = requests.get(f"{BASE_URL}/users", headers=HEADERS, timeout=10)
-        assert resp.status_code == 200
-        data = resp.json()
-        assert isinstance(data.get("data", data), list)
-
-    def test_get_user_required_fields(self):
-        resp = requests.get(f"{BASE_URL}/users/1", headers=HEADERS, timeout=10)
-        assert resp.status_code in (200, 404)
-        if resp.status_code == 200:
-            user = resp.json()
-            assert "id" in user and "email" in user
-
-    def test_invalid_auth_returns_401(self):
-        resp = requests.get(
-            f"{BASE_URL}/users",
-            headers={"Authorization": "Bearer invalid-token"},
-            timeout=10,
-        )
-        assert resp.status_code == 401
-```
-
-## Security
-
-### Token handling
-- Never log full tokens. Redact: `Bearer <REDACTED>`.
-- Never hardcode tokens in scripts. Read from env (`os.environ["API_TOKEN"]`) or `${HERMES_HOME:-~/.hermes}/.env`.
-- Rotate immediately if a token surfaces in logs, error messages, or git history.
-
-### Safe logging
-
-```python
-def redact_auth(headers: dict) -> dict:
-    sensitive = {"authorization", "x-api-key", "cookie", "set-cookie"}
-    return {k: ("<REDACTED>" if k.lower() in sensitive else v) for k, v in headers.items()}
-```
-
-### Leak checklist
-
-- [ ] **Credentials in URLs.** API keys in query strings end up in server logs, browser history, referrer headers — use headers.
-- [ ] **PII in error responses.** `404 on /users/123` shouldn't reveal whether the user exists (enumeration).
-- [ ] **Stack traces in prod.** 500s shouldn't leak file paths, framework versions.
-- [ ] **Internal hostnames/IPs.** `10.x.x.x`, `internal-api.corp.local` in error bodies.
-- [ ] **Tokens echoed back.** Some APIs include the auth token in error details. Verify they don't.
-- [ ] **Verbose `Server` / `X-Powered-By`.** Stack-info leaks. Note for security review.
-
-## Hermes Tool Patterns
-
-### terminal — for curl, dig, openssl
-
-```python
-terminal('curl -sI https://api.example.com')
-terminal('openssl s_client -connect api.example.com:443 -servername api.example.com </dev/null 2>/dev/null | openssl x509 -noout -dates')
-```
-
-### execute_code — for multi-step Python flows
-
-When debugging spans auth → fetch → paginate → validate, use `execute_code`. Variables persist for the script, results print to stdout, no risk of token spam in your context:
-
-```python
-execute_code('''
-import os, requests
-
-token = os.environ["API_TOKEN"]
-base  = "https://api.example.com"
-H     = {"Authorization": f"Bearer {token}"}
-
-# 1. auth
-me = requests.get(f"{base}/me", headers=H, timeout=10)
-print(f"auth {me.status_code}")
-
-# 2. paginate
-all_users, cursor = [], None
-while True:
-    params = {"cursor": cursor} if cursor else {}
-    r = requests.get(f"{base}/users", headers=H, params=params, timeout=10)
-    body = r.json()
-    all_users.extend(body["data"])
-    cursor = body.get("next_cursor")
-    if not cursor:
-        break
-print(f"users={len(all_users)}")
-''')
-```
-
-### web_extract — for vendor API docs
-
-Pull the spec for the endpoint you're debugging instead of guessing:
-
-```python
-web_extract(urls=["https://docs.example.com/api/v1/users"])
-```
-
-### delegate_task — for full CRUD test sweeps
-
-```python
-delegate_task(
-    goal="Test all CRUD endpoints for /api/v1/users",
-    context="""
-Follow the rest-graphql-debug skill (optional-skills/software-development/rest-graphql-debug).
-Base URL: https://api.example.com
-Auth: Bearer token from API_TOKEN env var.
-
-For each verb (POST, GET, PATCH, DELETE):
-  - happy path: assert status + response schema
-  - error cases: 400, 404, 422
-  - log a repro curl for any failure (redact tokens)
-
-Output: pass/fail per endpoint + correlation IDs for failures.
-""",
-    toolsets=["terminal", "file"],
-)
-```
-
-## Output Format
-
-When reporting findings:
-
-```
-## Finding
-Endpoint: POST /api/v1/users
-Status:   422 Unprocessable Entity
-Req ID:   req_abc123xyz
-
-## Repro
-curl -X POST https://api.example.com/api/v1/users \
-  -H 'Content-Type: application/json' \
-  -H 'Authorization: Bearer <REDACTED>' \
-  -d '{"name":"test"}'
-
-## Root Cause
-Missing required field `email`. Server validation rejects before processing.
-
-## Fix
--d '{"name":"test","email":"test@example.com"}'
-```
-
-## Related
-
-- `systematic-debugging` — once the failing API layer is isolated, root-cause your code
-- `test-driven-development` — write the regression test before shipping the fix