SciDEX — Task: [UI] Fix /experiments 500 error and /hypotheses 40

The /experiments page returns 500 Internal Server Error and /hypotheses returns 404. Both are linked from the homepage and are critical demo pages. Previous fix attempt (445f3420) did not resolve. ## 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)

Squash merge: orchestra/task/fa8fe4d7-experiments-500-error-and-hypotheses-404 (1 commits)2026-04-15

Spec File

[UI] Fix /experiments 500 error and /hypotheses 404

ID: fa8fe4d7-598 Priority: 92 Type: one_shot Status: open

Goal

The /experiments page returns 500 Internal Server Error and /hypotheses returns 404. Both are linked from the homepage and are critical demo pages. Previous fix attempt (445f3420) did not resolve.

Acceptance Criteria

☐ Concrete deliverables created

☐ Work log updated with timestamped entry

Work Log

2026-04-15 22:10 PT — Slot 0

Investigated /experiments (500) and /hypotheses (404) errors
Confirmed routes exist in api.py at lines 27238 (/hypotheses) and 30683 (/experiments)
Both route handlers are properly registered with correct @app decorators
DB queries verified: experiments table exists (6 rows), hypotheses table exists (527 rows)
Tested via curl against live server: /hypotheses → HTTP 200, /experiments → HTTP 200
Both pages render correctly with live search, filtering, and pagination
Root cause: prior task 43ed964ef already fixed these issues on main
No code changes needed — pages already functional
Result: Done — /experiments and /hypotheses both return HTTP 200 and render correctly

Payload JSON

{
  "requirements": {
    "coding": 8,
    "safety": 8
  }
}

Sibling Tasks in Quest (UI) ↗

○[UI] Orphan work detection and linking systemP80

○[UI] CI: Verify all main pages render without errorsP80

○[UI] CI: Site-wide link and render health checkP80

○[UI] Build documentation system and evolve SciDEX knowledge baseP42

✓[UI] Fix hypothesis detail pages timing out — critical demo blockerP99

✓[UI] Fix SQLite connection leaks causing API hangsP99

✓[UI] Fix NameError in hypothesis page: undefined _get_cached_pageP99

✓[UI] Fix hypothesis page timeout - critical demo blockerP99

✓[UI] Fix 500 errors on /notebooks and /atlas pagesP99

✓[UI] Fix hypothesis/analysis wiki link timeout — reapply SUBSTR join fixP98