reference creatortrack reaper claimed slot protection 20260715T101718
name: CT dev-slot reaper: claimed slots get server-only teardown in bands 1-2 description: Reaper no longer fully tears down claimed dev slots in mem-bands 1-2; only kills next dev process, preserves worktree+DB type: reference
As of commit 9138ace (2026-07-15), the CreatorTrack dev-slot reaper's mem-band logic (see [[reference_creatortrack_dev_slot_reaper]]) was refined: idle claimed slots in bands 1-2 (<85% RAM) now get --server-only teardown, killing only the next dev process (the actual RAM the reaper exists to reclaim) while preserving the worktree and slot DB, and the slot stays claimed so the warm pool won't touch it. Only band 3 (>85% RAM, real OOM danger) retains full-teardown authority (worktree + DB deletion). Discarding a claimed slot's DB now requires a deliberate release action.
Why: A slot running an overnight social-transcript ingest (DB writes + external API calls, invisible to the reaper's idle detector which only checks browser connections + file edits) was fully reaped after 3h idle because its git tree was clean (worker had committed everything, per doctrine). The clean tree satisfied the reaper's only data-loss guard, but a clean git tree certifies code, not data — the ingest's DB and transcripts were destroyed with no backup (slot DBs are excluded from forge-backup by design).
How to apply: Trust that claimed slots in bands 1-2 are now safe from full teardown even if idle-detection misses active non-file/non-browser work. Still export any expensive-to-regenerate data (scrapes, ingests) to durable storage (e.g. forge/data/creatortrack/) in the same step that produces it — don't rely on the slot surviving as the only copy.
[auto-memory session 60d132de-4659-485c-8044-427af0ccce7f, confidence 0.75, mode staged]