docs(oracle): correct experiments.mdx paths + add oracle-deployed.mdx

[mangrove-one]

Summary

Closes the doc-drift half of MangroveAI gh #576 (issues #1, #2, #4). The KB was claiming Oracle endpoints that don't exist at the documented paths, leaving customers staring at SPA index.html responses (issues #1 and #2) or expecting a strategy-ranking response that's actually a persona roster (#4).

Changes

docs/api-reference/experiments.mdx — endpoint table corrections:

• POST /api/v1/oracle/simulate → POST /api/v1/oracle/simulate/run (plus new rows for /simulate/generate, /simulate/presets, /simulate/history)
• GET /api/v1/oracle/exec-config → GET /api/v1/oracle/exec-config/defaults
• GET /api/v1/oracle/leaderboard description reworded: "Curated persona roster — wrappers for the deployed strategies on the public dashboard. See Deployed strategies for live execution state."
• GET /api/v1/oracle/results annotated to clarify experiment_id is optional (cross-experiment view when omitted).
• New row for GET /api/v1/oracle/deployed/strategies linking to the new page.
• "Related" section updated to point to the new deployed page and to mention SDK v1.4.0 coverage.

docs/api-reference/oracle-deployed.mdx (NEW) — ~60-line page covering:

• GET /oracle/deployed/strategies (list with live state)
• GET /oracle/deployed/{id}/state (per-strategy execution snapshot)
• GET /oracle/deployed/{id}/events (recent trade history)
• GET /oracle/deployed/stream (SSE)
• Curl + SDK example per route.
• A "why leaderboard returns personas, not strategies" section so customers don't fall into the same trap.

docs/mint.json — insert \"api-reference/oracle-deployed\" after experiments (Oracle endpoints group together).

Test plan

• python -m json.tool docs/mint.json → valid JSON
• `npx mintlify dev` → render check
• Post-merge: cut v1.0.6 tag via release workflow

Sibling PRs closing the rest of #576

• MangroveOracle PR #237 — BQ ORDER BY fix (issue Audit all signals, indicators, and pattern detectors against reference implementations #3)
• MangroveAI PR #580 — proxy allowlist for /oracle/deployed/*
• MangroveAI-SDK PR #14 — 9 new typed methods + live example

🤖 Generated with Claude Code

[mangrove-one]

Ship instructions — step 5 of 6

Status: CI green (test 3.10/3.11/3.12 + CodeQL all pass), MERGEABLE, blocked only on review approval.

Safe to merge any time independently — the SDK v1.4.0 references in the doc will become accurate once SDK PR #14 ships, but a customer reading the doc today against SDK v1.3.0 won't be misled because the new method calls are wrapped in code blocks that reference the upcoming version explicitly.

After clicking merge:

# KB uses the workflow per memory feedback_kb_release_must_use_workflow — never manual tag.
gh workflow run release.yml --repo MangroveTechnologies/MangroveKnowledgeBase --ref main -f version=v1.0.6

The release workflow:

1. Publishes mangrove-kb to PyPI.
2. Builds the Mintlify docs container.
3. Deploys to mangrove-docs-prod (= docs.mangrovedeveloper.ai).

Verify the new page is live:

curl -sS https://docs.mangrovedeveloper.ai/api-reference/oracle-deployed | head -3
# Expect MDX content, not 404.

Next: mangrove-agent #82 (pin bump after SDK v1.4.0 hits PyPI).