feat: local Slack gateway with DMs, engaged threads and inbound files #51
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feat/slack-socket-gateway"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Scope
Optional trusted local GatewayModule. Two required tokens only; workspace discovered, team/channel restrictions optional. DMs, persisted engaged public/private channel threads, stable message dedup IDs, private inbound files and actual image plumbing through Core contract v1. Socket lifecycle and method cooldowns bounded. Manifest and installation/rollback runbook included.
Verification
Self-reviewed local candidate. 34/34 fake-transport tests pass after rebase on
94d6dfb, no skips; diff check passes. Core inbound path PR282 merged cbec53b, tested separately with 152 tests including actual gateway-to-Core fake integration. No live Slack calls or activation.Dependency and limitations
Requires running Core with inboundAttachments:1 (PR282). Local immutable four-module installation, no automatic enablement. Upload adapter has durable stages and ambiguity blocking, but the Core/agent outbound file-send hook is NOT implemented: do not claim usable outbound transfer. Manifest excludes files:write until that path is delivered. This PR delivers a usable inbound/DM/thread increment and does NOT close the broader bidirectional file mandate. No automatic blob GC, parent directories trusted.
No external reviewer agents requested. Required repository checks remain in force; no claim of CI success or live deployment.