Repository navigation
Fix Orchestrate planning contracts and native document handoffs - #1904
Merged
Paul Lizer (paullizer) merged 2 commits intoNov 7, 2026
Merged
Paul Lizer (paullizer) merged 2 commits into
Paul Lizer (paullizer) merged 2 commits into
Conversation
Align planner defaults and output contracts, enforce native document action bindings through retention and citations, and add content-free debug checkpoints and authenticated end-to-end coverage. Bump the application version to 0.261.419. Co-authored-by: Copilot App <[email protected]>
Retain both native document-action diagnostics and saved-findings telemetry when resolving the logging allowlist conflict. Advance the integrated application version to 0.261.420 and synchronize current-version headers. Co-authored-by: Copilot App <[email protected]>
Paul Lizer (paullizer)
merged commit Nov 7, 2026
a974d36
into
paullizer-react-v2-ui
12 checks passed
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.
Summary
0.261.420(original implementation:0.261.419).Retained native sources keep their existing provenance and conversation/run access semantics; current integration access checks remain in place. Native metadata is not a conformance guarantee. No new route, setting, extraction engine, browser runtime asset, deployment, or live conversation change is introduced by this fix.
The original generic production failures did not retain their rejected model JSON. This PR fixes reproduced shared contract/integration gaps without claiming an exact historical field-level cause for every failed turn.
The latest React V2 base is integrated in merge commit
c8a1b950c. The logging conflict was resolved by preserving both the native orchestration diagnostics and the base's saved-findings correlation fields; the base's Sources inspector behavior is unchanged by the resolution.Linked issue
N/A. This work was intentionally tracked in the session without creating an issue.
Release Notes & Latest Features
Is this visible to end users?
Is this admin-facing (Admin Settings, governance, deployment, config)?
Uses the existing debug-logging switch; no new admin setting or deployment change.
Should this become a Latest Feature card?
Screenshot needed for the card?
Version bump
application/single_app/config.pyVERSIONthird segment bumped, or not needed because this is docs-onlydeployers/version.txtbumped, or not needed becausedeployers/was not changedIntegrated application version:
0.261.419->0.261.420. The original implementation bumped0.261.418->0.261.419; current-version headers now reflect the integrated version while implementation-version metadata remains historical. No deployer files changed.Testing / validation
Counts are separate, overlapping selections, not a combined total. The full original gates are recorded historical results, not a claim that all were rerun for this merge. Broader unrelated baseline failures were reproduced against pre-fix production code and are documented in the fix explanation; they are not suppressed or counted as passing. Validation does not claim live-model accuracy or a deployed success rate.
Exact commands and results
Python integration commands used the application and functional-test directories on
PYTHONPATH.Post-integration production V2 build - passed; generated output isolated in test artifacts:
Post-integration browser selection - passed (75 tests):
The saved-analysis fixture initially lacked its documented production CSS build artifact. Building it with the documented command above resolved setup; no test was changed or skipped to bypass that failure.
Post-integration documentation - coverage passed 7/7 and quality passed 6/6:
Post-integration committed PR diff - passed:
Original related regression selection - passed (507 tests, 184 subtests):
Original full reviewed SDK gate - passed (2,015 tests, 431 subtests):
Inventory review - passed (1,094 owners, 425 doubles, zero review gaps):
Original browser selection - passed (16 tests):
Original route policies and logger initialization - passed (31 tests):
Original production V2 build - passed; generated output isolated in test artifacts:
Original documentation - inventory regenerated; coverage passed 7/7 and quality passed 6/6:
The regenerated application-surface inventory matched the committed content; no surface item was added or renamed.
Original whitespace - passed before committing:
Documentation
Release notes were left unchanged pending review. Updated action access, Document Search, planning recovery, and logging references. Added
docs/explanation/fixes/ORCHESTRATION_PLANNER_CONTRACT_RECOVERY_FIX.mdwith root causes, behavior, full-path validation, privacy boundaries, and baseline limitations; its integrated-version note records the merged logging contracts and validation.Security checklist
@swagger_route(security=get_auth_security())sanitize_settings_for_user()No new routes or settings-rendering paths were added. Existing route policies, action restrictions, current source authority, conditional SDK writes, and exact-data completeness checks remain enforced. Debug checkpoints exclude raw source/model/provider payloads; session investigation artifacts and generated browser-test assets are not included.