docs: align docs validation commands with CI and drop unshipped references

Address review feedback:

- AGENTS.md: replace the npm build shortcut with the actual CI docs job
  steps (npm ci, social-images, then hugo with --gc --minify --cacheDir)
- AGENTS.md: drop internal/history from the package map; that package
  does not exist yet
- rsh-docs: list the CI docs job commands in CI order in the validation
  section and keep the plain hugo build as the quick iteration check
- rsh-docs: remove the npm test guidance; site/package.json has no test
  script

Author: danielgtaylor

.agents/skills/rsh-docs/SKILL.md

@@ -235,21 +235,20 @@ When migrating older docs, track whether material was retired, already migrated,
 
 ## Validation
 
-After meaningful site changes, run what CI runs:
+After meaningful site changes, run what the CI docs job runs:
 
 ```bash
-hugo --source site --quiet          # site builds (quick check)
-npm --prefix site run build        # CI parity: social images + Hugo (npm ci once first)
-scripts/check-doc-examples.rb      # restish-example shortcodes are valid
-scripts/check-doc-links.rb         # internal links resolve
-go run ./cmd/restish-docgen --check # generated regions are not stale
+npm --prefix site ci                  # once, to install dependencies
+go run ./cmd/restish-docgen --check   # generated regions are not stale
+npm --prefix site run social-images   # social preview images build
+hugo --source site --quiet --gc --minify --cacheDir /tmp/hugo_cache
+scripts/check-doc-links.rb            # internal links resolve
+scripts/check-doc-examples.rb         # restish-example shortcodes are valid
 ```
 
+A plain `hugo --source site --quiet` is a fine quick check while iterating.
 `npm run social-images` parses front matter across `content/en` and can fail
-independently of Hugo, so run the npm build for blog and front-matter changes
-even when the quick Hugo check passes.
-
-When touching site JavaScript or interactive examples (playground, query
-runner, docs interactions), also run `npm --prefix site test`.
+independently of Hugo, so run it for blog and front-matter changes even when
+the quick Hugo check passes.
 
 Also verify new links, check examples against current CLI behavior, grep touched docs for stale `api.example.com` placeholders and leftover `Source material:` sections, and prefer examples that can later be validated against `api.rest.sh` or promoted into tests.

AGENTS.md

@@ -21,9 +21,11 @@ go run ./cmd/restish-docgen --check
 # Validate the docs site after changes under site/ (quick check)
 hugo --source site --quiet
 
-# Full CI parity for the docs job: social preview images + Hugo
-# (npm ci needed once; social-images parses content front matter and can fail independently)
-npm --prefix site ci && npm --prefix site run build
+# Full CI parity for the docs job (npm ci needed once; social-images parses
+# content front matter and can fail independently of Hugo)
+npm --prefix site ci
+npm --prefix site run social-images
+hugo --source site --quiet --gc --minify --cacheDir /tmp/hugo_cache
 
 # Validate docs examples and links (CI runs both)
 scripts/check-doc-examples.rb
@@ -72,7 +74,7 @@ The core design is a `CLI` struct in `internal/cli/cli.go` that owns all state 
 - `internal/auth`, `internal/secrets` — auth schemes; credential-recognition allow-lists
 - `internal/config` — config files, profiles, comment-preserving JSONC edits, file locking
 - `internal/content`, `internal/input`, `internal/filter`, `internal/hypermedia` — content negotiation, shorthand request bodies, shorthand/jq filtering, link parsing
-- `internal/cache`, `internal/history` — size-bounded disk cache; request history
+- `internal/cache` — size-bounded disk cache for specs and responses
 - `internal/plugin`, `internal/procutil` — plugin discovery/manifests; subprocess lifecycle
 - `plugin/` (top level) — public plugin API contract; wire compatibility is a public promise