Problem
excludeChannels fully quarantines a conversation/channel going forward — no context injection, no memory writes, no memory tools for sessions in that channel. But it's a forward-only gate: content synced or written before a channel was added to the quarantine list isn't retroactively removed from Hyperspell. So turning on quarantine for a channel stops new leakage but doesn't clean up whatever already made it into searchable memory beforehand — a real, currently-open situation, not a hypothetical.
What we could do
At minimum, document this limitation clearly wherever excludeChannels is described, so operators don't assume enabling it retroactively scrubs history. Ideally, provide an explicit opt-in cleanup path (a CLI command or documented manual process) to find and remove already-synced content originating from a channel that's since been quarantined.
How we'd test it
Quarantine a channel that already has synced content from before the quarantine was added. Confirm (a) no new writes/injections happen for that channel going forward, and (b) whether the pre-existing content is still retrievable via hyperspell_search afterward — document the actual current behavior either way, then verify a cleanup path (if built) actually removes it.
Problem
excludeChannelsfully quarantines a conversation/channel going forward — no context injection, no memory writes, no memory tools for sessions in that channel. But it's a forward-only gate: content synced or written before a channel was added to the quarantine list isn't retroactively removed from Hyperspell. So turning on quarantine for a channel stops new leakage but doesn't clean up whatever already made it into searchable memory beforehand — a real, currently-open situation, not a hypothetical.What we could do
At minimum, document this limitation clearly wherever
excludeChannelsis described, so operators don't assume enabling it retroactively scrubs history. Ideally, provide an explicit opt-in cleanup path (a CLI command or documented manual process) to find and remove already-synced content originating from a channel that's since been quarantined.How we'd test it
Quarantine a channel that already has synced content from before the quarantine was added. Confirm (a) no new writes/injections happen for that channel going forward, and (b) whether the pre-existing content is still retrievable via
hyperspell_searchafterward — document the actual current behavior either way, then verify a cleanup path (if built) actually removes it.