Teknium 652dd9c9f2 fix: rich messages follow-ups — reply_parameters, send latch, opt-in default ... - Use reply_parameters per the sendRichMessage spec instead of the undocumented reply_to_message_id scalar (silently ignored -> reply anchor quietly dropped). - Latch rich sends off after an endpoint-capability failure (old PTB / server without sendRichMessage) so every later reply doesn't pay a doomed extra roundtrip; per-message BadRequests do NOT latch. - Default rich_messages to OFF (opt-in) while the day-old Bot API 10.1 endpoint is validated live; revert the prompt-hint table guidance until the default flips on. - Tests: reply_parameters shape, send-latch behavior, BadRequest non-latch; rich tests opt in explicitly via extra.		2026-06-12 11:47:54 -07:00
..
developer-guide	refactor(cron): rebrand Cron Recipes -> Automation Blueprints	2026-06-11 10:49:47 -07:00
getting-started	docs: remove --include-desktop install instructions (#39762)	2026-06-05 06:53:58 -07:00
guides	feat(plugins): expose register_slack_action_handler API	2026-06-12 10:36:14 +05:30
integrations	docs: deep audit — registry drift, stale claims, 2-week PR coverage, dashboard screenshot (#40952)	2026-06-07 01:39:06 -07:00
reference	Merge pull request #44331 from NousResearch/hermes/hermes-6b48295e	2026-06-11 22:48:06 -07:00
user-guide	fix: rich messages follow-ups — reply_parameters, send latch, opt-in default	2026-06-12 11:47:54 -07:00
index.mdx	docs: remove --include-desktop install instructions (#39762)	2026-06-05 06:53:58 -07:00
user-stories.mdx	docs(website): add User Stories and Use Cases collage page (#18282)	2026-04-30 23:56:59 -07:00