Dashboard hand-copies two server vocabularies with no single source #1513

Closed
opened 2026-10-27 13:40:42 +00:00 by sam · 0 comments
Owner

ui/src/tasks/attempt-config.jsx CONFIG_SCHEMA mirrors internal/events ConfigCapturedSchema, and ui/src/tasks/changed-files.jsx FILE_STATUS mirrors the five Change* strings in internal/domain/workflow/task/changes.go. Each side is now pinned by its own literal-value test (added with the per-run task detail change), so a one-sided rename fails a test, but nothing derives one side from the other.

The repo states the opposite convention for exactly this problem in ui/src/base/task-meta.jsx: vocabularies are served by the server via /api/task-meta. That path is currently DEAD - loadTaskMeta is exported with no callers - so the dashboard always renders its hardcoded defaults and a server-side catalogue change never reaches the browser. Wiring these vocabularies through that endpoint would therefore first require reviving dead code, which is why per-side pins were chosen as the bounded fix instead.

Decision needed: either serve these vocabularies (and revive or delete loadTaskMeta), or accept hand-copied constants as the convention and remove the contradicting task-meta precedent. Doing neither leaves two competing stories in the tree.

Close reason

Closed on GitHub; syncing bead state


Imported from beads archie-core-phpx · GitHub #865 · type task · priority P2 · created 2026-09-18 · closed 2026-09-26

ui/src/tasks/attempt-config.jsx CONFIG_SCHEMA mirrors internal/events ConfigCapturedSchema, and ui/src/tasks/changed-files.jsx FILE_STATUS mirrors the five Change* strings in internal/domain/workflow/task/changes.go. Each side is now pinned by its own literal-value test (added with the per-run task detail change), so a one-sided rename fails a test, but nothing derives one side from the other. The repo states the opposite convention for exactly this problem in ui/src/base/task-meta.jsx: vocabularies are served by the server via /api/task-meta. That path is currently DEAD - loadTaskMeta is exported with no callers - so the dashboard always renders its hardcoded defaults and a server-side catalogue change never reaches the browser. Wiring these vocabularies through that endpoint would therefore first require reviving dead code, which is why per-side pins were chosen as the bounded fix instead. Decision needed: either serve these vocabularies (and revive or delete loadTaskMeta), or accept hand-copied constants as the convention and remove the contradicting task-meta precedent. Doing neither leaves two competing stories in the tree. ### Close reason Closed on GitHub; syncing bead state --- _Imported from beads `archie-core-phpx` · GitHub #865 · type task · priority P2 · created 2026-09-18 · closed 2026-09-26_
sam added the mediumtask labels 2026-10-27 13:40:42 +00:00
sam self-assigned this 2026-10-27 13:40:42 +00:00
sam closed this issue 2026-10-27 13:40:42 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Reference: sam/archie#1513