Skip to content

fix(runtime): negotiate unsupported provider temperature - #321

Closed
seonghobae wants to merge 2 commits into
feat/multilingual-organization-label-searchfrom
fix/orchestrator-temperature-runtime-pin
Closed

fix(runtime): negotiate unsupported provider temperature#321
seonghobae wants to merge 2 commits into
feat/multilingual-organization-label-searchfrom
fix/orchestrator-temperature-runtime-pin

Conversation

@seonghobae

@seonghobae seonghobae commented Aug 20, 2026

Copy link
Copy Markdown
Contributor

Buyer-visible gap

The pinned Compose runtime must tolerate provider deployments that reject an optional sampling temperature without weakening fail-closed provider handling.

Change

  • Pin the runtime image to ContextualWisdomLab/contextual-orchestrator#779 exact head cf4a4501fa5057f89b21cad5033c5925755cd150.
  • Record the immutable integration boundary in ADR 0083.
  • Keep the regression that synchronizes the Docker archive pin, ADR commit, and upstream provenance.
  • Do not select models locally, reimplement provider behavior, or copy credentials into LineageWeave.

Stack and verification

  • Stacked on feat: search verified multilingual organization labels #316 at current parent 05c83781c76a3dee4cbe7cfb6d6320b2209b77aa.
  • Current head 8fc493c0 after a normal parent restack.
  • Python suite: 776 passed, 16 skipped, 4 warnings.
  • Frontend lint, 168 tests, production build, Storybook, actionlint, and git diff --check passed.
  • The pinned Docker build and isolated runtime evidence were recorded on the unchanged feature commit; rerun the image gate on this exact head before release.

Protected reviews and exact-head Checks remain external merge gates.

@coderabbitai

coderabbitai Bot commented Aug 20, 2026

Copy link
Copy Markdown

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: e85249fc-04b7-4325-9692-4b514b98c950

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@seonghobae

Copy link
Copy Markdown
Contributor Author

@OpenCode review exact HEAD 2b4030a. Verify the immutable upstream pin, ADR synchronization, and provider-temperature fail-closed boundary. Full local suite: 776 passed; exact pinned live gpt-5.6-sol transport succeeded with temperature 0.2.

@seonghobae

Copy link
Copy Markdown
Contributor Author

@opencode-agent Please review exact current head 221f8be9bd27e164abf25fd08e14c429ffd7285b. The only follow-up after the fully verified runtime pin is a documentation-contract cleanup: cross-repository references now use linkable ContextualWisdomLab/contextual-orchestrator#779 form. Focused exact-head regression: 1 passed; git diff --check passed. The previous full-suite and live synthetic transport evidence remain behaviorally unchanged.

@seonghobae

Copy link
Copy Markdown
Contributor Author

@opencode-agent review exact current HEAD 221f8be. Review the provider temperature capability negotiation and Azure-compatible runtime boundary; publish a formal review.

@seonghobae

Copy link
Copy Markdown
Contributor Author

Superseded by #322 exact head 7b710453d27286c307986fb3b0bad4ac27d7c8af, which reuses this PR’s temperature pin commits, removes the backend embedding-selector exposure, adds orchestrator-owned embedding provenance, and pins the combined contextual-orchestrator#791 runtime. No open PR targets this branch, so keeping both would duplicate commits and CI work.

@seonghobae seonghobae closed this Aug 20, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant