Bound Weather API response diagnostics

docs/integrations/weatherapi.md

@@ -138,9 +138,10 @@ It does not retry other HTTP statuses, malformed envelopes, missing data, or
 payload decoding failures. A canceled context also stops an in-progress retry
 delay.
 
-The adapter reads at most 10 MiB from one response body. A non-2xx response,
-request construction failure, read failure, or decode failure includes endpoint
-context in its error.
+The adapter accepts response bodies up to 10 MiB and rejects larger bodies
+before decoding. A non-2xx response reports its relative endpoint and status,
+without including upstream response text. Request construction, response-limit,
+read, and decode failures include endpoint context in their errors.
 
 Retry counts and delays are adapter behavior rather than Weather API request
 parameters. Do not depend on a particular attempt count when implementing the

docs/internal/collect.md

@@ -16,6 +16,10 @@ API base URL, as weather-collection setup errors and fetch failures as
 bundle-collection errors. It does not retry, persist, select reports, derive
 facts, build modules, invoke Promptkit, or notify Distributor.
 
+Fetch failures retain Weather API endpoint context but do not project upstream
+response bodies into application-facing errors. Oversized response bodies fail
+collection before source decoding.
+
 ## Application Composition
 
 `internal/app` owns the narrow `Collector` interface used by workflow tests;