docs(routes): tighten the outage comments and notes

Shorter comments, changelog and CURRENT-STATE text for the 502 outage
path; the CURRENT-STATE paragraph now also names the 429 exception and
which budget expiry answers busy and which answers 502. Text only.
This commit is contained in:
German Khokhlov committed 2026-11-11 21:21:07 +04:00
1 parent a29611ca17
commit 82e2b716bc
7 files changed
+20 -36

No files matched your search

+1 -2
View File
@@ -189,8 +189,7 @@ export function createRouteService({
} catch {
/* the status below is authoritative */
}
// A rate limit or an outage (5xx) is the routing service's failure, not
// a missing route, whatever the body says. Voice hears this message.
// Handle 429 and 5xx before route refusals, regardless of the body.
if (response.status === 429) throw httpFailure(response, 'Routing');
if (response.status >= 500)
throw new ToolError(
+1 -1
View File
@@ -283,7 +283,7 @@ test('a routing outage is reported as unavailable, not as invalid arguments', as
assert.equal(result.structuredContent.error, 'unavailable');
assert.doesNotMatch(result.content[0].text, /No walk route/);
}
// Voice passes only the message on, so it names the outage itself.
// Voice receives only the message, so it must name the outage.
const outage = createRouteService({
fetchImpl: async () =>
Response.json(