972f0314de
Compose/fix-up on top of the cherry-picked cluster commits: - Unify the config surface: platforms.buzz.reply_to_mode: off (PlatformConfig field, as Discord/Telegram) and extra.reply_in_thread: false (the key Slack users know; env BUZZ_REPLY_IN_THREAD) are equivalent opt-outs, bridged through _apply_yaml_config and honored by send(), send_image(), and _standalone_send (cron delivery). - Progress/status bubbles honor the opt-out too: gateway/run.py resolves _progress_reply_in_thread from the Buzz adapter (mirroring the Slack path) so the synthetic-thread fallback and the progress reply anchor are both suppressed when the user asked for flat replies (#75082, #95842). - Deduplicate NIP-10 parsing: inbound session thread_id now reuses _extract_thread_root (marked root > reply > legacy positional e-tag) instead of a second inline root-marker-only scan. - display_config: add buzz to _PLATFORM_DEFAULTS at TIER_MEDIUM — with edit_message now implemented, accumulate-style progress works, but without the entry Buzz inherited the verbose _GLOBAL_DEFAULTS and every interim update became a permanent channel post (#95841). - plugin.yaml optional_env + platform docs for the new keys. - contributors/emails mappings for the cherry-picked authors.
2 lines
11 B
Plaintext
2 lines
11 B
Plaintext
tomwattsca
|