fix: update invalid inbound/outbound activities

[rajan-chari]

Summary

Fixes #338.

removed:

• ConversationUpdateActivityInput

  • invalid outbound activity that fails service validation

• inbound and outbound HandoffActivity

  • not recognized by backend
  • BF has a similar event but it uses type: "event" + name: "handoff.initiate"
  • similiarly exists for copilot but it is only inbound as HandoffActionInvokeActivity which we have

• inbound and outbound TraceActivity

  • not recognized by backend
  • is only for the BF Emulator which is now deprecated. doc ref

• MessageDeleteActivityInput

  • invalid outbound activity that fails service validation
  • will be provided in a new API endpoint instead

• MessageUpdateActivityInput

  • invalid outbound activity that fails service validation

• CommandSendActivityInput

  • invalid outbound activity that fails service validation
  • not a Teams concept. it's a BF activity type used in the skills protocol — where one bot sends a command to a skill bot and gets a commandResult back.

• CommandResultActivityInput

  • not recognized by backend
  • not a Teams concept, it's a BF skill that sends back to the parent bot after completing a command.

[Copilot]

Pull request overview

This PR updates the outbound “sendable activity” typing surface in the Teams API package to better reflect what the Bot Framework /v3/conversations/{id}/activities endpoints accept, aligning the SDK’s type promises with runtime behavior (Fixes #338).

Changes:

• Narrow ActivityParams to only include MessageActivityInput, TypingActivityInput, and (temporarily) MessageReactionActivityInput.
• Remove several inbound-only *ActivityInput types from the outbound ActivityParams union to prevent users from attempting unsupported sends.

[rajan-chari]

Manual Test Results — Echo Bot (Python)

Tested on branch fix/338-rename-activity-params (PR #342, which stacks on this PR), commit bf62a5c. Python echo bot deployed to BAMI1 tenant via DevTunnel.

#	Test	Result	Details
1	Send a message → bot replies	PASS	Sent "Hello from bolt test" → bot replied "You said 'Hello from bolt test'" (MessageActivityInput via ctx.send(str))
2	Bot shows typing indicator before reply	PASS	TypingActivityInput sent in handler before reply
3	Edit a sent message → @app.on_message_update fires	PASS	Edited message → bot replied "Message updated: 'Hello from bolt test EDITED'"
4	Delete a message → @app.on_message_delete fires	PASS	Deleted message → bot replied "A message was deleted."
5	No regression in send/typing	PASS	Both MessageActivityInput and TypingActivityInput work after narrowing the union

All 5 test steps from the test plan passed. The narrowed sendable union (message + typing only) works correctly; incoming event handlers are unaffected.

[lilyydu]

I did another pass with Claude and based on scanning APX repo - it accepts message, command, and typing:

• MessageUpdateActivityInput and MessageDeleteActivityInput can use PUT and DELETE respectively on
  /v3/conversations/{id}/activities/{activityId}
• CommandSendActivityInput is handled by POST

thus, MessageUpdateActivityInput, MessageDeleteActivityInput, and CommandSendActivityInput should remain in ActivityParams

Can you re-test different requests with these activities to verify acurracy?

[heyitsaamir]

Makes sense to me. @lilyydu based on your models work, I think you're better suited to approve.

Edit: saw your message above.

[jerbob92]

Why keep messageReaction? There is no currently no option to set a reaction from a bot right?

I did another pass with Claude and based on scanning APX repo - it accepts message, command, and typing:

• MessageUpdateActivityInput and MessageDeleteActivityInput can use PUT and DELETE respectively on
  /v3/conversations/{id}/activities/{activityId}
• CommandSendActivityInput is handled by POST

thus, MessageUpdateActivityInput, MessageDeleteActivityInput, and CommandSendActivityInput should remain in ActivityParams

Can you re-test different requests with these activities to verify acurracy?

When I tried it out, at least MessageDeleteActivityInput did not work because it's not routed to the correct operation (only update and create are handled in send).