ci(spec-sync): scope the 504 timeout remediation per endpoint in the wiring prompt - #130
Merged
Merged
Conversation
…r endpoint The prompt said "route a 504 through raise_if_sync_timeout" without noting the helper's message was parse/extract-specific, so a wired build_schema inherited a 504 hint pointing at the wrong async resource. Instruct the AI to pass the endpoint's own `jobs_resource` (extending the helper if needed) so future regenerations name the correct *_jobs route. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow-up to the Copilot finding on #129: a wired `build_schema` reused `raise_if_sync_timeout`, whose message was hardcoded to `parse_jobs`/`extract_jobs` — so a build-schema 504 pointed users at the wrong async resource.
The code fix lands on the #129 branch (parameterize `raise_if_sync_timeout` with a required `jobs_resource`, pass the correct route at every call site). This PR is the pipeline half: the V2 wiring prompt now tells the AI to pass the endpoint's own `jobs_resource` (and extend the helper if it lacks per-endpoint support), so future regenerations don't reintroduce the wrong remediation.
Prompt-only change; no SDK surface touched.