Endpointprobe: HTTP Desk

You are about to ship an API change and someone asks the question that matters: does the new build answer exactly like the old one, or only close enough to fool a glance? Endpointprobe: HTTP Desk exists for that moment. You describe a scenario once — method, path template, headers, assertions — and point it at two environments, baseline and candidate. The workbench replays both sides and reads back a semantic verdict instead of a wall of raw text. The diff engine compares structure, not noise. Declare a timestamp, request id, or server-date header volatile and it is canonicalized out of the comparison — with every normalization disclosed on screen beside the verdict, so the proof stays honest. Stored tokens live in the device Keychain. Previews and exports use placeholders for bound secrets. Before writing a checksummed evidence bundle, the app checks for bound secret values in text,…