docs(site): content audit + refresh across all pages for 1.5.0 accuracy

[rlaope]

What

A content audit + refresh of the documentation site (design/structure unchanged — this is about what the pages say). Every page was audited against the actual code/docs via parallel review, and each finding was re-verified against source before editing.

Factual corrections (verified against source)

Page	Fix
reference.html	Module architecture 7 → 11 (adds argus-diagnostics, argus-aggregator, argus-operator, argus-instrument). Config table: argus.buffer.size=65536 (was argus.buffer-size=131072), argus.cpu.interval=1000 (was .interval-ms=500), argus.allocation.threshold=1048576 (was 524288); +12 missing knobs (server.enabled, profiling.interval, contention.threshold, correlation.enabled, otlp.*, metrics.legacyNames, anomaly.mode).
integrations.html	Spring YAML defaults fixed (65536/1000/1048576); add argus.mode; complete the actuator surface (argus-doctor, argus-gc, + mode=full-only health caveat); doctor.gc-log-path requirement; scheduling note; DoctorService.lastCollectionWarnings().
dashboard.html	argus.server.enabled default is true (was documented false); +missing config rows; note jdk.VirtualThreadSubmitFailed.
scenarios.html	S6 used argus classloader --top (no such flag) → argus classleak.
commands.html	ZGC --watch=N is iterations, not seconds.

Completeness

• commands.html: the "All 71 Commands" reference listed only ~24 — now covers all 71 across 8 categories, with the newer commands documented (rightsize, instrument, explain --llm, heapanalyze, gcscore, profile-gate, …).
• index.html: new capability cards — JVM right-sizing (FinOps), learned anomaly detection, OTel-native semconv metrics, opt-in LLM root-cause; corrected the virtual-thread card (JEP-491 taxonomy, structured-concurrency view, carrier-saturation argus doctor rule); broadened "two tools" → CLI/Agent/Spring starter/diagnostics library.
• comparison.html: framing broadened beyond GC; pool jdbc / pool advise surfaced.
• scenarios.html: argus rightsize added to the OOMKilled scenario, an argus instrument confirmation step to lock contention, and a new scenario 13 (virtual-thread carrier saturation) — a flagship 1.5 capability that previously had no scenario home.

Honesty / accuracy guards

• Opt-in features (LLM, instrument, learned anomaly) are labelled opt-in (honest-value-framing rule).
• A proposed Micrometer "legacyNames" note was dropped — that dual-emit lives in argus-server, not argus-micrometer; adding it would be a false claim.
• Verified: every argus <cmd> invocation resolves to a real command (caught + fixed one hallucinated argus vthread); v1.5.0 and 71 commands consistent across all pages; HTML tag balance OK on all 7 pages; the GitHub Pages assembly reproduces with assets resolving.

🤖 Generated with Claude Code