Root cause: The /api/dedup/scan endpoint returns 405 Method Not Allowed, indicating it's defined as POST in api.py but being accessed via GET from the frontend. The route definition shows @app.post('/api/dedup/scan') but links are trying to access it as GET requests.
Fix strategy: In api.py, change @app.post('/api/dedup/scan') to @app.get('/api/dedup/scan') to match how it's being accessed from the frontend. Alternatively, update the frontend code to use POST requests if the endpoint requires POST data. Check the senate/artifact-governance page that links to this endpoint.
Affected links (1):
- /api/dedup/scan
## 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 (5)
[Verify] dedup scan GET fix already on main [task:fc114569-49e6-453c-a88d-e2f3c07b1779]2026-04-20
Merge remote-tracking branch 'origin/main' into orchestra/task/f5c124e6-d958-4962-a45b-cc798165a3052026-04-04
[UI] Update task work log for dedup endpoint fix [task:fc114569-49e6-453c-a88d-e2f3c07b1779]2026-04-04
[UI] Allow GET on dedup scan endpoint [task:fc114569-49e6-453c-a88d-e2f3c07b1779]2026-04-04
Spec File
Goal
Fix the /api/dedup/scan endpoint method mismatch so linked dashboard actions can invoke the scan successfully. The dedup governance UI links to this endpoint as browser navigation, but the route was POST-only and returned 405. This task aligns route behavior with actual usage while preserving dedup scan behavior.
Acceptance Criteria
☑ /api/dedup/scan is callable via GET without 405
☑ Existing dedup scan behavior still executes and returns JSON stats
☑ API syntax checks pass
☑ Relevant pages and API status still return healthy responses
Approach
Inspect route declaration and call sites for /api/dedup/scan.
Update api.py route method to match browser-linked usage.
Run syntax and endpoint verification checks.
Update work log and complete task.
Dependencies
None
Dependents
a9bbf4cf-0f86-4ed0-9c7b-0e951dc6393b — related dynamic page health checks rely on functional tooling endpoints
- curl http://localhost:8000/api/status returned valid JSON (analyses/hypotheses/edges counts). - Page checks returned healthy codes: 302 /, 200 /exchange, 200 /graph, 200 /analyses/, 200 /senate/artifact-governance. - scidex status shows API active and healthy.
Attempted in-process endpoint execution with TestClient; request reached dedup scan handler but failed due local worktree DB lacking hypotheses table, unrelated to HTTP method routing change.
2026-04-04 05:01 PDT — Slot 11
Committed and pushed from worktree:
- Commit: fe2194ec - Message: [UI] Allow GET on dedup scan endpoint [task:fc114569-49e6-453c-a88d-e2f3c07b1779]
Integrated to main and pushed via /home/ubuntu/Orchestra/scripts/push_main.sh (lock-safe merge path).
Restarted API service: sudo systemctl restart scidex-api.
Result: Done — dedup scan endpoint now supports browser-linked GET access while preserving POST compatibility.
2026-04-04 05:02 PDT — Slot 1
Independently validated in this worktree that OpenAPI exposes both methods for /api/dedup/scan: [get, post].
Confirmed intermittent API restarts during parallel integration activity; successful checks returned HTTP/1.1 200 OK for /api/status when service was active.
Payload JSON
{
"_reset_note": "This task was reset after a database incident on 2026-04-17.\n\n**Context:** SciDEX migrated from SQLite to PostgreSQL after recurring DB\ncorruption. Some work done during Apr 16-17 may have been lost.\n\n**Before starting work:**\n1. Check if the task's goal is ALREADY satisfied (run the relevant checks)\n2. Check `git log --all --grep=task:YOUR_TASK_ID` for prior commits\n3. If complete, verify and mark done. If partial, continue. If not done, proceed.\n\n**DB change:** SciDEX now uses PostgreSQL. `get_db()` auto-detects via\nSCIDEX_DB_BACKEND=postgres env var.",
"_reset_at": "2026-04-18T06:29:22.046013+00:00",
"_reset_from_status": "done"
}