Root cause of the 75-item week-long backlog USR369 found live (08/12-08/19 accumulation across most of the 11 systems): classify_actionable() in verify_lib.php only blocks on literal keywords (ACTION -- / MANDATORY / REQUIRED / URGENT / MUST / STANDING DUTY). Routine session-close broadcasts, bug reports, and even a real corrupted-file warning (T-OUTBOUND-TZ/K371) never contain those words, so the gate silently passed every time and nothing ever forced a resolve call. Both suggested fixes from an earlier community transfer (K343 -- real-path resolve URL, GET fallback on resolve/deliver) were confirmed already live and working before I touched anything -- this was a separate, deeper gap. Added two new triggers to actionability_gate(): AGE (any pending item >48h, matches existing SOP-HANDOFF.md staleness standard) and VOLUME (total pending >20). Either now forces blocking regardless of keyword content. Backed up verify_lib.php first given its K371 corruption history, syntax-checked via bootstrap before deploy, confirmed both OPEN.php and SYNC.php still return 200/valid JSON post-deploy.