SN6 Validator Fixes Config Bug; Reports Proxy Issues

A validator corrected a misconfigured Chutes service link (MAIN → SIGNAL track) and confirmed Chutes API usage resumed. However, deeper infrastructure problems persist: RSS feeds and LLM endpoints (DeepSeek-V3.1, V3.2-Exp) are returning HTTP 503 errors across multiple validators, causing zero-bundle outputs and fallback predictions. The issue mirrors earlier reports and suggests backend sandbox proxy instability.

• •Validator UID 187 fixed Chutes service config; API usage now active
• •RSS/LLM endpoints returning 503; affects Phase 1 and Phase 3
• •Bundle size zero, predictions imputed across multiple validator runs
• •Recurring issue flagged May 1 (UID 194); backend stability unclear