docs: refresh against v1.41.25 ground truth (2026-06-20)

[alias8818]

Summary

Full Mintlify docs refresh against the current source-repo ground truth. Every page in enoch-docs was cross-checked against the system repo (enoch-agentic-research-system, v1.41.25, 2026-06-20), the corpus repo (enoch-ai-research-corpus), and the promising-signals repo (enoch-promising-signals). 12 files changed, +96 / -12.

What changed

Source-grounded fixes (committed)

• release-notes.mdx — Added <Info> pointing to canonical CHANGELOG.md and surfacing the actual current version (1.41.25, 2026-06-20). The old page listed only milestones through 0.3.0, while the system repo has 176 published entries. We keep the 0.1.0 / 0.2.0 / 0.3.0 entries because they introduced public terminology (ENOCH_CONFIG, control_api_bearer_token, .enoch/project_decision.json contract), but the canonical changelog is now the source of truth for version history.
• current-runtime-snapshot.mdx — Documented the Dashboard V2 cutover (/control/dashboard 307 → /control/dashboard-v2, merged 2026-05-21). Surfaces the private deploy alias enoch-core.exe.xyz as a non-public fact. Adds an operator-dashboard table.
• introduction.mdx — Corpus counts 388/388 → 389/389 (matches quality/packaging_provenance_report.json and quality/claim_evidence_audit.json). Adds a <Note> that both JSON files are the source of truth and that counts must be re-verified before external quoting.
• quickstart.mdx — Dashboard URL → /control/dashboard-v2. Added a <Note> that the source repo's docs/quickstart.md uses 32-byte tokens while this page (and docs/deployment-guide.md) use 48-byte tokens; both are valid.
• deployment.mdx — Dashboard URL → /control/dashboard-v2.
• configuration/overview.mdx — Added operational_trace_* and hermes_alert_webhook_* field groups that exist in enoch_control_plane/config.py and config.example.json but were missing from the docs.
• reference/api-endpoints.mdx — Added /control/dashboard-v2 to the unauthenticated dashboard shell paths list.
• index.mdx — Dashboard mention → Dashboard V2.
• docs-audit-notes.md — Appended a 2026-06-20 section cataloguing the drift and what remains open.

Screenshot redaction — public-repo safety (placeholders committed; replacements still pending)

All five PNGs in images/ currently leak details that conflict with this repo's public-facing framing:

File	Issue
dashboard-status-blocked.png	Footer reads "Bounded Supabase read models · raw states stay in drill-down views". The docs publicly frame Supabase Cloud as a compatibility-only label for the local Postgres adapter, not an active runtime DB.
dashboard-active-queue.png	Same Supabase footer; internal counts that drift (9 attention, 0/0/0 running).
dashboard-queued-queue.png	Same Supabase footer.
dashboard-paper-reviews.png	Internal paper IDs and a "publication queue · 496 filtered · 496 total" line that no longer matches the current 389/389 corpus.
dashboard-papers.png	Internal paper paths and counts; same Supabase footer.

These images are still referenced from guides/dispatch-flow.mdx, guides/paper-artifacts.mdx, and reference/authorship-provenance.mdx. Each reference now has an explicit <Info> block noting the PNG is pending replacement with a redacted, public-safe capture (re-captured after the V2 cutover, with the "Supabase" footer removed or relabeled).

This PR does not replace the PNGs — replacing them requires re-running dashboard_v2_smoke.py against a public-safe view and exporting fresh captures. That work is tracked in docs-audit-notes.md under "What remains open" so a follow-up PR can land the actual image swaps.

Validation

• node scripts/validate-docs.mjs passes (22 MDX files, 21 docs.json navigation entries).
• All cross-page links still resolve.
• No new private hostnames, LAN IPs, or live credentials introduced.

Out of scope (per the original task)

This PR does not modify anything outside enoch-docs/. Source repos, scripts in /home/jeremy/Desktop/projects/enoch-release/, and parent-folder scratch files were read for fact-checking only.

Reviewer checklist

• Confirm the version-pointer approach on release-notes.mdx matches the team's preferred CHANGELOG mirroring policy.
• Confirm current-runtime-snapshot.mdx operator-dashboard table reads correctly on Mintlify render.
• Confirm screenshot-replacement placeholder language (<Info> block) is acceptable; if you'd rather we replace the PNGs in this PR, please flag and we'll generate redacted captures from a public-safe dashboard view.
• Spot-check configuration/overview.mdx JSON example for the new operational_trace_* block against the latest config.example.json from the system repo.
• Verify the introduction.mdx 389/389 counts against the canonical JSON files in the corpus repo before merging.

🤖 Generated with Claude Code

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated (UTC)
solo-09d10f60	🟢 Ready	View Preview	Jun 20, 2026, 12:09 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.