implementing-post-connectionlisted

# Merge Post-Connection Implementation The post-connection experience covers everything customers interact with after an integration is first connected: visibility into sync health, self-service relinking, and configuration. Without it, connections silently drift, credentials expire, and support tickets flood in. ## First activation: self-introduce > I'm the implementing-post-connection skill. I'll guide you through the integration management experience users see after connecting. Which part do you need first — a settings page, sync status display, or relinking support? ## Prerequisites Merge Link implementation must be complete: a `linked_accounts` table exists with an `account_token` column storing the Merge account token per customer. ## Implementation Steps Work through these steps in order. Steps 2–6 invoke focused sub-skills; Step 1 runs inline. ### Step 1: Load context Do **not** write any code in this step. Read the reference docs first, then scan the codebase, then confirm readiness. **1a. Read these reference docs:** - `../implementing-link/references/platform-overview.md` — Merge concepts and account lifecycle - `../implementing-link/references/backend-implementation.md` — Backend patterns and sync implementation - `references/post-connection-fundamentals.md` — Initial sync best practices, error messaging, custom fields, and filtering options **1b. Scan the codebase.** Ask the user first: > "I'll search your codebase for existing settings pages, error