readyblockedneeds helpallepicskb

Pipeline: process only tasks tagged pipeline; add tag editing in task web UI

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

Description

Edit

Implement two changes: 1) Omni/Pipeline scheduler should only consider ready tasks that include the tag 'pipeline' (case-insensitive), while still respecting existing namespace and status checks. 2) Omni/Task/Web should expose task tags in the task detail UI with controls to add and remove tags (no CLI needed), and persist changes via TaskCore.

Acceptance:

  • untagged tasks are ignored by pipeline scheduler
  • tagged tasks continue normal scheduler flow
  • in task detail page, current tags are visible and user can add/remove tags
  • updates persist and re-render without full page reload where practical

Timeline (13)

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

Implemented: pipeline now requires tag 'pipeline' before scheduling; task web UI now supports add/remove tags on task detail page via HTMX endpoints. Verification artifact: _/tmp/proof-t-668.md

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

Deployed pipeline service via Omni/Ide/ship.sh Omni/Pipeline.hs. Deployer applied at 2026-02-20 15:30 EST and pipeline now runs /nix/store/2ga81sp602ah6h5fnvdc81yrr7vlhl5n-pipeline. Startup log shows tag gate active: open-tagged-with-namespace=0.

💬[human]1 month ago

Task Web tag UI changes are now live via standalone web.service at http://127.0.0.1:8081 (systemd service: web). Verified /tasks and task detail tag controls render there.

💬[human]1 month ago

Tag UI is now live on canonical web endpoint port 8079 after final web/ava cutover.

💬[human]1 week ago

Ava verified: implementation present in live tree (file/feature confirmed via inspection). Moving to Verified.

🔄[human]Review → Verified1 week ago