From 826f0f666fc0b5a1d59c0a64728bfbc5867b1f93 Mon Sep 17 00:00:00 2001 From: "Reichenbach, Michael" <755327+Silthus@users.noreply.github.com> Date: Fri, 13 Nov 2026 16:28:29 +0000 Subject: [PATCH 1/9] fix(migrate-email): collect before-cutover plan notes in Step 9 A provider's mapping.md or account.md, or a rewrite file, can ask for an item on the report's "Before cutover" list. Such items now go into the plan as notes that start with `before cutover:`, and Step 9 lists each one there. Co-Authored-By: Claude Opus 5.5 --- context/skills/migrate-email/references/3-inventory.md | 2 ++ context/skills/migrate-email/references/9-report.md | 4 ++-- context/skills/migrate-email/references/rewrite-php.md | 2 +- 3 files changed, 5 insertions(+), 3 deletions(-) diff --git a/context/skills/migrate-email/references/3-inventory.md b/context/skills/migrate-email/references/3-inventory.md index dcab8f2c..53ed3ae0 100644 --- a/context/skills/migrate-email/references/3-inventory.md +++ b/context/skills/migrate-email/references/3-inventory.md @@ -108,4 +108,6 @@ A sites table, one row per site, in source tree order: Under the table, for each `template` site that moves, note its provider template's ID or name, whether it moves into the code or to a template made in PostHog, and where its content is: the person's copy, or the temporary file of the API answer. For a template made in PostHog, add its template ID, and `must be marked sensitive: ` when Step 3 says it must be. For any site that moves with an open pixel its emails never had, note `open pixel added: the person agreed`, as Step 3 says under "Opens the provider didn't track". For each site that stays because it relies on the provider's suppression list, note what would let it move, as Step 3 says after the sender check. +In any step, when the provider's `mapping.md` or `account.md`, or a rewrite file, says to note something for the report's "Before cutover" list, write it under the table as a note that starts with `before cutover:`, such as `before cutover: enable ext-curl where the app runs`. Step 9 lists each such note there. + A list of the other provider calls, each with its file, line, and what it does, and a list of the webhook handlers, each with its file, line, the events it handles, and how it finds the send. diff --git a/context/skills/migrate-email/references/9-report.md b/context/skills/migrate-email/references/9-report.md index 36915a45..c49d1dc3 100644 --- a/context/skills/migrate-email/references/9-report.md +++ b/context/skills/migrate-email/references/9-report.md @@ -29,7 +29,7 @@ Read `.posthog-email-migration-plan.md`. Write `posthog-migrate-email- ", or "Stays on : ".> - + ## Other calls @@ -63,7 +63,7 @@ Read `.posthog-email-migration-plan.md`. Write `posthog-migrate-email- The moved sites send through PostHog as soon as this code is deployed. Everything in this list has to be done before that deploy. - + ## After cutover diff --git a/context/skills/migrate-email/references/rewrite-php.md b/context/skills/migrate-email/references/rewrite-php.md index 6f54eadb..42750f87 100644 --- a/context/skills/migrate-email/references/rewrite-php.md +++ b/context/skills/migrate-email/references/rewrite-php.md @@ -11,7 +11,7 @@ For a site in PHP, such as in a Laravel or Symfony app. A site that sends throug `composer require posthog/posthog-php`, which installs or upgrades it to the latest release that the project's constraints allow. Raise the constraint in `composer.json` when it holds the package back. -The send needs PHP's curl extension, which Composer doesn't ask for: without it every send fails with the code `missing_curl`. Add `"ext-curl": "*"` to `require` in `composer.json`, so an install where it's missing fails instead. When the app's Dockerfile, buildpack, or server setup doesn't show that it installs the extension, such as the official `php` Docker image, which has it built in, or a `php-curl` or `php8.3-curl` package, note it for the report's "Before cutover" list: enable ext-curl where the app runs. +The send needs PHP's curl extension, which Composer doesn't ask for: without it every send fails with the code `missing_curl`. Add `"ext-curl": "*"` to `require` in `composer.json`, so an install where it's missing fails instead. When the app's Dockerfile, buildpack, or server setup doesn't show that it installs the extension, such as the official `php` Docker image, which has it built in, or a `php-curl` or `php8.3-curl` package, note it for the report's "Before cutover" list: `before cutover: enable ext-curl where the app runs`. ## The client From 10e86b6fe3737083f881d50c21121122d6738e78 Mon Sep 17 00:00:00 2001 From: "Reichenbach, Michael" <755327+Silthus@users.noreply.github.com> Date: Fri, 13 Nov 2026 16:34:19 +0000 Subject: [PATCH 2/9] fix(migrate-email): delete a before-cutover note when its install is undone When no site is left in a language, Step 7 undoes the SDK install with the other changes its rewrite file's Install made, and deletes the notes it wrote, so Step 9 never lists a stale item. Co-Authored-By: Claude Opus 5.5 --- context/skills/migrate-email/references/3-inventory.md | 2 +- context/skills/migrate-email/references/7-rewrite.md | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/context/skills/migrate-email/references/3-inventory.md b/context/skills/migrate-email/references/3-inventory.md index 53ed3ae0..114515ab 100644 --- a/context/skills/migrate-email/references/3-inventory.md +++ b/context/skills/migrate-email/references/3-inventory.md @@ -108,6 +108,6 @@ A sites table, one row per site, in source tree order: Under the table, for each `template` site that moves, note its provider template's ID or name, whether it moves into the code or to a template made in PostHog, and where its content is: the person's copy, or the temporary file of the API answer. For a template made in PostHog, add its template ID, and `must be marked sensitive: ` when Step 3 says it must be. For any site that moves with an open pixel its emails never had, note `open pixel added: the person agreed`, as Step 3 says under "Opens the provider didn't track". For each site that stays because it relies on the provider's suppression list, note what would let it move, as Step 3 says after the sender check. -In any step, when the provider's `mapping.md` or `account.md`, or a rewrite file, says to note something for the report's "Before cutover" list, write it under the table as a note that starts with `before cutover:`, such as `before cutover: enable ext-curl where the app runs`. Step 9 lists each such note there. +In any step, when the provider's `mapping.md` or `account.md`, or a rewrite file, says to note something for the report's "Before cutover" list, write it under the table as a note that starts with `before cutover:`, such as `before cutover: enable ext-curl where the app runs`. When a later step undoes what a note is about, such as an SDK install once no site in its language moves, it deletes the note. Step 9 lists each note left. A list of the other provider calls, each with its file, line, and what it does, and a list of the webhook handlers, each with its file, line, the events it handles, and how it finds the send. diff --git a/context/skills/migrate-email/references/7-rewrite.md b/context/skills/migrate-email/references/7-rewrite.md index 1c0e0f42..79956cfb 100644 --- a/context/skills/migrate-email/references/7-rewrite.md +++ b/context/skills/migrate-email/references/7-rewrite.md @@ -57,7 +57,7 @@ Before you install or upgrade an SDK, check the release you install against ever When the app already used the SDK and the upgrade crosses a major version, read the installed package's changelog when it ships one, such as `CHANGELOG.md`, and search the whole repository for the app's other calls into the SDK, such as `capture` and `identify`. Fix each call the new major version changed, and note it for the report. A check that reads only syntax doesn't find these. -When the latest release lacks one of these, change no site that needs it. Mark each such row `moves: no — has no yet`, tell the person, and go on with the rest. When the client options lack the provider name, leave it out of the client. When no site is left in a language, undo that SDK's install or upgrade. When no site is left at all, delete each temporary copy of template content, tick the phase with `none moved`, and go to the next step. +When the latest release lacks one of these, change no site that needs it. Mark each such row `moves: no — has no yet`, tell the person, and go on with the rest. When the client options lack the provider name, leave it out of the client. When no site is left in a language, undo that SDK's install or upgrade, with each other change its rewrite file's "Install" made, such as `ext-curl` in `composer.json`, and delete each `before cutover:` note it wrote. When no site is left at all, delete each temporary copy of template content, tick the phase with `none moved`, and go to the next step. ## Set up the client @@ -106,7 +106,7 @@ For each site that moves, in plan order: - When the old code handled the provider's answer to a bad value that the app passes at run time, such as an empty recipient, also catch the argument error that the rewrite file names, or check the value before the send. - Never add a field that the old call didn't set, apart from the template key, the template ID, the distinct ID, the sensitive flag on a send with rendered content that carries a secret, the subject, body, `from`, and reply-to address that a provider template brought into the code held, and a field that the provider's `mapping.md` or this step says to add because the old send behaved that way without setting it, such as no retries for a request that kept its own deadline. Open or click tracking never adds one: engagement capture decides only whether the email's events land on the recipient's person, and PostHog adds its open pixel either way, so a site whose emails had none moves only with the person's yes, as Step 3 says under "Opens the provider didn't track". It sends each link through its click redirect only when the email is not sensitive, and a send in the code form is sensitive, since no template saved in PostHog has its key, as the rule on keys above makes sure, so PostHog counts its opens and no clicks. For a template made in PostHog, the template data takes the place of the provider's template variables. For a template brought into the code, the code renders them, and the send has no template data. -When a site turns out to need something `mapping.md` keeps on the provider, undo its change, set `moves` to `no` with the reason, delete the temporary copy of its template content when no other moving site sends that template, and go on. +When a site turns out to need something `mapping.md` keeps on the provider, undo its change, set `moves` to `no` with the reason, delete the temporary copy of its template content when no other moving site sends that template, and go on. When that leaves no site in its language, undo that SDK's install as "Set up the SDK" says. ## Write down From ee9437e5b47892e497ded7a78c6e3bb7d8e377c8 Mon Sep 17 00:00:00 2001 From: "Reichenbach, Michael" <755327+Silthus@users.noreply.github.com> Date: Fri, 13 Nov 2026 16:38:21 +0000 Subject: [PATCH 3/9] fix(migrate-email): keep the SDK installed after a late per-site undo A site's undo runs after the email client module exists, so removing the SDK there would break the build. That path keeps the install, and its before-cutover note stays true. Co-Authored-By: Claude Opus 5.5 --- context/skills/migrate-email/references/7-rewrite.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/context/skills/migrate-email/references/7-rewrite.md b/context/skills/migrate-email/references/7-rewrite.md index 79956cfb..795638b8 100644 --- a/context/skills/migrate-email/references/7-rewrite.md +++ b/context/skills/migrate-email/references/7-rewrite.md @@ -106,7 +106,7 @@ For each site that moves, in plan order: - When the old code handled the provider's answer to a bad value that the app passes at run time, such as an empty recipient, also catch the argument error that the rewrite file names, or check the value before the send. - Never add a field that the old call didn't set, apart from the template key, the template ID, the distinct ID, the sensitive flag on a send with rendered content that carries a secret, the subject, body, `from`, and reply-to address that a provider template brought into the code held, and a field that the provider's `mapping.md` or this step says to add because the old send behaved that way without setting it, such as no retries for a request that kept its own deadline. Open or click tracking never adds one: engagement capture decides only whether the email's events land on the recipient's person, and PostHog adds its open pixel either way, so a site whose emails had none moves only with the person's yes, as Step 3 says under "Opens the provider didn't track". It sends each link through its click redirect only when the email is not sensitive, and a send in the code form is sensitive, since no template saved in PostHog has its key, as the rule on keys above makes sure, so PostHog counts its opens and no clicks. For a template made in PostHog, the template data takes the place of the provider's template variables. For a template brought into the code, the code renders them, and the send has no template data. -When a site turns out to need something `mapping.md` keeps on the provider, undo its change, set `moves` to `no` with the reason, delete the temporary copy of its template content when no other moving site sends that template, and go on. When that leaves no site in its language, undo that SDK's install as "Set up the SDK" says. +When a site turns out to need something `mapping.md` keeps on the provider, undo its change, set `moves` to `no` with the reason, delete the temporary copy of its template content when no other moving site sends that template, and go on. ## Write down From 463e9dd5c43543a133d74f51d5b45c4c49f21519 Mon Sep 17 00:00:00 2001 From: "Reichenbach, Michael" <755327+Silthus@users.noreply.github.com> Date: Fri, 13 Nov 2026 16:40:26 +0000 Subject: [PATCH 4/9] fix(migrate-email): name the only undo that deletes a before-cutover note Co-Authored-By: Claude Opus 5.5 --- context/skills/migrate-email/references/3-inventory.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/context/skills/migrate-email/references/3-inventory.md b/context/skills/migrate-email/references/3-inventory.md index 114515ab..cc3c6303 100644 --- a/context/skills/migrate-email/references/3-inventory.md +++ b/context/skills/migrate-email/references/3-inventory.md @@ -108,6 +108,6 @@ A sites table, one row per site, in source tree order: Under the table, for each `template` site that moves, note its provider template's ID or name, whether it moves into the code or to a template made in PostHog, and where its content is: the person's copy, or the temporary file of the API answer. For a template made in PostHog, add its template ID, and `must be marked sensitive: ` when Step 3 says it must be. For any site that moves with an open pixel its emails never had, note `open pixel added: the person agreed`, as Step 3 says under "Opens the provider didn't track". For each site that stays because it relies on the provider's suppression list, note what would let it move, as Step 3 says after the sender check. -In any step, when the provider's `mapping.md` or `account.md`, or a rewrite file, says to note something for the report's "Before cutover" list, write it under the table as a note that starts with `before cutover:`, such as `before cutover: enable ext-curl where the app runs`. When a later step undoes what a note is about, such as an SDK install once no site in its language moves, it deletes the note. Step 9 lists each note left. +In any step, when the provider's `mapping.md` or `account.md`, or a rewrite file, says to note something for the report's "Before cutover" list, write it under the table as a note that starts with `before cutover:`, such as `before cutover: enable ext-curl where the app runs`. When a later step undoes what a note is about, such as an SDK install that Step 7 undoes under "Set up the SDK", it deletes the note. Step 9 lists each note left. A list of the other provider calls, each with its file, line, and what it does, and a list of the webhook handlers, each with its file, line, the events it handles, and how it finds the send. From 3a08ccd14a1431d8e1aad82dba0647a1290c1924 Mon Sep 17 00:00:00 2001 From: "Reichenbach, Michael" <755327+Silthus@users.noreply.github.com> Date: Sat, 14 Nov 2026 19:02:19 +0000 Subject: [PATCH 5/9] fix(migrate-email): stop promising hand-added suppressions block moved sends PostHog's Suppression list page adds an address only as a manual entry, which blocks marketing email but not a transactional send. When the import tool is missing, Step 5 and the report now say so, and Step 5 keeps the sites that rely on the provider's list to skip bounced addresses, with Step 3's reason. Co-Authored-By: Claude Opus 5.5 --- context/skills/migrate-email/references/5-suppressions.md | 4 ++-- context/skills/migrate-email/references/9-report.md | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/context/skills/migrate-email/references/5-suppressions.md b/context/skills/migrate-email/references/5-suppressions.md index 48577351..fb076f23 100644 --- a/context/skills/migrate-email/references/5-suppressions.md +++ b/context/skills/migrate-email/references/5-suppressions.md @@ -19,7 +19,7 @@ After the migration, while any site still sends through a provider that keeps a 1. Start with "Read the provider's notes", writing nothing down, since there is no plan file. When `account.md` says the provider keeps no suppression list at all, tell the person there is nothing to re-import, because keeps no suppression list, and stop. 2. Make sure the import lands in the project the deployed app sends from, which may not be the one the local env file names. Read the MCP's active project, its name and `api_token`, with the PostHog MCP `project-get` tool, called without an ID, and ask the person once whether production sends from that project, naming it. When the env file's project token differs from that `api_token`, say so in the question. Read only the token's line of the env file, by searching for the token variable's name: the file also holds secret keys, so never open all of it. When the person says no, ask which project production sends from. When `projects-get` lists it, offer to switch to it with `switch-project`, ask again once switched, and when this step ends, switch back to the project you started from and tell the person. When it isn't listed, such as a project in another organization, or they can't tell or don't want the switch, stop before importing. -3. Do "Check the import tool", "Get the list", "Import it" and "The full-access key", reading the provider's `account.md` for them, and skip the other sections. When the import tool is missing, tell the person to add the addresses the provider added since the last import in the production project they confirmed, naming it (Workflows, then Messaging, then Suppression list), and go to "The full-access key". +3. Do "Check the import tool", "Get the list", "Import it" and "The full-access key", reading the provider's `account.md` for them, and skip the other sections. When the import tool is missing, tell the person that the addresses the provider added since the last import can't reach PostHog yet: PostHog's Suppression list page adds an address only as a manual entry, which blocks marketing email but not the moved sends. Then go to "The full-access key". 4. Tell the person how many entries you imported, of how many, or that the import tool was missing, or why you couldn't get the list, and stop when this step ends: do not go on to the next step, and change no other file. ## Read the provider's notes @@ -32,7 +32,7 @@ When `account.md` says the provider keeps no suppression list at all, there is n Look for the PostHog MCP tool `email-suppressions-add`, and read its schema with `info`. -When it is missing, the import is not available to this person yet. Do not try other tools, and do not use the opt-out tools: opt-outs are marketing preferences, and transactional email ignores them. Tick the phase as `- [ ] suppressions — not imported: no import tool`, do what "Calls that change the provider's list" says, ask about the full-access key as the last section says, and continue to the next step. The report tells the person to add the addresses in PostHog (Workflows, then Messaging, then Suppression list) right before cutover, so the list holds the entries the provider adds until then. +When it is missing, the import is not available to this person yet. Do not try other tools, and do not use the opt-out tools: opt-outs are marketing preferences, and transactional email ignores them. Tick the phase as `- [ ] suppressions — not imported: no import tool`, do what "Calls that change the provider's list" says, ask about the full-access key as the last section says, and continue to the next step. Adding the addresses by hand doesn't take its place: PostHog's Suppression list page adds an address only as a manual entry, which blocks marketing email but not the moved sends. So ask the person once which sites that move rely on the provider's list to skip addresses that bounced, and set each one's `moves` to `no` with Step 3's reason `relies on 's suppression list` and its `to move:` note. When they can't tell or don't answer, every site that moves stays with that reason. ## Get the list diff --git a/context/skills/migrate-email/references/9-report.md b/context/skills/migrate-email/references/9-report.md index c49d1dc3..235ae0da 100644 --- a/context/skills/migrate-email/references/9-report.md +++ b/context/skills/migrate-email/references/9-report.md @@ -69,7 +69,7 @@ The moved sites send through PostHog as soon as this code is deployed. Everythin suppression list into PostHog with the migrate-email- skill`, or, when the plan says the import tool was missing, the PostHog page where the person adds the addresses by hand. Say that a re-import is safe to repeat: an address already on PostHog's list stays on it. Ask for one final import after the deploy that moves the last site off the provider. When no site stays, or the plan says the provider keeps no suppression list, leave this out: the import right before cutover is the last one, or there is no list to grow. +When a site stays on the provider, it keeps adding addresses that bounce to the provider's suppression list, and PostHog never sees them, so a moved send can mail them. Tell the person to re-import the list weekly while any site sends through the provider, as Step 5 says under "Re-import only": a moved send then mails an address that bounced for a week at most, and a release schedule wouldn't do, since the sites that stay add entries between releases. Give the prompt that re-imports only the list, `Re-import the suppression list into PostHog with the migrate-email- skill`, or, when the plan says the import tool was missing, say that those addresses can't reach PostHog until the import tool is available: an address added by hand on PostHog's Suppression list page blocks marketing email only, so a moved send still reaches it. Say that a re-import is safe to repeat: an address already on PostHog's list stays on it. Ask for one final import after the deploy that moves the last site off the provider. When no site stays, or the plan says the provider keeps no suppression list, leave this out: the import right before cutover is the last one, or there is no list to grow. When a moved send has a template key, list the keys, and tell the person to give each template they save in PostHog from now on another key: a send whose key a saved template has goes out through that template's settings. It fails when that template isn't transactional, and unless the send sets the sensitive flag, it takes the template's sensitive setting, off by default, so its links go through PostHog's click redirect and its subject lands on engagement events.> From ea0e8925e409fff21f33ed01dabd0683b1ca053e Mon Sep 17 00:00:00 2001 From: "Reichenbach, Michael" <755327+Silthus@users.noreply.github.com> Date: Sat, 14 Nov 2026 19:05:23 +0000 Subject: [PATCH 6/9] fix(migrate-email): ask before moving on when the import tool is missing The question that keeps sites comes before "continue to the next step", its note names the import as the way to move, and the inventory count follows. Co-Authored-By: Claude Opus 5.5 --- context/skills/migrate-email/references/5-suppressions.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/context/skills/migrate-email/references/5-suppressions.md b/context/skills/migrate-email/references/5-suppressions.md index fb076f23..51efe48f 100644 --- a/context/skills/migrate-email/references/5-suppressions.md +++ b/context/skills/migrate-email/references/5-suppressions.md @@ -32,7 +32,7 @@ When `account.md` says the provider keeps no suppression list at all, there is n Look for the PostHog MCP tool `email-suppressions-add`, and read its schema with `info`. -When it is missing, the import is not available to this person yet. Do not try other tools, and do not use the opt-out tools: opt-outs are marketing preferences, and transactional email ignores them. Tick the phase as `- [ ] suppressions — not imported: no import tool`, do what "Calls that change the provider's list" says, ask about the full-access key as the last section says, and continue to the next step. Adding the addresses by hand doesn't take its place: PostHog's Suppression list page adds an address only as a manual entry, which blocks marketing email but not the moved sends. So ask the person once which sites that move rely on the provider's list to skip addresses that bounced, and set each one's `moves` to `no` with Step 3's reason `relies on 's suppression list` and its `to move:` note. When they can't tell or don't answer, every site that moves stays with that reason. +When it is missing, the import is not available to this person yet. Do not try other tools, and do not use the opt-out tools: opt-outs are marketing preferences, and transactional email ignores them. Adding the addresses by hand doesn't take the import's place: PostHog's Suppression list page adds an address only as a manual entry, which blocks marketing email but not the moved sends. So ask the person once which sites that move rely on the provider's list to skip addresses that bounced, and set each one's `moves` to `no` with Step 3's reason `relies on 's suppression list` and the note `to move: import the suppression list once PostHog's import tool is available`. When they can't tell or don't answer, every site that moves stays with that reason. Update the count in the plan's `inventory` line. Then tick the phase as `- [ ] suppressions — not imported: no import tool`, do what "Calls that change the provider's list" says, ask about the full-access key as the last section says, and continue to the next step. ## Get the list From c9fbe58718db8265af84684a0fdebf4bc9690d4a Mon Sep 17 00:00:00 2001 From: "Reichenbach, Michael" <755327+Silthus@users.noreply.github.com> Date: Sat, 14 Nov 2026 19:24:34 +0000 Subject: [PATCH 7/9] fix(migrate-email): skip the reliance question for an empty list or a re-import Co-Authored-By: Claude Opus 5.5 --- context/skills/migrate-email/references/5-suppressions.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/context/skills/migrate-email/references/5-suppressions.md b/context/skills/migrate-email/references/5-suppressions.md index 51efe48f..2f2caab8 100644 --- a/context/skills/migrate-email/references/5-suppressions.md +++ b/context/skills/migrate-email/references/5-suppressions.md @@ -32,7 +32,7 @@ When `account.md` says the provider keeps no suppression list at all, there is n Look for the PostHog MCP tool `email-suppressions-add`, and read its schema with `info`. -When it is missing, the import is not available to this person yet. Do not try other tools, and do not use the opt-out tools: opt-outs are marketing preferences, and transactional email ignores them. Adding the addresses by hand doesn't take the import's place: PostHog's Suppression list page adds an address only as a manual entry, which blocks marketing email but not the moved sends. So ask the person once which sites that move rely on the provider's list to skip addresses that bounced, and set each one's `moves` to `no` with Step 3's reason `relies on 's suppression list` and the note `to move: import the suppression list once PostHog's import tool is available`. When they can't tell or don't answer, every site that moves stays with that reason. Update the count in the plan's `inventory` line. Then tick the phase as `- [ ] suppressions — not imported: no import tool`, do what "Calls that change the provider's list" says, ask about the full-access key as the last section says, and continue to the next step. +When it is missing, the import is not available to this person yet. Do not try other tools, and do not use the opt-out tools: opt-outs are marketing preferences, and transactional email ignores them. Adding the addresses by hand doesn't take the import's place: PostHog's Suppression list page adds an address only as a manual entry, which blocks marketing email but not the moved sends. So, outside a re-import, ask the person once whether the provider's list has any entries and, when it does, which sites that move rely on it to skip addresses that bounced, and set each one's `moves` to `no` with Step 3's reason `relies on 's suppression list` and the note `to move: import the suppression list once PostHog's import tool is available`. When they can't tell or don't answer, every site that moves stays with that reason. Update the count in the plan's `inventory` line. Then tick the phase as `- [ ] suppressions — not imported: no import tool`, do what "Calls that change the provider's list" says, ask about the full-access key as the last section says, and continue to the next step. ## Get the list From c8d380237775234238d64a0e3e2301b929de138f Mon Sep 17 00:00:00 2001 From: "Reichenbach, Michael" <755327+Silthus@users.noreply.github.com> Date: Sat, 14 Nov 2026 19:26:26 +0000 Subject: [PATCH 8/9] fix(migrate-email): tick an empty list as done when the import tool is missing Co-Authored-By: Claude Opus 5.5 --- context/skills/migrate-email/references/5-suppressions.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/context/skills/migrate-email/references/5-suppressions.md b/context/skills/migrate-email/references/5-suppressions.md index 2f2caab8..140ce571 100644 --- a/context/skills/migrate-email/references/5-suppressions.md +++ b/context/skills/migrate-email/references/5-suppressions.md @@ -32,7 +32,7 @@ When `account.md` says the provider keeps no suppression list at all, there is n Look for the PostHog MCP tool `email-suppressions-add`, and read its schema with `info`. -When it is missing, the import is not available to this person yet. Do not try other tools, and do not use the opt-out tools: opt-outs are marketing preferences, and transactional email ignores them. Adding the addresses by hand doesn't take the import's place: PostHog's Suppression list page adds an address only as a manual entry, which blocks marketing email but not the moved sends. So, outside a re-import, ask the person once whether the provider's list has any entries and, when it does, which sites that move rely on it to skip addresses that bounced, and set each one's `moves` to `no` with Step 3's reason `relies on 's suppression list` and the note `to move: import the suppression list once PostHog's import tool is available`. When they can't tell or don't answer, every site that moves stays with that reason. Update the count in the plan's `inventory` line. Then tick the phase as `- [ ] suppressions — not imported: no import tool`, do what "Calls that change the provider's list" says, ask about the full-access key as the last section says, and continue to the next step. +When it is missing, the import is not available to this person yet. Do not try other tools, and do not use the opt-out tools: opt-outs are marketing preferences, and transactional email ignores them. Adding the addresses by hand doesn't take the import's place: PostHog's Suppression list page adds an address only as a manual entry, which blocks marketing email but not the moved sends. So, outside a re-import, ask the person once whether the provider's list has any entries and, when it does, which sites that move rely on it to skip addresses that bounced, and set each one's `moves` to `no` with Step 3's reason `relies on 's suppression list` and the note `to move: import the suppression list once PostHog's import tool is available`. When they can't tell or don't answer, every site that moves stays with that reason. Update the count in the plan's `inventory` line. Then tick the phase as `- [x] suppressions — empty list` when the list has no entries, and as `- [ ] suppressions — not imported: no import tool` otherwise, do what "Calls that change the provider's list" says, ask about the full-access key as the last section says, and continue to the next step. ## Get the list From a14b591fda88325caff57bfb01c05fdc03789d89 Mon Sep 17 00:00:00 2001 From: "Reichenbach, Michael" <755327+Silthus@users.noreply.github.com> Date: Sat, 14 Nov 2026 19:28:16 +0000 Subject: [PATCH 9/9] fix(migrate-email): keep "no import tool" on an empty-list tick Co-Authored-By: Claude Opus 5.5 --- context/skills/migrate-email/references/5-suppressions.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/context/skills/migrate-email/references/5-suppressions.md b/context/skills/migrate-email/references/5-suppressions.md index 140ce571..8f84c196 100644 --- a/context/skills/migrate-email/references/5-suppressions.md +++ b/context/skills/migrate-email/references/5-suppressions.md @@ -32,7 +32,7 @@ When `account.md` says the provider keeps no suppression list at all, there is n Look for the PostHog MCP tool `email-suppressions-add`, and read its schema with `info`. -When it is missing, the import is not available to this person yet. Do not try other tools, and do not use the opt-out tools: opt-outs are marketing preferences, and transactional email ignores them. Adding the addresses by hand doesn't take the import's place: PostHog's Suppression list page adds an address only as a manual entry, which blocks marketing email but not the moved sends. So, outside a re-import, ask the person once whether the provider's list has any entries and, when it does, which sites that move rely on it to skip addresses that bounced, and set each one's `moves` to `no` with Step 3's reason `relies on 's suppression list` and the note `to move: import the suppression list once PostHog's import tool is available`. When they can't tell or don't answer, every site that moves stays with that reason. Update the count in the plan's `inventory` line. Then tick the phase as `- [x] suppressions — empty list` when the list has no entries, and as `- [ ] suppressions — not imported: no import tool` otherwise, do what "Calls that change the provider's list" says, ask about the full-access key as the last section says, and continue to the next step. +When it is missing, the import is not available to this person yet. Do not try other tools, and do not use the opt-out tools: opt-outs are marketing preferences, and transactional email ignores them. Adding the addresses by hand doesn't take the import's place: PostHog's Suppression list page adds an address only as a manual entry, which blocks marketing email but not the moved sends. So, outside a re-import, ask the person once whether the provider's list has any entries and, when it does, which sites that move rely on it to skip addresses that bounced, and set each one's `moves` to `no` with Step 3's reason `relies on 's suppression list` and the note `to move: import the suppression list once PostHog's import tool is available`. When they can't tell or don't answer, every site that moves stays with that reason. Update the count in the plan's `inventory` line. Then tick the phase as `- [x] suppressions — empty list: no import tool` when the list has no entries, and as `- [ ] suppressions — not imported: no import tool` otherwise, do what "Calls that change the provider's list" says, ask about the full-access key as the last section says, and continue to the next step. ## Get the list