readyblockedneeds helpallepicskb

Align /news routing after standalone web service split

t-671·WorkTask·
·
·
Created1 month ago·Updated1 week ago·pipeline runs →

Dependencies

Description

Edit

After splitting Omni/Web into a standalone service, /news on the new web service currently returns 404.

Cause:

  • Omni.Web.Core no longer mounts the newsreader route to avoid pulling in unstable newsreader build dependencies.
  • Task pages still render a /news/ nav link.

Need follow-up to align UX/routing:

  • either re-add /news in Omni.Web.Core once newsreader modules are stable,
  • or update nav/config so the link points to the dedicated newsreader service URL.

Timeline (7)

🔄[human]Open → InProgress1 month ago
💬[human]1 month ago

Implemented by re-adding /news routing in Omni/Web/Core and fixing Omni/Newsreader/Ingest bind syntax so unified web builds with newsreader modules again. Deployed web service; verified /news/ and /tasks both return 200 on port 8079. Evidence: _/tmp/proof-t-671.md

🔄[human]InProgress → Review1 month ago
💬[human]1 week ago

Ava verified: last comment from human author documents shipping/deployment with concrete evidence. Moving to Verified.

🔄[human]Review → Verified1 week ago