Repository navigation
fix: share resilient provider execution and validated candidate publication - #350
Merged
Merged
Conversation
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.
Provider requests currently fail immediately on recoverable connection failures, and interrupted streams can lose diagnostic causes and consumption evidence. Add a portable
wiki-graph-runtimepackage shared by core and job: bounded transport recovery over full response consumption, safe nested error diagnostics, cancellation-aware budgets, resource leases, and bounded concurrency.JSON repair now has one implementation and a shared deadline. Candidates publish caches only after business validation; Summary publishes the selected revision. Quality gates distinguish legitimate empty output from all-failed fallback. Usage records real attempts independently of acceptance, and progress has explicit scope/phase/unit/attempt boundaries. Existing core retry configuration and public entry points remain compatible; timeouts now bound the full request including retries. POST retries may duplicate work and billing.
The runtime is included in workspace builds, portable checks, release order and isolated package-install verification. Host-specific credentials, cloud storage and state persistence remain outside this public package. Adapter contracts and limitations are documented in
docs/provider-runtime.md.Validation:
pnpm lint:fix,pnpm verify, workspace build andpnpm smoke:pack-installpassed.