feat: durable session-bound inbound attachments and runtime images #282
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feat/slack-inbound-attachments"
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
Small Core-only inbound vertical slice: durable session-bound references, admission and replay validation, bounded verified file reads, actual runtime SDK image blocks, explicit non-vision model rejection. Text-only transports unchanged. No Slack activation, no outbound file uploads.
Verification after rebase on
f985096152/152 relevant tests pass, no skips, including FIFO admission in a killable subprocess, persisted inbox restoration, forged ownership/source rejection, SDK image delivery, actual local Slack gateway-to-Core fake-transport integration. Typecheck, build and diff checks pass. Optional cross-repository test explicitly ran with SLACK_GATEWAY_CANDIDATE=/home/node/work/slack-gateway; default suite does not assume another checkout.
Review
Local self-review performed; FIFO open and post-IO admission fencing findings fixed and regression tested. plugin_review invoked but returns retained unrelated review for dirty /home/node/work/core; it is NOT claimed as coverage for this candidate. No external review agents requested.
Dependencies / limits
Core independently deployable. Paired local Slack plugin requires GatewayFactoryContext.inboundAttachments=1 and must be provisioned separately after this Core is activated. docs/inbound-attachments.md records storage, trusted local parent directories, size limits and retention. No automatic blob GC, no image decoder/malware scanner, no exactly-once or live Slack success claim.
Delivery
Source publication only at PR creation. Normal merge gates and GitOps remain required; build is not live activation.