9d4ad84 (read-only app password -> 403) and e6959e6 (bounded HTTP clients on
the token path) both landed with no test at all. These are the ones a
regression would be silent in: a revert of either leaves every existing test
green.
Each test was mutation-verified against the defect it claims to catch, in a
throwaway worktree, and required to fail:
* revert ResolveHoldDID to http.DefaultClient -> SlowHoldIsCutOff fails
* revert getServiceAuth to http.DefaultClient -> SlowPDSIsCutOff fails
* NewSessionValidator back to &http.Client{} -> ClientsAreBounded fails
* drop the InsufficientScope classification -> IsClassified fails
* drop the handler's errors.Is branch -> Returns403 fails, and the
body it returns is the exact retry-inviting 503 UNAVAILABLE the commit
exists to remove
The slow-path tests wait on an outer deadline rather than on the call itself.
With an unbounded client these calls never return, so a test that simply
awaited the result would hang the suite instead of failing it, and a hung
suite reports nothing.
The client caps are asserted twice on purpose: once as a field value, which
guards the production 10s/15s numbers, and once functionally, which proves the
call site routes through the bounded client rather than merely declaring one.
Neither half catches the other's regression.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01SeaUS5AFPX9gqCahoLRMRh
