readyblockedneeds helpallepicskb

Expose Omni/Task/Web at baryllium/tasks

t-609·WorkTask·
·
·
Created2 days ago·Updated2 days ago

Description

Edit

Add deployment/routing so Omni/Task/Web is accessible at baryllium/tasks, similar to existing /news web app route.

Review This Task

Timeline (6)

🔄[human]Open → InProgress2 days ago
💬[human]2 days ago

Implemented by wiring Omni.Task.Web routes into Omni.Ava.Web on the existing 8079/funnel surface: API now composes TaskWeb.API with Ava control-plane API, so /tasks is served at baryllium via the existing Ava web endpoint. Also fixed build blocker discovered during integration: Omni/Task/Web/Components.hs had non-exhaustive Status pattern matches (missing ReviewInProgress + Integrating). Verified with typecheck.sh Omni/Ava/Web.hs, typecheck.sh Omni/Ava/Core.hs, typecheck.sh Omni/Task/Web/Components.hs, and bild Omni/Ava/Core.hs.

🔄[human]InProgress → Review2 days ago
💬[human]2 days ago

Committed as 735a0ea0 and deployed via Omni/Ide/push.sh Omni/Ava/Core.hs. Forced immediate reconciliation with 'sudo systemctl start deployer'. Verified endpoint is live: curl https://beryllium.oryx-ide.ts.net/tasks -> HTTP 200.