Note

Medium Risk
Touches the orchestration projection pipeline’s transaction + filesystem cleanup paths; while mostly a refactor, mistakes could cause missed or overly-broad attachment deletions during thread delete/revert flows.

Overview
Refactors ProjectionPipeline to wrap projector apply functions and internal helpers in named Effect.fn blocks, improving traceability while keeping projector behavior the same.

Reworks attachment cleanup/prune side effects into shared helpers (including reusing a single attachments-root directory read per side-effect run) and ensures unsafe thread IDs are skipped in both delete and prune flows.

Adds a regression test that directly calls projectEvent for a thread.deleted event with an unsafe thread id (..) to confirm attachment/state directories aren’t removed, and marks the projection pipeline refactor as complete in docs/effect-fn-checklist.md.

^{Written by Cursor Bugbot for commit 9aa023c. This will update automatically on new commits. Configure here.}

Note

Refactor projection pipeline side effects with named Effect.fn helpers

• Wraps projection pipeline handlers and utilities in named Effect.fn(...) calls to improve traceability in Effect traces.
• Extracts removeDeletedThreadAttachmentEntry, deleteThreadAttachments, pruneThreadAttachmentEntry, and pruneThreadAttachments as named helpers from inline code in runAttachmentSideEffects.
• Behavioral Change: the attachments root directory is now listed once per runAttachmentSideEffects invocation and the result is reused across all deletions and prunes, rather than re-reading the directory for each thread operation.

^{Macroscope summarized 684160a.}