Repository navigation
Improve orchestration UX and semantic answer checking - #1899
Merged
Paul Lizer (paullizer) merged 1 commit intoNov 6, 2026
Conversation
Keep end-user progress quiet, collapse answered questions, separate preparation from checking, and apply feedback-informed corrections. Preserve authorized image and native workbook evidence with safe retained-check recovery and regression coverage. Co-authored-by: Copilot App <[email protected]>
Paul Lizer (paullizer)
merged commit Nov 6, 2026
0452e9c
into
microsoft: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
completeness_requirements_changedfailures: preserve canonical obligation identities without requiring verbatim checklist descriptions. Show preparation, deterministic validation, and semantic review as separate stages; expose Auto / On / Off for optional semantic review through approved plan edits.Linked issue
N/A - no linked issue.
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 remain unchanged pending approval. Existing administrative correction limits and semantic-review disablement remain outer bounds; plan choices cannot override them.
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.415->0.261.416. No deployer changes.Testing / validation
python .\scripts\check_cosmos_response_boundaries.py --run-contracts- passed: 2,005 tests and 431 subtests with Cosmos network access blocked; 1,094 owners, 425 doubles, zero review gaps.python -m pytest .\ui_tests\test_v2_orchestration_recovery.py .\ui_tests\test_v2_orchestration_quiet_activity.py .\ui_tests\test_v2_orchestration_m365_inline_approval.py .\ui_tests\test_v2_orchestration_m365_recovery.py -q -x- passed: 84 tests.python -m pytest .\ui_tests\test_task_completeness_ui.py -q- passed: 13 tests, including classic report versions 1/2, historical inspection, keyboard accessibility, and inert markup.python -m pytest functional_tests\test_orchestration_attachment_native_evidence.py functional_tests\test_orchestration_selected_source_planning.py functional_tests\test_orchestration_search_result_integrity.py functional_tests\test_orchestration_source_kind_planning.py functional_tests\test_chat_vision_current_turn.py -q --disable-warnings --basetemp=.test-artifacts\orchestration-native --tb=short- passed: 115 tests.python .\functional_tests\test_docs_app_surface_coverage.py- passed: 7/7 checks.python .\functional_tests\test_docs_site_quality.py- passed: 6/6 checks.git --no-pager diff --check- passed before committing.Quiet activity was inspected at 1440px/light and 390px/dark without overflow. Scripted provider responses verify control flow and evidence handoff, not an empirical semantic-accuracy score. Native workbook coverage remains limited to authorized readable material and is explicitly partial when resource limits apply.
Known unrelated limitation:
python .\ui_tests\test_v2_orchestration_composer.pyfails an older public-source tooltip expectation at line 291; the committed base already uses different wording, and the legacy harness lacks an existing document-sources endpoint stub. Left unchanged. No production deployment or replay of the investigated conversations was performed.Documentation
Added
docs/explanation/fixes/ORCHESTRATION_QUIET_ACTIVITY_AND_SEMANTIC_REVIEW_FIX.md; updated orchestration administration, plan-review guidance, and chat-control reference. Documentation inventory remains current.Security checklist
@swagger_route(security=get_auth_security())sanitize_settings_for_user()No new Flask routes or raw settings responses were introduced. Public checking reports omit candidates, prompts, and raw evidence. Attachment access, masking, linkage, and revision are rechecked around reads; existing approval and external-effect recovery fencing remains intact.