refactor: centralize provider registry for settings integrations #325

New issue

Closed

opened 2026-05-11 19:20:27 +00:00 by barrettruth · 0 comments

barrettruth commented

2026-05-11 19:20:27 +00:00

Owner

Parent: #305
Related: #290, #123, #291, #314, #315

Problem

Provider IDs, labels, token field names, default models, enabled-provider rules, and test adapters are split across settings UI and route handlers. Google sync will add more provider surface, so this needs one registry before it grows.

Solution

Create a provider registry for settings-owned integrations:

centralize provider IDs, display labels, token metadata field names, and scopes/categories
include NLP recurrence and geocoding providers if they remain in scope
leave Google provider OAuth with a clean path to use the same registry concepts without becoming app login
update settings UI and test routes to import provider definitions instead of duplicating switch statements

Acceptance criteria

Settings UI and API routes agree on provider IDs and required fields.
Provider tests are dispatched through a single registry or adapter map.
Token/secret fields are named consistently and never rendered back to the client.
Google Calendar/Tasks sync issues have a clear provider-extension path.

Parent: #305 Related: #290, #123, #291, #314, #315 ## Problem Provider IDs, labels, token field names, default models, enabled-provider rules, and test adapters are split across settings UI and route handlers. Google sync will add more provider surface, so this needs one registry before it grows. ## Solution Create a provider registry for settings-owned integrations: - centralize provider IDs, display labels, token metadata field names, and scopes/categories - include NLP recurrence and geocoding providers if they remain in scope - leave Google provider OAuth with a clean path to use the same registry concepts without becoming app login - update settings UI and test routes to import provider definitions instead of duplicating switch statements ## Acceptance criteria - Settings UI and API routes agree on provider IDs and required fields. - Provider tests are dispatched through a single registry or adapter map. - Token/secret fields are named consistently and never rendered back to the client. - Google Calendar/Tasks sync issues have a clear provider-extension path.

barrettruth added this to the v0.1.0 milestone

2026-05-11 19:20:27 +00:00

barrettruth added the

track:api

track:ui

type:cleanup

labels

2026-05-11 19:20:27 +00:00

barrettruth referenced this issue

2026-05-11 19:20:49 +00:00

tracker: blank-start cleanup and foundation migration #305

barrettruth referenced this issue from a pull request that will close it,