Risk detail: references section (spec §7 leftover) — RiskReference is a dead model

[CST-100]

Issue #40 §7 lists the risk detail page contents as "… linked issues · narrative · references (parts, requirements)". PR #42 shipped everything else; the references element was deliberately deferred:

• RiskReference (OPAL/WO cross-references, src/opal/db/models/reference.py) has existed since the cross-references migration but has no API route, no web UI, and no MCP tool — it is currently a dead model (predates Development: Risks #40).
• The asset part link covers the "parts" half of §7 implicitly; requirement references have no mechanism at all.

Scope to decide: render + edit RiskReference on the detail page, or replace it with the generic reference pattern used elsewhere; and whether risk→requirement references deserve a first-class link table (the SE module side) rather than a stringly OPAL-number reference.

Related small follow-up, same page: the asset part <select> is capped at 200 parts ordered by name (PR #42 makes the currently-set part always render selected, but parts beyond the cap can't be chosen). The right fix is the parts search typeahead used on the issues form.

🤖 Generated with Claude Code