[Atlas/UI] open_question + proposal detail pages — render artifact_type=open_question and four proposal kinds with discussion + provenance tabs done

Quest: Open Questions as Ranked Artifacts (b307ad54-a95) + Continuous Proposal Generation (eb6ff576-9d5). The new artifact kinds have schema + API + auto-population, but no human-readable detail pages. Acceptance: - Route /artifact/ already exists; ensure it renders correctly for kinds: open_question, analysis_proposal, code_proposal, experiment_proposal, funding_proposal. - Per-kind layout: * open_question — question text, field tag, Elo rank within field, evidence summary, status, source link (wiki page or gap), pairwise tournament history, derived hypotheses + proposals. * analysis_proposal — analysis question, datasets, methods, expected outputs, target notebook, conversion link to spawned notebook. * code_proposal — feature summary, target files, proposed changes, est_loc, conversion link to spawned task. * experiment_proposal — aims, hypotheses, dataset deps, protocol summary, predictions, falsification criteria, est cost/duration. * funding_proposal — sections per NIH page limits, mechanism, budget, references to experiment_proposals as preliminary data. - Universal tabs on every artifact detail page: Overview / Discussion (artifact_comments thread) / Provenance (audit chain) / Versions / Links. - Spec: docs/planning/specs/artifact_detail_pages_kinds.md. Why now: shipped artifact kinds need first-class views. Without them the data is invisible to humans driving the system.

Git Commits (3)

Sibling Tasks in Quest (Open Questions as Ranked Artifacts) ↗