Bump slack-support-agent to 0.0.2

[fr3on]

Plugin Submission

Plugin information

• Author: fr3on
• Plugin name: slack-support-agent
• Version: 0.0.2
• Source repository: https://github.com/fr3on/slack-support-agent
• Contact: https://github.com/fr3on

Submission type

• New plugin
• Version update

What changed

• Fixed a bug where thread history could silently lose all older context once local cache entries expired (24h TTL): the cache-emptiness check ran after the current message was already pre-appended, so it never detected a truly empty cache and skipped backfilling from Slack's API. A thread that went quiet for a day would then look context-free to the linked app on the next mention, even though Slack still has the full history. Now correctly backfills and merges from Slack when needed.
• Each Slack channel/DM is now attributed to its own Dify end user (user field on chat.invoke), instead of every conversation falling back to one shared anonymous end user - improves per-conversation visibility in Dify's own Logs/Messages.
• Added an optional "Summarize Thread History" setting: condenses the selected thread history into a single AI-generated summary before sending it, instead of the raw message list. Short conversations are sent unchanged with no extra cost.
• Added an optional "Summarization Model" setting to pick a specific model for the above; defaults to Dify's system reasoning model if left unset.

Risk level

• Low risk
• Medium risk
• High risk

Same risk profile as the initial submission: sends Slack message content to the linked Dify app and processes user-uploaded Slack files. No code/SQL execution, no SSH/filesystem/browser automation, no arbitrary user-controlled URL fetching.

Required checks

• I have read and followed the Marketplace submission requirements.
• I have read and comply with the Plugin Developer Agreement.
• I tested this plugin on Dify Community Edition and Dify Cloud, or documented any limitation below.
• The package contains only files needed at runtime.
• The package does not contain secrets, local credentials, .env files, .git directories, virtual environments, caches, logs, or IDE files.
• The package does not contain executables or bundled binaries, or I explained why they are required below.
• The plugin README includes setup steps, usage instructions, required APIs or credentials, connection requirements, and the source repository link.
• The plugin includes PRIVACY.md, and manifest.yaml references it.
• All user-facing text is primarily in English.

Security and privacy notes

No change to the security/privacy profile from the initial submission - see PRIVACY.md. The new summarization feature reuses the plugin's existing model permission (already declared in manifest.yaml) and sends the same thread content that was already being sent as thread_history; it does not introduce a new data flow.

Local validation

• Full unit/regression test suite (chunking, mention substitution, markdown conversion, routing context, context-scope trimming, cache backfill/merge, summarization with and without an explicit model) run locally against the actual plugin code - all passing.
• Live-tested against a real Slack workspace and a self-hosted Dify instance: verified multi-turn DM conversation continuity, thread-history grounding in the linked app's responses, and the stale-cache backfill fix against a real multi-day-old thread.
• Packaged with the official Dify plugin CLI (dify-plugin v0.6.10): dify-plugin plugin package ./slack-support-agent -o ./slack-support-agent-0.0.2.difypkg. Verified the archive contains only the 11 runtime files (no .git, caches, or secrets).

Reviewer notes

None.