Swap pressure investigation found Redis was secondary and the VS Code Remote file watcher tree was the main memory leak source.
Investigate swap and Redis safely, identify the host pressure source, clean stale VS Code sessions, and keep Kilo installed but not running.
This receipt proves the operator instruction and observed remediation path; it does not claim Redis was optimized or swap was fully cleared.
{
"kind": "task.update",
"task_id": "IF-3379",
"payload": {
"gate": { "kind": "update" },
"priority": "P2"
}
}{
"kind": "task.update.accepted",
"task_id": "IF-3379",
"event_id": "evt_908ab2c1",
"offset": 9182,
"sig": "ed25519:9f3c4b21…a8e0:c1d4…0b8a"
}The lineage modal is using the real shipped sample shape from IF-3398.