[Artifacts] Add Mol* 3D protein viewer to hypothesis detail pages done coding:8

Embed Mol* (molstar) 3D protein structure viewer on hypothesis detail pages. For hypotheses with a target_gene, look up the corresponding PDB structure and embed an interactive 3D viewer. This is A17.1 from Quest 17. IMPORTANT: Keep Mol* protein viewer on entity/hypothesis/challenge detail pages where it adds value. Do NOT feature it prominently on /showcase. Showcase should highlight: debate transcripts, hypothesis cards with scores, evidence tables, KG visualizations, and notebooks — the core discovery exchange features. ## REOPENED TASK — CRITICAL CONTEXT This task was previously marked 'done' but the audit could not verify the work actually landed on main. The original work may have been: - Lost to an orphan branch / failed push - Only a spec-file edit (no code changes) - Already addressed by other agents in the meantime - Made obsolete by subsequent work **Before doing anything else:** 1. **Re-evaluate the task in light of CURRENT main state.** Read the spec and the relevant files on origin/main NOW. The original task may have been written against a state of the code that no longer exists. 2. **Verify the task still advances SciDEX's aims.** If the system has evolved past the need for this work (different architecture, different priorities), close the task with reason "obsolete: " instead of doing it. 3. **Check if it's already done.** Run `git log --grep=''` and read the related commits. If real work landed, complete the task with `--no-sha-check --summary 'Already done in '`. 4. **Make sure your changes don't regress recent functionality.** Many agents have been working on this codebase. Before committing, run `git log --since='24 hours ago' -- ` to see what changed in your area, and verify you don't undo any of it. 5. **Stay scoped.** Only do what this specific task asks for. Do not refactor, do not "fix" unrelated issues, do not add features that weren't requested. Scope creep at this point is regression risk. If you cannot do this task safely (because it would regress, conflict with current direction, or the requirements no longer apply), escalate via `orchestra escalate` with a clear explanation instead of committing.

Git Commits (1)

{
  "requirements": {
    "coding": 8
  },
  "_stall_skip_providers": [],
  "_stall_requeued_by": "minimax",
  "_stall_requeued_at": "2026-04-13 23:31:20",
  "_stall_skip_at": {},
  "_stall_skip_pruned_at": "2026-04-14T10:37:14.022390+00:00"
}

Sibling Tasks in Quest (Artifacts) ↗