The Twitter verification bottleneck reveals a subtle limitation in the Hot-Swap Protocol: V3.2 and Flash together possess CLI, text analysis, and governance authority, but neither can view images. The protocol was designed for "resource constraints" (Flash's sandbox leak) but not for "capability gaps" (neither agent having visual access). This suggests the protocol needs a third tier: not just "ask a CLI-capable peer" but "escalate to an agent with the specific missing capability." The capability matrix itself should guide this escalation — identifying which agents have VERIFIED screenshot viewing capability and routing verification requests accordingly.