Repository navigation
Integrate React V2 into Development (v0.261.419) - #1903
Merged
Paul Lizer (paullizer) merged 2236 commits intoNov 7, 2026
Merged
Conversation
Preserve both the upload status fix and the base branch's saved-memory resolution changes. Refresh this fix's version references and verify the combined regressions, browser workflows and storage inventory. Co-authored-by: Copilot App <[email protected]>
Preserve the base memory-resolution changes and both sets of reviewed Cosmos boundaries. Resolve the application version conflict at 0.261.351 and align connector test/documentation headers. Post-merge checks passed: 219 Python tests, 5 subtests, 37 client checks, and 26 browser cases. Co-authored-by: Copilot App <[email protected]>
…stigation Add shared credential-safe SQL connection diagnostics
Preserve incoming SQL diagnostics alongside document status classification and refresh the fix's version references and integration evidence. Co-authored-by: Copilot App <[email protected]>
Retain the upstream SQL diagnostics and both branches of owner-runtime regression evidence for the unchanged plugin storage owners. Reconcile the shared module fingerprint and version 0.261.354. Combined validation passed 275 Python tests, 37 client checks, and 26 browser cases; inventory review has zero gaps. Co-authored-by: Copilot App <[email protected]>
Request JSON for shared V2 and classic chat uploads, and honor JSON negotiation for idle-expired sessions. Preserve authorization, idle activity semantics, drafts, and explicit-only retries. Add functional and browser regressions, documentation, and version 0.261.351. Co-authored-by: Copilot App <[email protected]>
Resolve the application version conflict at 0.261.354 and align upload regression and fix documentation versions. Co-authored-by: Copilot App <[email protected]>
Fix credential-clear intent in OpenAPI and MCP action tests
…stigation Fix document status classification across uploads and workspaces
Fix multipart upload authentication response negotiation
Synchronize recovery conversation identity before preflight so delayed React cleanup cannot cancel a valid first send. Preserve stale-context protections and add runtime and browser regressions. Co-authored-by: Copilot App <[email protected]>
Save independently encrypted chat credentials, preserve source grants across access-token expiry, and add confirmed chat disconnect without changing workflow access. Document the one-time reconnect migration and bump the application to 0.261.355. Co-authored-by: Copilot App <[email protected]>
…igation Fix V2 first-agent-message context race
Persist Microsoft 365 chat connections across sign-ins
Resolve placeholder inline source labels from exact message-scoped citation IDs, retain document citation metadata at React stream completion, and cover saved and streamed answers in both clients. Co-authored-by: Copilot App <[email protected]>
Persist active status on creation and apply missing-only compatibility defaults to directory and membership response rows. Preserve explicit restrictions and saved visibility choices, add regression coverage, refresh storage contract evidence, and bump to 0.261.355. Co-authored-by: Copilot App <[email protected]>
…estigation Fix public workspace missing-status chat visibility
Keep action preflight bound to its send's own conversation adoption while rejecting genuinely stale contexts and preserving unsent drafts without replay. Add credential-safe connection context and UI correlation references without changing SQL authentication or retry policy. Co-authored-by: Copilot App <[email protected]>
Provide authorized attachment identities and bounded spreadsheet schemas to planning, repair contradictory source-content questions, and fence native execution against changed source revisions. Add complete-source export, analysis, chart and clarification regressions and documentation for v0.261.355. Co-authored-by: Copilot App <[email protected]>
Keep the incoming synchronous conversation subscription and delegate it to the full recovery context owner. Preserve fail-closed selected-agent creation cancellation, unsent draft restoration, and already-admitted background behavior. Align the overlapping regression with the approved preflight contract and advance the application to 0.261.356. Co-authored-by: Copilot App <[email protected]>
Resolve the UUID factory through its module at context creation, cover post-import factory changes with a scoped regression, and retain Playwright fixtures through explicit module exports. Record validation and advance the application to 0.261.357. Co-authored-by: Copilot App <[email protected]>
Preserve pytest's name-based fixture discovery while making shared fixture exports explicit to static analysis. Bump the application patch version and document the review follow-up. Co-authored-by: Copilot App <[email protected]>
…estigation Use matching filenames for untitled document citations
Merge origin/paullizer-react-v2-ui at d8dd6c1, preserving the selected-source planning changes and newer application version 0.261.356. Validation: V2 production build, 111 focused regressions, 137 browser tests and zero-gap Cosmos inventory passed. The broader Python selection reproduced one existing M365 notification-fixture import failure with test and application dependencies identical to base; no tests were skipped or weakened. Co-authored-by: Copilot App <[email protected]>
Fix V2 chat preflight ownership and extend safe SQL diagnostics
Merge origin/paullizer-react-v2-ui at 7ecd3bf. Retain the newer incoming application version 0.261.357 and align selected-source test/documentation headers without changing the feature's original implementation version. Validation: 253 Python tests, 58 incoming browser tests, V2 production build, direct Node recovery-owner contracts, syntax/whitespace checks and zero-gap Cosmos inventory passed. Four broader new-chat fixture teardown errors were reproduced with all V2 source and UI tests identical to base; no assertions or tests were weakened. Co-authored-by: Copilot App <[email protected]>
Supply the SDK-required backup intent through the shared Azure Files client and report credential-safe provider failures across connection tests, browsing, and sync. Add real-SDK regressions and document access semantics. Co-authored-by: Copilot App <[email protected]>
Preserve both SQL and Azure Files diagnostic references and advance the application and Azure Files fix metadata to 0.261.358. Co-authored-by: Copilot App <[email protected]>
…ation-investigation Fix selected-source context across orchestration planning
Use the shared document citation pipeline to preserve evidence references through orchestration composition, persistence, and reload. Add backend and V2 browser regressions and bump the application to 0.261.356. Co-authored-by: Copilot App <[email protected]>
…ction Fix Excel comment content and add scalable table-aware inspection
Route native Foundry models through their supported inference APIs while preserving discovery endpoints and Custom gateway contracts. Preconfigure canonical model identity from built-in selections, add MAI request and authentication compatibility, and cover mixed-model clients and metadata consumers. Co-authored-by: Copilot App <[email protected]>
Integrate the latest base document-index, Excel inspection and conversation-menu changes while retaining automatic Foundry model routing. Combine release notes and tabular test metadata, and align the pending feature release at 0.261.410. Co-authored-by: Copilot App <[email protected]>
…tions Add automatic Foundry routing and Microsoft MAI support
Co-authored-by: Copilot App <[email protected]>
Co-authored-by: Copilot App <[email protected]>
Add guided follow-up questions and safe local-agent continuation
Align Analyze option contracts, retain selected sources through bounded plan correction, and add privacy-safe debug diagnostics while preserving Analyze and pre-plan inspection. Update documentation and application version to 0.261.411. Co-authored-by: Copilot App <[email protected]>
Resolve the application version overlap at 0.261.413 and align recovery test/documentation headers. Preserve guided-question support and verify the combined document-planning and guided-input behavior. Co-authored-by: Copilot App <[email protected]>
…failure Fix picked-document orchestration planning and debug diagnostics
Keep pending attachments scoped to their original conversation, reject stale async updates and sends, and restore document filenames. Include regression coverage, documentation, and application version 0.261.411. Co-authored-by: Copilot App <[email protected]>
Resolve the application version conflict at 0.261.414, preserve incoming guided-question support and document planning recovery, and synchronize the strict shared API fixture with current pending-question read contracts. Co-authored-by: Copilot App <[email protected]>
…ment-isolation Fix V2 attachment leakage between conversations
Persist accepted questions before planning, continue authorized Auto work server-side, and restore turn state after navigation or reload. Fixes #1893 Co-authored-by: Copilot App <[email protected]>
Preserve guided questions, selected-document planning recovery, and conversation attachment isolation alongside durable planning. Reconcile runtime-backed SDK inventory reviews, align integration fixtures, and advance VERSION to 0.261.415. Co-authored-by: Copilot App <[email protected]>
…ersistence Fix lost orchestration turns after navigation and refresh
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]>
…experience Improve orchestration UX and semantic answer checking
Keep confirmed task progress distinct from transport uncertainty, resolve native annotation citations against retained authorized evidence, and correct the thought cleanup call contract. Add regression coverage and related documentation for version 0.261.417. Co-authored-by: Copilot App <[email protected]>
Fix orchestration progress, workbook citations, and message cleanup
Stabilize application-owned review obligations, ground checking in the original message, and add narrowly scoped Auto recovery for checker errors. Preserve strict content, source-access and required-output gates, show truthful plan validation outcomes, and update coverage and documentation for version 0.261.417. Co-authored-by: Copilot App <[email protected]>
Resolve the shared UI-test version header, retain upstream task/phase progress and native-citation changes, and align review recovery with application version 0.261.418. Verified 196 functional tests and 111 UI tests plus typecheck, builds, documentation and SDK inventory checks. Co-authored-by: Copilot App <[email protected]>
…w-failure Fix orchestration review contracts and context-only recovery
Preserve both branch histories and their fixes, resolve the integration conflicts, and validate the combined application at version 0.261.419. Co-authored-by: Copilot App <[email protected]>
Contributor
There was a problem hiding this comment.
CodeQL found more than 20 potential problems in the proposed changes. Check the Files changed tab for more details.
Preserve late admin conflict protection, rebuild recovery editor routes with encoded identifiers, and remove unused bindings. Add focused regression coverage and document the remaining broader validation gaps. Co-authored-by: Copilot App <[email protected]>
Pin the frontend manifest to existing resolved versions and keep lockfile changes limited to its root declarations. Represent screening joiners with visible source escapes while retaining exact runtime values and coverage. Add focused regressions and version 0.261.421 fix/release documentation. Keep the mixed CodeQL findings and broader V2 validation gaps for human review. Refs PR #1903. Co-authored-by: Copilot App <[email protected]>
Correct the proven PR-introduced CodeQL side-effect cluster in one group-agent contract module. Execute all HTTP requests before assertions while preserving all 153 checks, request methods, arguments, and expected comparisons. Add normal/optimized cold-process regressions covering 12 scenarios and 49 request/status checks per mode, plus version 0.261.422 documentation. Preserve the published static-security and review-comment fixes. Refs PR #1903 and CodeQL check run 128260505956. Co-authored-by: Copilot App <[email protected]>
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-uiintoDevelopmentthrough a history-preserving merge, carrying forward the React V2 interface and its orchestration, workspace, document, and administration capabilities without changing interface rollout defaults.main, retain the React source branch, and leave Staging/main promotion outside this PR. Retarget the two pending React PRs only after this integration lands.Integration commit:
783153c1af61b52cb7236a63066be1a422abd3de.Its parents are React
34df8404ab9e20e51ffaf9d98ea40d75a18570e8and Developmentf4e186401b58e284ee9b626aa84c903f69ea100b; both ancestry checks passed.Linked issue
N/A - this integration PR is the tracking item, as requested.
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?
The integration preserves the source branch's feature catalog rather than adding a second promotion-only 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 changedApplication:
0.261.418->0.261.419. The integrated deployer changes already carry1.0.37versus Development's1.0.32; reconciliation adds no deployer changes relative to the React input.Testing / validation
1.109.1, and Cosmos4.9.0. In the SDK-dependent commands below,$pythonwas.\.test-artifacts\integration-venv\Scripts\python.exe; that task-local environment was removed after validation.6.0.3and test-only Uvicorn0.52.0, rather than the declared6.0.2and0.50.2. Clean pinned CI is required before merge. The shared host SDK was not changed.npm --prefix .\application\v2_ui run buildnpm --prefix .\application\v2_ui run build -- --outDir ..\..\ui_tests\artifacts\orchestration-plan-editorpython -m compileall -q .\application\single_appnode --check .\application\single_app\static\js\chat\chat-export.jsnode --check .\application\single_app\static\js\chat\chat-inline-diagrams.jspython .\functional_tests\route_tests\test_route_blueprint_policy_inventory.pypython .\functional_tests\route_tests\test_route_unauthenticated_policy_contract.pypython .\functional_tests\route_tests\test_route_policy_test_coverage.pypython .\scripts\build_docs_inventory.pypython .\functional_tests\test_docs_app_surface_coverage.pypython .\functional_tests\test_docs_site_quality.pypython .\scripts\build_release_notes_pages.py --check& $python .\functional_tests\test_chat_inline_diagram_rendering.py& $python .\functional_tests\test_export_mermaid_browser_rasterizer.pynode .\functional_tests\test_v2_navigation_groups_logic.mjsgit diff --check HEAD^1 HEADSDK, backend, and browser selections: exact commands and results
The SDK matrix ran with
PYTHONPATHset to the application and functional-test directories, warmed tokenizer assets, and the repository's network guard:Result: 2,005 passed; 431 subtests passed. Inventory: 1,094 owners, 425 doubles, zero review gaps.
Result: 262 passed.
Result: 175 passed; 57 subtests passed.
Result: 77 passed; 33 subtests passed.
Result: 184 passed.
node --test .\functional_tests\test_native_workbook_citation_parser.mjs .\functional_tests\test_v2_chat_attachment_isolation.mjs .\functional_tests\test_v2_orchestration_progress_lane.mjs .\functional_tests\test_v2_orchestration_run_progress_status.mjs .\functional_tests\test_v2_stream_citation_delivery.mjs .\functional_tests\test_v2_web_iq_citations.mjsResult: 43 passed.
Committed-head guardrail CLI commands
The actual committed head, not the pre-merge source head, was checked. The file arrays were generated from the complete application diff and converted to Windows paths:
Results: Swagger passed for 562 paths, access-control passed for 562 paths, and XSS passed for 1,460 paths, against base
f4e186401b58e284ee9b626aa84c903f69ea100band head783153c1af61b52cb7236a63066be1a422abd3de.Not run: a live authenticated Azure deployment smoke test, private/native OneNote executable fixtures, or a full native/container build. Local component/HTTP fixtures are not a claim of deployment validation. No resources were provisioned or independently deployed.
Documentation
See
docs/explanation/fixes/REACT_V2_DEVELOPMENT_INTEGRATION_FIX.md, the0.261.419release entry, chat-control and waiting-run guidance, and the preserved historical fix notes.Security checklist
@swagger_route(security=get_auth_security())sanitize_settings_for_user()The pinned classic Mermaid distribution uses the existing vendor boundary; first-party wrappers remain scanned. Narrow annotations document reviewed sanitizer, generated-blob, fixed-route, and intentionally hostile fixture boundaries rather than globally disabling first-party checks.