[exe-dev-github-integration]

Summary

• Port RSS/Atom ingestion, Jev event deduplication, and frozen feed-only news snapshots; no survey-update scoring or historical private data.
• Add recent-shadow-noairo to AIRO on Fridays, using the same ECI-selected panel, complete 73-question instrument, scenario set and harness. Unpublished/unpooled; existing condition hashes and published numbers are unchanged.
• Preserve the owner-approved prompt exactly. Cache is read through the existing read_page tool; reuse the existing no-AIRO instruction and URL guard.
• Set max_turns = 0 for the full shadow: no forced-turn submission cap. The old abbreviated probe remains a separate explicit manual script only.
• Add daily free RSS collection at 11:45 UTC and fresh preparation before the Friday shadow. Missing feeds/key or reduction failure skips only the shadow, alerts, and never falls back to old news.

Validation

• Full offline suite: 500 passed, 16 skipped, 856 subtests passed.
• redlines build + redlines assemble reproduce tracked frontend/data bytes.
• Friday dispatch lists the normal published group plus airo aside recent-shadow-noairo; Wednesday has no news shadow.
• No live panel or deployment run to validate this change.

Production handoff

See deploy/README.md, section "Friday recent-news shadow". Production must provision the private Jev key, grant RSS/Jev hosts, then deploy normally after merge/checks. State lives outside the release under the private runtime state directory. Initial RSS history is bounded; do not reuse the old experiment archive as current news. Deployment preserves the published forecast data snapshot.

The development checkout contains unrelated UI edits; they are deliberately excluded from this PR.

[exe-dev-github-integration]

Updated against current main (including the pi-only runner and production storage safeguards). Current local suite: 465 passed, 16 skipped, 856 subtests passed; build/assemble reproduce the tracked bytes. Required CI checks are all green on 108ae70. This package is prepared for production-cell deployment; no production activation or paid panel was performed here. Operator prerequisites and failure handling are in deploy/README.md.