Ctrl K
ComunidadGuías…

Ayuda y problemas de morning-signal

Pregunta a la comunidad o invita a KiBot con contexto del repositorio.

Publicar un problema

No publiques contraseñas, tokens ni claves privadas. HostingByte aplica una redacción básica de secretos evidentes antes de guardar el texto.

Problemas en HostingByte

Todavía no hay problemas publicados.

Issues abiertas upstream

#86 Evaluate per-segment forced generation for guaranteed political-pulse coverage · 1 comentarios#168 [P2] morning-signal-bakeoff fires 82 minutes before its news digest exists — the 'fails every Wednesday' folklore is a race, not a day · 0 comentarios#167 morning-signal init wizard constructs the Anthropic SDK directly — the CLI's own entry point bypasses the krepis router · 0 comentarios#165 oss_bakeoff.py candidates dispatch directly to OpenRouter, bypassing krepis router (I6367) — build a compliant candidate-registration path · 0 comentarios#134 Register morning-signal's LLM call sites — unregistered, so I1–I9 and DLP reconciliation do not apply to them · 0 comentarios#121 Verify multi-version Python (3.9-3.12) on self-hosted AL2023 runner before repointing test.yml · 0 comentarios#117 Add live validation for configured OpenRouter model IDs (llm/fallback_llm) — bad fallback_llm silently broken 3 days, lost the 7/15 AM episode · 0 comentarios#115 Same-day episode regen/correction is invisible to already-subscribed clients (GUID never changes) · 0 comentarios#113 Add script content-sanity gate before publish (defense-in-depth for the 2026-07-14 garbage-episode incident) · 0 comentarios#93 Wire auto-deploy-on-merge for the box checkout (git pull + optional service-relevant refresh) · 0 comentarios#89 CI: add a scheduled (cron) run so unpinned-dependency drift surfaces on main, not on unrelated PRs · 0 comentarios#60 Local/offline TTS engine (no AWS/GCP required) · 1 comentarios#61 Zero-cloud output backend (publish locally, no S3) · 0 comentarios