the failure that looked like the network

A command failed with a timeout. Not an error and not a rejection: an immediate, universal timeout. The obvious reading is the network, and the obvious reading was wrong. The settings loader had a default value that only applied while parsing a configuration file. When the file was absent the value stayed at zero, so every request expired before it was sent.

That one line explains a class of incidents that had been costing afternoons across several tools: a stale build, an address resolved from a chain that had reached a dead default, and a bare timeout with no context. Three invisible causes, one visible symptom.

The response was not a patch but a diagnostic surface. A doctor command performs a real authenticated round trip and then reports each link: which element of the resolution chain supplied the address, how long the attempt took, whether name resolution and the encrypted channel came up, and one concrete next step per failure class. Build identity is stamped into the version output with its build time and a marker for uncommitted work, so the question of whether we are running the code we just wrote stops being a guess.

An address silently baked into an artefact is the same bug in another costume: fresh identities were picking up a test-bench default and writing it into a production credential, which would have sent every later call to the wrong place.

What this proves: diagnosis was built as a product surface rather than left to experience, and a default value is treated as a decision that can fail rather than a placeholder that cannot.