Triage the highest-signal recurring-engine failures in the SciDEX autonomous task fleet and turn real failures into concrete follow-up work. The outcome should distinguish transient rate limits from actionable code, DB, and task-shape problems so the recurring engine layer wastes fewer cycles.
last_error.tasks.last_error set is smaller than 20, extend the census with recent task_runs.last_error history and mark which failures are live-state vs run-history.rate_limit, code_error, db_error, or spec_mismatch.docs/planning/specs/quest-engine-ci.md - quest-engine recurring task behavior and target frequencydocs/planning/specs/senate_quest_engine_noop_fix_spec.md - existing sibling investigation for the quest-engine recurring driver9e45545a-0eeb-4698-9d79-ffda3f456b45 from the assigned worktree on current main commit 0f46acefa./home/ubuntu/Orchestra/AGENTS.md, repo AGENTS.md, docs/planning/specs/quest-engine-ci.md, docs/planning/specs/senate_quest_engine_noop_fix_spec.md, docs/planning/alignment-feedback-loops.md, docs/planning/artifact-governance.md, and docs/planning/landscape-gap-framework.md.2026-04-23T04:44:38Z, no attached spec existed, and live SciDEX recurring tasks still carry non-empty last_error values.tasks.last_error query described in the task now yields 10 live recurring tasks, so this triage extends the analysis with recent task_runs.last_error history to reach 20 concrete failure events while preserving the distinction between live-state failures and run-history failures.tasks.last_error on 2026-04-26)task_runs.last_error, newest-first, to reach 20 triaged failures)24c69375-1e0a-4b9d-a926-355a7fbdbff2 — [Senate] Fix recurring engine worktree acquisition failures77521747-85b5-4463-a04e-ccbe05424b77 — [Senate] Fix phantom-running recurring engine cleanup5caa79fb-399c-4c4a-bbe6-c1eb032617ec — [Exchange] Remove PostgreSQL-incompatible PRAGMA calls from recurring market enginesmax_gmail.Link validation sweep, Visual regression testing, and likely KG edge consistency) to batched work with a smaller per-cycle surface area before considering a longer lease.cli-requeue history as a health signal for recurrence quality. For Quest engine CI, Debate engine cycle, and DB health check, the meaningful fixes are the upstream worktree/phantom-run issues and the too-frequent no-op cadence already documented in sibling quest-engine specs.spec_path in Orchestra./home/ubuntu/Orchestra/orchestra.db and supplemented the census with recent task_runs.last_error history because only 10 live recurring tasks currently carry last_error.rate_limit, code_error, db_error, and spec_mismatch.24c69375-1e0a-4b9d-a926-355a7fbdbff2 for recurring worktree acquisition failures77521747-85b5-4463-a04e-ccbe05424b77 for phantom-running recurring tasks5caa79fb-399c-4c4a-bbe6-c1eb032617ec for PostgreSQL-incompatible PRAGMA usage in recurring market engines9e45545a-0eeb-4698-9d79-ffda3f456b45 was created 2026-04-23T04:44:38Z, still has no spec_path, and the recurring-failure query on /home/ubuntu/Orchestra/orchestra.db still returns 10 non-empty live last_error rows for SciDEX.task_runs ordering for recurring failures, with Quest engine CI dominating the recent error stream and multiple acquire_fail:worktree_creation_failed entries still visible.5caa79fb-399c-4c4a-bbe6-c1eb032617ec and 77521747-85b5-4463-a04e-ccbe05424b77 remain open for follow-up work, while 24c69375-1e0a-4b9d-a926-355a7fbdbff2 has already been completed by a later worker.