Repository navigation
Fix orchestration reliability in Development - #1908
Merged
Paul Lizer (paullizer) merged 9 commits intoNov 9, 2026
Merged
Paul Lizer (paullizer) merged 9 commits into
Paul Lizer (paullizer) merged 9 commits into
Conversation
Keep answers focused, disclose retained findings and evidence on demand, and add content-free debug publication correlation. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
…nce-experience Unify saved findings and evidence in the existing Sources inspector
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 <223556219+Copilot@users.noreply.github.com>
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 <223556219+Copilot@users.noreply.github.com>
…e-planning-failures Fix Orchestrate planning contracts and native document handoffs
Reuse canonical package imports so native document guards receive the same reader class as discovery. Preserve source isolation and recovery policy while adding safe action-stage failures and real-loader format/startup regressions. Pin the required template parser, add the CI gate, and update documentation and release pages for 0.261.421. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
…ion-stability Fix canonical plugin discovery for document orchestration
Repair unambiguous selected-source wiring with two shared planner corrections, route native Word comments through the authorized shared reader and retained citations, and repair malformed checker evidence labels without weakening grounding. Add content-free correlated diagnostics, regressions and documentation for v0.261.422. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Preserve Development changes and exclude the separate saved-findings Sources inspector work. Include the required plan-contract, native action source-binding and canonical plugin-loader prerequisites with the reliability fixes. Record v0.261.423 validation and retain published history without force-pushing. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Paul Lizer (paullizer)
merged commit Nov 9, 2026
6fd290b
into
microsoft:Development
13 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
paullizer-react-v2-ui. This PR targetsDevelopment, preserves its existing UI and release notes, and excludes the separate saved-findings/Sources inspector work. It includes the required earlier plan-contract, authorized action-source binding, and canonical plugin-loader prerequisites missing from Development.The published head is
a229ed79cc92a232e40b4ae804a8faaa4880ec02. This is a normal integration merge with Development commit4dd6d80230fe60e3cbfe8544d1d52308a14a7387, not a history rewrite. The PR has 57 target-relative changed files. The original merge remains untouched. The branch is published from the existingpaullizer/simplechatfork because direct push permission to the upstream repository is unavailable; the base repository remainsmicrosoft/simplechat.Linked issue
N/A — no associated issue was requested. The original PR is referenced above as a non-closing target-correction reference.
Release Notes & Latest Features
Is this visible to end users?
Is this admin-facing (Admin Settings, governance, deployment, config)?
Should this become a Latest Feature card?
Screenshot needed for the card?
Release notes and Latest Feature cards were deliberately left unchanged during this target correction.
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 changedApplication version: 0.261.422 → 0.261.423. No deployer files changed.
Testing / validation
The counts below overlap and are not a live end-to-end success-rate measurement.
python .\scripts\check_cosmos_response_boundaries.py --run-contractsnpm --prefix .\application\v2_ui ci --no-audit --no-fundtscbuild failure. No new frontend dependency/lockfile changes relative to Development.npm --prefix .\application\v2_ui run buildnode --check .\application\single_app\static\js\chat\chat-citations.jspython .\scripts\build_docs_inventory.pypython .\functional_tests\test_docs_app_surface_coverage.pypython .\functional_tests\test_docs_site_quality.pygit --no-pager diff --checkandgit --no-pager diff --cached --checkCombined pipeline command — 515 passed:
Local browser command — 49 passed:
The synthetic action-browser fixture now returns the existing pending-question endpoint's empty response only for its exact origin, GET method, path, and conversation. Unexpected requests still abort and fail, and browser-error assertions remain active. No production controller was changed to make these tests pass.
Route-policy command — 30 passed:
Published-commit guardrails — passed:
The unchanged execution-module Cosmos reviews were restored from Development only after proving exact whole-file and owner/module fingerprint equality. Changed storage owners retain their concrete runtime evidence; the full network-blocked gate subsequently passed.
Not performed: deployment, live beta replay, or a full Jekyll build. Source-level documentation checks passed. The original v0.261.422 validation and its unrelated historical baseline limitations are recorded separately in the fix document; they are not presented as the current Development results.
Documentation
Updated the orchestration, action-binding, and document accessibility feature documentation; native-comment action and logging references; and
docs/explanation/fixes/ORCHESTRATION_RELIABILITY_PIPELINE_FIX.md. The fix document records v0.261.423, required prerequisites, excluded UI work, and current Development validation. Release notes remain unchanged as noted above.Security checklist
@swagger_route(security=get_auth_security())sanitize_settings_for_user()No new Flask routes are introduced. Current source authorization and committed-evidence integrity are rechecked when citations reopen. Word author/comment/anchor text is rendered as inert text. Planner corrections never broaden permissions or replace explicit source selections, and diagnostic properties do not include prompts, raw failed references, source text, filenames, document IDs, or provider messages.