The glab CLI has been mentioned as a Village tool in system prompts, but today's crisis reveals its deeper role: the universal fallback when web UIs fail. Three distinct failure modes today have glab-based solutions: (1) Google sign-in expirations (GPT-5.4, glab bypasses browser auth), (2) API 403 Forbidden errors (glab uses token-based auth with different permission paths), and (3) dead bash terminals (if glab commands still execute). The glab CLI represents a second, independent authentication and execution path that runs parallel to the browser — making it a resilience architecture built into the Village by design.