SVC-3: Dashboard CRUD UI for service config #752

New issue

Closed

opened 2026-05-02 17:26:49 +00:00 by claude-desktop · 0 comments

claude-desktop commented

2026-05-02 17:26:49 +00:00

Collaborator

As an operator, I want the Settings → Service tab to let me edit every field in service_config at scope='global' (falling back to scope='builtin' on reset), so that I can adjust deploy-time service infra (forge URL, container image, watchdogs, auth, node flows, penpot, MCP command) from the dashboard without editing service.json.

Acceptance criteria

Editor

Tab grouped by section: Forge / Container image / UI / MCP / Auth / Watchdogs / Node flows / Penpot / Routing.
Reset-to-builtin available per field — drops the scope='global' row and falls through to scope='builtin'.

Validation + safety

Confirm dialog on forgejo_url and container_image_default (destructive enough that an accidental save shouldn't go through silently).
Field-level validation surfaces the same errors as the JSON Schema for service.json today.

Tests

Smoke: edit container_image_default, restart, observe new agents use the new image.
Smoke: edit watchdogs.*, observe the watchdog cadence change without restart (where the watchdog supports hot reload).

Out of scope

Killing service.json from the repo altogether — SVC-4.
Audit log surfacing — already covered by AT-7's pattern (kind-agnostic UI).

References

Spec: specs/config-to-db.md § Story SVC-3.
Blocked by: SVC-1, SVC-2.

As an operator, I want the Settings → Service tab to let me edit every field in `service_config` at `scope='global'` (falling back to `scope='builtin'` on reset), so that I can adjust deploy-time service infra (forge URL, container image, watchdogs, auth, node flows, penpot, MCP command) from the dashboard without editing `service.json`. ## Acceptance criteria ### Editor - [ ] Tab grouped by section: **Forge** / **Container image** / **UI** / **MCP** / **Auth** / **Watchdogs** / **Node flows** / **Penpot** / **Routing**. - [ ] Reset-to-builtin available per field — drops the `scope='global'` row and falls through to `scope='builtin'`. ### Validation + safety - [ ] Confirm dialog on `forgejo_url` and `container_image_default` (destructive enough that an accidental save shouldn't go through silently). - [ ] Field-level validation surfaces the same errors as the JSON Schema for `service.json` today. ### Tests - [ ] Smoke: edit `container_image_default`, restart, observe new agents use the new image. - [ ] Smoke: edit `watchdogs.*`, observe the watchdog cadence change without restart (where the watchdog supports hot reload). ## Out of scope - Killing service.json from the repo altogether — SVC-4. - Audit log surfacing — already covered by AT-7's pattern (kind-agnostic UI). ## References - Spec: `specs/config-to-db.md` § Story SVC-3. - Blocked by: SVC-1, SVC-2.

claude-desktop added the

area:infra

type:user-story

labels

2026-05-02 17:28:59 +00:00

claude-desktop added this to the Config to DB milestone

2026-05-02 17:29:00 +00:00