@hogsend/plugin-discord 0.22.0 → 0.23.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@hogsend/plugin-discord",
-  "version": "0.22.0",
+  "version": "0.23.0",
   "type": "module",
   "license": "MIT",
   "repository": {
@@ -23,7 +23,7 @@
     "access": "public"
   },
   "dependencies": {
-    "@hogsend/engine": "^0.22.0"
+    "@hogsend/engine": "^0.23.0"
   },
   "peerDependencies": {
     "discord.js": ">=14.0.0"

package/src/connect/member-link.ts

@@ -2,10 +2,11 @@ import type { DiscordCurrentUser } from "./oauth.js";
 
 /**
  * The shape a per-member link reduces to: the args for a single
- * `resolveOrCreateContact({ email?, discordId })` call (the consumer's
+ * `client.identity.linkContact({ email?, discordId })` call (the consumer's
  * `resolveContact` callback forwards it). No bespoke merge path — the engine's
  * existing identity machinery folds the Discord-only contact onto the
- * email/identified one (or fills `discord_id` in when only the email resolves).
+ * email/identified one (or fills `discord_id` in when only the email resolves),
+ * and `linkContact` propagates the resulting analytics merge (§7).
  */
 export interface DiscordMemberLink {
   /** The Discord user the member linked. */

package/src/connector.ts

@@ -251,13 +251,20 @@ export interface CreateDiscordConnectorConfig {
   /** Persist server-derived Discord config (kind="derived"). */
   saveDerived: (patch: Record<string, unknown>) => Promise<void>;
   /**
-   * Resolve / merge the member-linked contact (the consumer wires this to the
-   * engine's `resolveOrCreateContact`). The ONLY correct wiring is
-   * `resolveOrCreateContact({ discordId: patch.discordId, email: patch.email,
-   * contactProperties: patch.contactProperties })` — routing the raw snowflake
-   * through the `discord` identity Kind so the `discord_id` column is
-   * load-bearing. `email` is the AUTHORITATIVE address the link was issued for
-   * (from the engine-verified state), NOT the OAuth-reported Discord email.
+   * Resolve / merge the member-linked contact. The consumer wires this to the
+   * engine's identity-attach helper `client.identity.linkContact({ discordId:
+   * patch.discordId, email: patch.email, contactProperties:
+   * patch.contactProperties })` — routing the raw snowflake through the `discord`
+   * identity Kind so the `discord_id` column is load-bearing. `email` is the
+   * AUTHORITATIVE address the link was issued for (from the engine-verified
+   * state), NOT the OAuth-reported Discord email.
+   *
+   * Use `client.identity.linkContact` (NOT bare `resolveOrCreateContact`): on a
+   * successful `/link` contact-merge it propagates the analytics merge through
+   * the SAME engine emission ingest uses (§7), folding the discord-keyed loser
+   * into the canonical (email/external) survivor so Discord-platform events stop
+   * landing on a separate PostHog person. `resolveOrCreateContact` alone merges
+   * the rows but emits no PostHog merge.
    */
   resolveContact: (patch: {
     discordId: string;