Why: #2090 added delete for models and aliases on /settings/models. The API refuses only a missing alias, so deleting the default model or an alias a saved workflow still names succeeds, and those workflows fail at run time. The confirmation dialog only warns about it.
Plan: the delete is refused while any saved workflow names the alias, with the error naming those workflows. The governance module asks the runs module through its API package; no cross-module table access. Deleting the default model is refused while any workflow relies on it.
Done when: deleting an alias in use returns a conflict naming the workflows, the dashboard shows that error inline, and deleting an unused alias still succeeds.
**Why**: #2090 added delete for models and aliases on /settings/models. The API refuses only a missing alias, so deleting the default model or an alias a saved workflow still names succeeds, and those workflows fail at run time. The confirmation dialog only warns about it.
**Plan**: the delete is refused while any saved workflow names the alias, with the error naming those workflows. The governance module asks the runs module through its API package; no cross-module table access. Deleting the default model is refused while any workflow relies on it.
**Done when**: deleting an alias in use returns a conflict naming the workflows, the dashboard shows that error inline, and deleting an unused alias still succeeds.
sam
added the lowbug labels 2026-11-21 15:04:47 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Why: #2090 added delete for models and aliases on /settings/models. The API refuses only a missing alias, so deleting the default model or an alias a saved workflow still names succeeds, and those workflows fail at run time. The confirmation dialog only warns about it.
Plan: the delete is refused while any saved workflow names the alias, with the error naming those workflows. The governance module asks the runs module through its API package; no cross-module table access. Deleting the default model is refused while any workflow relies on it.
Done when: deleting an alias in use returns a conflict naming the workflows, the dashboard shows that error inline, and deleting an unused alias still succeeds.