fix(gmail): credit threads to the sender, not the connection

[KrisBraun]

Problem

A Gmail thread's notification (and in-app header) showed the connection — "Gmail (Plot)" — where the sender should be, e.g. Gmail (Plot): Workshop ideas.

transformGmailThread set only per-note authors and no link-level author, so the runtime defaulted thread.author_id to the connection's twist_instance, whose actor name renders as <Connector> (<account>).

Fix

Set the link-level author to the first message's sender — mirroring outlook-mail and slack, which already do this. We reuse the first note's author so the existing DMARC From-rewrite name suppression carries through unchanged.

The runtime side (a platform fallback so any connector that omits a link author credits the originator instead of the connection, plus the notification layout and a backfill of existing threads) lands in the core repo PR.

Tests

gmail.test.ts adds a transformGmailThread — link author (thread originator) suite: credits the first sender, credits the originator (not a later replier) on multi-message threads, and mirrors DMARC name suppression. All 24 gmail tests pass; tsc clean.

🤖 Generated with Claude Code

[KrisBraun]

Problem

A Gmail thread's notification (and in-app header) showed the connection — "Gmail (Plot)" — where the sender should be, e.g. Gmail (Plot): Workshop ideas.

transformGmailThread set only per-note authors and no link-level author, so the runtime defaulted thread.author_id to the connection's twist_instance, whose actor name renders as <Connector> (<account>).

Fix

Set the link-level author to the first message's sender — mirroring outlook-mail and slack, which already do this. We reuse the first note's author so the existing DMARC From-rewrite name suppression carries through unchanged.

The runtime side (a platform fallback so any connector that omits a link author credits the originator instead of the connection, plus the notification layout and a backfill of existing threads) lands in the core repo PR.

Tests

gmail.test.ts adds a transformGmailThread — link author (thread originator) suite: credits the first sender, credits the originator (not a later replier) on multi-message threads, and mirrors DMARC name suppression. All 24 gmail tests pass; tsc clean.

🤖 Generated with Claude Code

[KrisBraun]

Problem

A Gmail thread's notification (and in-app header) showed the connection — "Gmail (Plot)" — where the sender should be, e.g. Gmail (Plot): Workshop ideas.

transformGmailThread set only per-note authors and no link-level author, so the runtime defaulted thread.author_id to the connection's twist_instance, whose actor name renders as <Connector> (<account>).

Fix

Set the link-level author to the first message's sender — mirroring outlook-mail and slack, which already do this. We reuse the first note's author so the existing DMARC From-rewrite name suppression carries through unchanged.

The runtime side (a platform fallback so any connector that omits a link author credits the originator instead of the connection, plus the notification layout and a backfill of existing threads) lands in the core repo PR.

Tests

gmail.test.ts adds a transformGmailThread — link author (thread originator) suite: credits the first sender, credits the originator (not a later replier) on multi-message threads, and mirrors DMARC name suppression. All 24 gmail tests pass; tsc clean.

🤖 Generated with Claude Code

[KrisBraun]

Problem

A Gmail thread's notification (and in-app header) showed the connection — "Gmail (Plot)" — where the sender should be, e.g. Gmail (Plot): Workshop ideas.

transformGmailThread set only per-note authors and no link-level author, so the runtime defaulted thread.author_id to the connection's twist_instance, whose actor name renders as <Connector> (<account>).

Fix

Set the link-level author to the first message's sender — mirroring outlook-mail and slack, which already do this. We reuse the first note's author so the existing DMARC From-rewrite name suppression carries through unchanged.

The runtime side (a platform fallback so any connector that omits a link author credits the originator instead of the connection, plus the notification layout and a backfill of existing threads) lands in the core repo PR.

Tests

gmail.test.ts adds a transformGmailThread — link author (thread originator) suite: credits the first sender, credits the originator (not a later replier) on multi-message threads, and mirrors DMARC name suppression. All 24 gmail tests pass; tsc clean.

🤖 Generated with Claude Code

[KrisBraun]

Problem

A Gmail thread's notification (and in-app header) showed the connection — "Gmail (Plot)" — where the sender should be, e.g. Gmail (Plot): Workshop ideas.

transformGmailThread set only per-note authors and no link-level author, so the runtime defaulted thread.author_id to the connection's twist_instance, whose actor name renders as <Connector> (<account>).

Fix

Set the link-level author to the first message's sender — mirroring outlook-mail and slack, which already do this. We reuse the first note's author so the existing DMARC From-rewrite name suppression carries through unchanged.

The runtime side (a platform fallback so any connector that omits a link author credits the originator instead of the connection, plus the notification layout and a backfill of existing threads) lands in the core repo PR.

Tests

gmail.test.ts adds a transformGmailThread — link author (thread originator) suite: credits the first sender, credits the originator (not a later replier) on multi-message threads, and mirrors DMARC name suppression. All 24 gmail tests pass; tsc clean.

🤖 Generated with Claude Code

[KrisBraun]

Problem

A Gmail thread's notification (and in-app header) showed the connection — "Gmail (Plot)" — where the sender should be, e.g. Gmail (Plot): Workshop ideas.

transformGmailThread set only per-note authors and no link-level author, so the runtime defaulted thread.author_id to the connection's twist_instance, whose actor name renders as <Connector> (<account>).

Fix

Set the link-level author to the first message's sender — mirroring outlook-mail and slack, which already do this. We reuse the first note's author so the existing DMARC From-rewrite name suppression carries through unchanged.

The runtime side (a platform fallback so any connector that omits a link author credits the originator instead of the connection, plus the notification layout and a backfill of existing threads) lands in the core repo PR.

Tests

gmail.test.ts adds a transformGmailThread — link author (thread originator) suite: credits the first sender, credits the originator (not a later replier) on multi-message threads, and mirrors DMARC name suppression. All 24 gmail tests pass; tsc clean.

🤖 Generated with Claude Code

[KrisBraun]

Problem

A Gmail thread's notification (and in-app header) showed the connection — "Gmail (Plot)" — where the sender should be, e.g. Gmail (Plot): Workshop ideas.

transformGmailThread set only per-note authors and no link-level author, so the runtime defaulted thread.author_id to the connection's twist_instance, whose actor name renders as <Connector> (<account>).

Fix

Set the link-level author to the first message's sender — mirroring outlook-mail and slack, which already do this. We reuse the first note's author so the existing DMARC From-rewrite name suppression carries through unchanged.

The runtime side (a platform fallback so any connector that omits a link author credits the originator instead of the connection, plus the notification layout and a backfill of existing threads) lands in the core repo PR.

Tests

gmail.test.ts adds a transformGmailThread — link author (thread originator) suite: credits the first sender, credits the originator (not a later replier) on multi-message threads, and mirrors DMARC name suppression. All 24 gmail tests pass; tsc clean.

🤖 Generated with Claude Code

[KrisBraun]

Problem

A Gmail thread's notification (and in-app header) showed the connection — "Gmail (Plot)" — where the sender should be, e.g. Gmail (Plot): Workshop ideas.

transformGmailThread set only per-note authors and no link-level author, so the runtime defaulted thread.author_id to the connection's twist_instance, whose actor name renders as <Connector> (<account>).

Fix

Set the link-level author to the first message's sender — mirroring outlook-mail and slack, which already do this. We reuse the first note's author so the existing DMARC From-rewrite name suppression carries through unchanged.

The runtime side (a platform fallback so any connector that omits a link author credits the originator instead of the connection, plus the notification layout and a backfill of existing threads) lands in the core repo PR.

Tests

gmail.test.ts adds a transformGmailThread — link author (thread originator) suite: credits the first sender, credits the originator (not a later replier) on multi-message threads, and mirrors DMARC name suppression. All 24 gmail tests pass; tsc clean.

🤖 Generated with Claude Code