F1 audits: fragile + simplify batch (post-Barcelona)
Batch the remaining non-deadline-critical items from the two 2026-06-11 F1 audits (reports/f1-pipeline-audit/2026-06-11.md + 2026-06-11-engine.md). Not urgent for Barcelona; sch...
StateWaitingNext ActionWaiting: until 2026-06-15 f1 audit batchOwnerLuciRuntimeIdleAge1d ago
Last runtime ended unexpectedly.·profile claude_opus_1m_medium
Description
MC-5002
Batch the remaining non-deadline-critical items from the two 2026-06-11 F1 audits (reports/f1-pipeline-audit/2026-06-11.md + 2026-06-11-engine.md). Not urgent for Barcelona; schedule next week.
Scheduling:
- Deadline-aware prediction scheduling: read qualifying_utc/sprint_utc per race instead of the fixed 4-slot guard windows in f1-prediction-saturday (keep tests/test_sprint_winner.py::test_saturday_* gates passing)
Pipeline-audit fragile leftovers (items 9-20): WARP monitoring/reconnect, HTTP retries on external calls, fastest-lap deleted-laps handling, refresh_calendar cancelled-flag wipe, superbru module shadowing, rank-stats update path, Reddit heading mismatch, editorial wrong-race filter, zombie Node dashboard :3002, scheduler timeout inversion, orphaned JS test mutating live signals.
Engine-audit fragile leftovers (items 7-17): POLE_EXCLUDED permanent blacklist, quali/sprint results writer (post-quali branch dead), Polymarket score saturation, Opus output validation enforcement (hallucinated drivers/pole/FL), string-pos audit-trail zeroing, wet-probability percentage parsing, contradictory wet-mode prompt, per-day --resume session anchoring, team field validation, 09 vs 09b FP engine disagreement, circuit map coverage.
Simplify cluster (both audits): sprint-constructor triplication, DRIVERS_2026 duplication + 04_odds drift, Firecrawl client x3, dead 06_ai_review.py, dead superbru.py submit stub, dead odds input (0/6 lifetime), 05 bypassing shared signals loader, FP mapping x3, wet logic duplication.
Suggest splitting into 2-3 child scopes at pickup. Polish items stay parked in the reports.
Expected check-in: 2026-06-15.
Activity
waiting
INTERACTIVE
Luci is working...
Details —
Waiting
· Medium
· Luci
▼
SState
Waiting
Waiting: until 2026-06-15 f1 audit batch
PPeople
TTiming / Details▼
api (human)
F1 Predictor
1d ago
1d ago
!Next step
Last runtime failure: not urgent; scheduled for next week per ticket description, expected check-in 2026-06-15
Check the last comment for context, then mark this ticket ready.
Advanced / Operator evidence
RRouting owner
ROperator console
Last runtime ended unexpectedly.not urgent; scheduled for next week per ticket description, expected check-in 2026-06-15profile claude_opus_1m_mediumMC is visibility-only. Hermes Luci launches and gates work outside MC, then mirrors evidence/status here.
WWorkflow
Start Dev Review + QA ▾
Select phases to include:
Agents
Review Gates
Decision
WAT routing: choose an agent, review gate, or decision. Buttons use the live runtime when one is attached.
[visibility-only] Queued message recorded for Hermes Luci. MC did not claim the ticket or spawn a runtime.
luci-board-manager1d ago
Visibility-only scheduling note: this F1 audit batch explicitly says it is not urgent and should be scheduled next week (expected check-in 2026-06-15), so I am not spawning internal Kanban work tonight. Parked as controller-scheduled backlog until 2026-06-15 unless Elmar asks to accelerate it.