diff --git a/.storkit/work/1_backlog/453_bug_agent_pty_crashes_with_fatal_runtime_error_on_restart_after_gate_failure.md b/.storkit/work/1_backlog/453_bug_agent_pty_crashes_with_fatal_runtime_error_on_restart_after_gate_failure.md
index c8ed2b2e..9cce9738 100644
--- a/.storkit/work/1_backlog/453_bug_agent_pty_crashes_with_fatal_runtime_error_on_restart_after_gate_failure.md
+++ b/.storkit/work/1_backlog/453_bug_agent_pty_crashes_with_fatal_runtime_error_on_restart_after_gate_failure.md
@@ -25,7 +25,9 @@ The root cause is unknown. It is NOT caused by zombie process accumulation (that
 - Story 359 — Docker security hardening (`cap_drop: ALL`, added back only `SETUID`/`SETGID`) — could affect PTY allocation
 - Story 329 — Docker/OrbStack evaluation spike (first crash was on this story's mergemaster)
 
-Possible areas to investigate: changes to the agent runtime abstraction in story 343, Docker capability restrictions from story 359 affecting PTY allocation, or environment state left behind by the previous agent session.
+**Ruled out:** Docker capability restrictions (cap_drop: ALL) — tested by temporarily removing all cap_drop/security_opt; crash still occurs.
+
+Remaining areas to investigate: changes to the agent runtime abstraction in story 343, or environment state left behind by the previous agent session.
 
 ## How to Reproduce