What changed, provider status and blind spots

When something breaks, the first questions are what changed, whether a provider you depend on is down, and whether the answer sits in a system Firefight cannot see. Halon now answers all three before it guesses. See What changed, provider status and blind spots.

What changed. One list, newest first, of everything that changed around a resource, a service or the whole workspace, from the map, live updates, changes made through Firefight, and the provider's own builds, deploys and CI runs. It is in each resource's panel on the map and on the incident page, where Read runs now reads the provider's runs as you.

Provider status. When logs or errors show failures calling a provider's address, such as timeouts to a payment API, Halon reads that provider's public status page straight away and says whether it reports an outage, before blaming your own code. Agents use check_status_page.

Blind spots. When a question needs a system you have not connected, such as an outside sign-in provider, Halon names it, says where it saw your apps use it, and links to connect it instead of guessing. Agents list these with blind_spots.