post-connection-build-settings-pagelisted

# Building the Integration Settings Page This is the **single home** for everything an end user does with a connected integration after the initial Merge Link flow: see whether it's healthy, reconnect when it breaks, and configure how data syncs. Treating the UI page and its persistence model as one artifact prevents silent failure modes (credentials expire, settings drift, partial setup looks "done"). ## Purpose A dedicated settings page prevents "silent failure" — credentials expire, permissions change, customer requirements differ, and end users need a self-service way to fix and configure their integration without filing a support ticket. This page is the persistent home for integration configuration, not a one-time setup wizard. ## Prerequisites - All four backend endpoints from `link-implement-backend` working — these are routes on **your** server (e.g., `/api/merge/create-link-token`), not Merge API endpoints - A backend able to add either a new `integration_settings` table or a `jsonb`/JSON column on `linked_accounts` ## Before Proceeding Three pieces of information are needed before generating any code. If invoked from `implementing-post-connection`, these were answered in Step 1 — use that context. Otherwise, gather them now: **Step 1 — Confirm or gather required context:** - **Categories**: Which Merge categories does the settings page need to display? (`hris`, `ats`, `crm`, `accounting`, `ticketing`, `filestorage`, `knowledgebase`) - **Frontend framework