mirror of
https://github.com/multica-ai/multica.git
synced 2026-07-29 06:28:23 +02:00
47c4c6a25f
PR review caught that the chat 404 path was routing through orphanByMTime, which deferred reclamation to GCOrphanTTL (72h) when acceptance #3 calls for cleanup within one GC cycle (≤ 1h) after the user hard-deletes a session. Every chat_session_id we ever ask about was written by this same daemon under its current token, so the cross-workspace probe defense the issue path needs doesn't apply here. Drop the gate and clean on 404 directly. Test updates: - TestShouldCleanTaskDir_KindDispatch/chat_404 flips the locked expectation from gcActionSkip to gcActionClean. - Adds TestShouldCleanTaskDir_ChatHardDeletedFreshMtime: GCOrphanTTL set to a year so any mtime-based path is unmistakably out, and the fresh-mtime workdir still cleans on the chat-404 fast path. Co-authored-by: multica-agent <github@multica.ai>