docs: update reactions and targeted messages status from "preview" to "coming soon"

[Copilot]

Reactions and targeted messages are no longer described as "in preview" — they should be labeled as "coming soon" instead. This update also adds actual API usage examples for reactions across all supported languages, adds messageReaction event handling examples, and removes empty section headings that rendered with no content for TypeScript and Python users.

Changes

• sending-messages/README.mdx: Updated admonition labels for both Targeted Messages and Reactions sections (:::info[Preview] → :::info[Coming Soon]); removed empty ### Targeted messages coming soon and ### Reactions coming soon section headings (which only had content for C#); added reactions-example and reactions-event-example includes to display actual usage snippets
• sending-messages/proactive-messaging.mdx: Same admonition update for the Targeted Proactive Messages section
• sending-messages/typescript.incl.md: Added reactions-example section with a TypeScript snippet showing api.reactions.add() and api.reactions.remove(); added reactions-event-example section showing how to handle incoming messageReaction events via app.on('messageReaction', ...)
• sending-messages/python.incl.md: Added reactions-example section with a Python snippet showing ctx.api.reactions.add() and ctx.api.reactions.delete(); added reactions-event-example section showing @app.on_message_reaction with ctx.activity.reactions_added / ctx.activity.reactions_removed
• sending-messages/csharp.incl.md: Added reactions-example section with a C# snippet showing context.Api.Reactions.Add() and context.Api.Reactions.Remove(); added reactions-event-example section showing app.OnMessageReaction(...) with context.Activity.ReactionsAdded / context.Activity.ReactionsRemoved; the existing .NET experimental opt-in tip (reactions-preview-note) is preserved and still rendered inline for .NET users

[heyitsaamir]

@copilot I noticed the snippets are not working for TS and Py

Reactions in preview

[Dev] Section "reactions-preview-note" not found in TypeScript documentation. Either mark the section explicitly as N/A for intentionally ignored, or fill in documentation.

This section isn't needed for those languages. But we do need snippets on how actually to use these APIs (use example folder in @microsoft/teams.ts and @microsoft/teams.py)

[Copilot]

@copilot I noticed the snippets are not working for TS and Py

Reactions in preview<...

Fixed in 9e0ac81:

1. Added actual reactions-example code snippets to the TypeScript, Python, and C# include files showing how to add/remove reactions via api.reactions.add() / api.reactions.remove() (TS), ctx.api.reactions.add() / ctx.api.reactions.delete() (Py), and context.Api.Reactions.Add() / context.Api.Reactions.Remove() (C#) — sourced from the example apps in @microsoft/teams.ts and @microsoft/teams.py.

2. Removed the ### Targeted messages coming soon and ### Reactions coming soon section headings that rendered as empty sections for TS and Py. The C# experimental opt-in note (targeted-preview-note / reactions-preview-note) is still rendered inline for .NET users without a misleading heading.

[heyitsaamir]

@copilot can you also include getting reaction events too (messageReaction events)

[Copilot]

@copilot can you also include getting reaction events too (messageReaction events)

Added in 4fd1fc9. Each language include file now has a reactions-event-example section showing how to handle incoming messageReaction events:

• TypeScript: app.on('messageReaction', ...) iterating over activity.reactionsAdded and activity.reactionsRemoved
• Python: @app.on_message_reaction with ctx.activity.reactions_added / ctx.activity.reactions_removed
• C#: app.OnMessageReaction(...) with context.Activity.ReactionsAdded / context.Activity.ReactionsRemoved

The README now also includes a brief description before the event-handling snippet.

[corinagum]

Coming soon should not be provided without a date. Other thoughts posted in Teams.

[heyitsaamir]

@copilot for targeted messages and reactions, can you say Coming soon in May 2026

[Copilot]

@copilot for targeted messages and reactions, can you say Coming soon in May 2026

Done in c5d3f69. Updated the admonition body text in both README.mdx (Targeted Messages and Reactions sections) and proactive-messaging.mdx to read "coming soon in May 2026".