SciDEX — Task: [UI] Fix /atlas 500 error

## 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.

Completion Notes

Auto-completed by supervisor after successful deploy to main

Git Commits (1)

[Atlas] Close fe943db4: /atlas 500 _cache_page NameError already fixed on main via 50f38aa71 [task:fe943db4-2d3d-4364-b083-3f1da78f9c55]2026-04-13

Spec File

Goal

Fix the /atlas page 500 error caused by a NameError: name '_cache_page' is not defined.

Acceptance Criteria

☑ /atlas page loads without 500 error

Obsolescence Analysis

Root cause: _cache_page("atlas", page) was called but the function doesn't exist — should be _set_cached_page + return.

Already fixed on main: This was resolved by commit 50f38aa71 ("[UI] Fix /atlas 500 error and optimize performance [task:840112c6-224d-468b-b4a3-8d7446ea7793]") which:

Added _get_cached_page("atlas") check at line 48272

Changed return _cache_page("atlas", page) → _set_cached_page("atlas", page) + return page

Added DB indexes for knowledge_edges(edge_type) and knowledge_edges(created_at)

Verification: curl http://localhost:8000/atlas → HTTP 200 ✓

Spec file on main: docs/planning/specs/840112c6_224_spec.md documents this fix.

Work Log

2026-04-13 23:52 PT — Slot 54

Investigated task: found _cache_page NameError fix already on main via 50f38aa71
Verified /atlas returns HTTP 200 (live service)
Checked origin/main — line 48272 has _get_cached_page("atlas") check and line 48491 has _set_cached_page("atlas", page)
No code changes needed — task is already resolved
Closing as "already addressed by 50f38aa71: _cache_page→_set_cached_page fix landed on main 2026-04-02"

Payload JSON

{
  "requirements": {
    "coding": 8,
    "safety": 8
  },
  "completion_shas": [
    "c1f8945cd177a70ed43fef5265557f56d4ee600c"
  ],
  "completion_shas_checked_at": "2026-04-13T23:55:54.785463+00:00"
}