SciDEX — Task: [Wiki] Fix 404 on individual wiki entity pages (ap

Wiki category pages (/wiki/genes, /wiki/all-pages) work but individual entity pages (/wiki/apoe, /wiki/trem2) return 404. These are critical for the demo — visitors click entity links from the wiki homepage and get errors. ## 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)

[Docs] Document da354aa6 task: wiki entity pages 404 fix already on main [task:da354aa6-f7e1-4e2f-b705-5a5e3fbb9b90]2026-04-13

Spec File

Goal

Fix 404 errors on individual wiki entity pages (/wiki/apoe, /wiki/trem2, etc.) while wiki category pages (/wiki/genes, /wiki/all-pages) work correctly.

Acceptance Criteria

☑ /wiki/apoe returns 200 (not 404)

☑ /wiki/trem2 returns 200 (not 404)

☑ Other entity pages like /wiki/proteins-apoe return 200

☑ Wiki category pages continue to work (/wiki/genes, /wiki/all-pages)

Approach

Issue already resolved on origin/main via task 22eb3b44-2093-496b-99fc-b88182f181f1:

Commit 64a228dfd added a compatibility VIEW wiki_entities that maps to wiki_pages
This fixed the root cause where wiki entity pages were stored in wiki_pages but wiki_entities was a separate table

Dependencies

None (resolved)

Dependents

None

Work Log

2026-04-13 — Verification

Fetched origin/main and confirmed worktree is up to date
Tested /wiki/apoe, /wiki/trem2, /wiki/genes, /wiki/all-pages — all return 200
Confirmed fix is already on main via commit 64a228dfd (task 22eb3b44)
Task da354aa6 was likely addressed contemporaneously with 22eb3b44 or the same fix resolved both
Issue: Already resolved on main, no additional code changes needed
Completing task with note that fix already landed on main

Payload JSON

{
  "requirements": {
    "coding": 7
  },
  "completion_shas": [
    "4b9fca2292baba63b23bc8c2fed468a037055441"
  ],
  "completion_shas_checked_at": "2026-04-14T03:14:49.988394+00:00"
}