fix: pin the eager-503 default error_code to `not_ready` (Worldtree b2)

worldtree-dev finalized the #331 503 turn-launch error_code as `not_ready`
(re-pinned from internal_error; retryable, matching the /readyz 503 sense)
and re-froze the OpenAPI at 2.2.0 documenting the 409/503 statuses our
v0.18.3 mapping already handles. Tighten our fallback default from the
placeholder `turn_launch_unavailable` to the canonical `not_ready` (the
default only fires when the body omits error_code — the real code is
surfaced verbatim regardless). +1 test, suite 510 green.

NOTE: a full conversation-api-spec.md re-vendor to the b2 era is a separate,
larger pin-refresh (ratatoskr vendors the markdown spec, not the OpenAPI
JSON) — deferred, to bundle with the v1 coverage-audit / when personal is on b2.

This commit is contained in:

2026-06-30 13:26:14 -07:00

parent b2e4901264

commit e4317f6a73

4 changed files with 20 additions and 3 deletions

									
										uv.lock
									
Generated

		+1
		-1
	
												View File
												
				@@ -1052,7 +1052,7 @@ wheels = [

				[[package]]

				name = "ratatoskr"

				version = "0.18.3"

				version = "0.18.4"

				source = { editable = "." }

				dependencies = [

				    { name = "httpx" },

fix: pin the eager-503 default error_code to not_ready (Worldtree b2)

fix: pin the eager-503 default error_code to `not_ready` (Worldtree b2)