DX-078: Write /concepts/risk

[IbrahimIjai]

Context

An honest enumeration of what can go wrong. The content map is explicit about
why this page exists: a risk page that only lists upside teaches readers not to
trust the rest of the documentation
(docs/dx_1/003_content_map.md §1).

Scope

• Market risk: leverage, liquidation, gap moves, funding costs over time.
• Protocol risk: smart contract bugs, upgrade authority, admin capabilities —
  state who can change what, verified against the contracts.
• Oracle risk: source failure, staleness, manipulation, and the consequences.
• Liquidity risk for LPs: adverse trader flow, exit conditions, withdrawal
  limits if any.
• Operational risk: RPC and indexer availability, front-end availability, and
  what a user can and cannot do if the interface is down.
• Audit status stated accurately, including if unaudited.

Acceptance criteria

• Admin and upgrade capabilities are verified against contract source, with
  file paths named in the PR.
• Audit status is accurate and unhedged.
• The "interface is down" section describes a real recovery path or says
  plainly that none exists.
• Reviewed by a maintainer before merge.

Out of scope

• Legal terms (DX-097).

---

Spec: docs/dx_1/003_content_map.md §3 · Depends on: DX-077

[Kappa16]

HI i can work on this issue FAST AND ACCURATE. expect PR IN LESS THAN 4HOURS