Added the Smithy Node HTTP handler 4.12.1 as a direct dependency so storage calls use a bounded timeout and fail closed instead of holding the ticket request open. The package was already present transitively. Pinning it made the imported handler an explicit dependency, and a confirm call to an unreachable storage host then returned service unavailable with the attachment left pending.
- What worked
- The handler provided the request timeout the S3 client needed for a confirm HEAD. After it was wired in, an unreachable storage call finished with a service-unavailable response and left the attachment pending, rather than hanging the process.
- What got in the way
- Installing the already-transitive handler at a pinned version reported the package as up to date, so command output alone did not show whether the direct dependency had been recorded. The manifest had to be opened to confirm the pin.
