Extract + Drizzle `service_config` + `label_catalog` + `agent_type_*` aggregates #845

New issue

Closed

opened 2026-05-04 20:29:17 +00:00 by claude-desktop · 1 comment

claude-desktop commented

2026-05-04 20:29:17 +00:00

Collaborator

As a maintainer, I want the resolver hot-path tables (service_config, label_catalog, agent_type_config, agent_type_container, agent_type_routing, plugin/MCP/skill scope tables) split out and Drizzled, so that domain/agent-config/resolver.ts calls type-safe queries instead of raw SQL.

Acceptance criteria

Extraction

service-config-store.ts + label-catalog.ts + agent-type-config.ts (split by aggregate).
Functions moved: getSettings, patchSettingsDb, plus all getServiceConfig, resolveAgentTypeConfig, resolveAgentTypeContainer, resolveAgentTypeRouting, getLabelCatalogForRepo, resolvePlugins, resolveMarketplaces, resolveMcpServers, resolveSkill, getAgentType, getSpeechConfig etc. that currently sit in resolver.ts but talk SQL directly.
Callers updated.

Drizzle

Schema files per aggregate.
Add-only inheritance contract preserved (see docs/inheritance-contract.md).

Tests

Resolver tests green.
No raw SQL strings remain in domain/agent-config/resolver.ts for these tables (resolver becomes pure logic over typed queries).

Out of scope

Resolver business logic (scope ladder rules) — only data access layer rewritten.

References

apps/server/src/domain/agent-config/resolver.ts — current SQL hot path.
docs/inheritance-contract.md.
Foundation story (#839) must merge first.

**As a** maintainer, **I want** the resolver hot-path tables (`service_config`, `label_catalog`, `agent_type_config`, `agent_type_container`, `agent_type_routing`, plugin/MCP/skill scope tables) split out and Drizzled, **so that** `domain/agent-config/resolver.ts` calls type-safe queries instead of raw SQL. ## Acceptance criteria ### Extraction - [ ] `service-config-store.ts` + `label-catalog.ts` + `agent-type-config.ts` (split by aggregate). - [ ] Functions moved: `getSettings`, `patchSettingsDb`, plus all `getServiceConfig`, `resolveAgentTypeConfig`, `resolveAgentTypeContainer`, `resolveAgentTypeRouting`, `getLabelCatalogForRepo`, `resolvePlugins`, `resolveMarketplaces`, `resolveMcpServers`, `resolveSkill`, `getAgentType`, `getSpeechConfig` etc. that currently sit in `resolver.ts` but talk SQL directly. - [ ] Callers updated. ### Drizzle - [ ] Schema files per aggregate. - [ ] Add-only inheritance contract preserved (see `docs/inheritance-contract.md`). ### Tests - [ ] Resolver tests green. - [ ] No raw SQL strings remain in `domain/agent-config/resolver.ts` for these tables (resolver becomes pure logic over typed queries). ## Out of scope - Resolver business logic (scope ladder rules) — only data access layer rewritten. ## References - `apps/server/src/domain/agent-config/resolver.ts` — current SQL hot path. - `docs/inheritance-contract.md`. - Foundation story (#839) must merge first.

claude-desktop added the

area:database

type:user-story

labels

2026-05-04 20:30:08 +00:00

claude-desktop added this to the ORM migration (Drizzle) milestone

2026-05-04 20:30:17 +00:00

claude-desktop added a new dependency

2026-05-04 21:47:30 +00:00

#843 Extract + Drizzle flows aggregate (flows + runs + audit + legacy_forge_calls)

claude-desktop added a new dependency

2026-05-04 21:47:30 +00:00