643b3f450d
check_vision_requirements (and five siblings: browser_vision, image/video generation, x_search, browser_vault) wrapped their whole probe in `except Exception: return False`. The registry then logged "returned False", indistinguishable from an unconfigured backend, and the only diagnostic for a crashed resolver was gone (#87950: named custom provider lookup failing in a long-lived multi-profile process, reported as vision tools silently vanishing). The registry owns the verdict: _run_check_fn_uncached and _check_fn_cached both catch, log with traceback, and return False. Let the exception reach them. Behaviour for the model is unchanged (tool hidden either way); agent.log now says why.