Repository navigation
Fix native audit citations for separate supporting documents - #1918
Merged
Paul Lizer (paullizer) merged 1 commit intoNov 11, 2026
Merged
Paul Lizer (paullizer) merged 1 commit into
Paul Lizer (paullizer) merged 1 commit into
Conversation
Admit supporting-document citations through the retained owner's projection while keeping native facts and strict marker validation separate. Version the checking contract for explicit renewal and cover mixed-source delivery, refusal, and recovery. Update fix documentation and application version to 0.261.428. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Paul Lizer (paullizer)
merged commit Nov 11, 2026
2fafbd6
into
microsoft:Development
12 of 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
Linked issue
N/A - no linked issue was supplied.
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 are intentionally unchanged at the user's request. No new admin control or Latest Feature card is introduced.
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.427 -> 0.261.428. No deployer files changed.
Testing / validation
Local validation used the existing network guard and isolated external I/O/provider replies. Counts below overlap and are not a combined unique-test total.
Passed: 218 tests covering native contracts/delivery, the real action HTTP path and lineage, completeness, and available-information controls:
Passed: 127 tests under optimized Python, including source-backed native pipeline and request-contract compatibility:
Passed: 38 tests for the final application version and focused citation contracts:
python -B .\scripts\check_cosmos_response_boundaries.py- passed, 1,094 owners, 425 doubles, zero review gaps.python -B .\functional_tests\test_docs_app_surface_coverage.py- passed, 7/7 checks; inventory is current.python -B .\functional_tests\test_docs_site_quality.py- passed, 6/6 checks.git --no-pager diff --check- passed.No live beta deployment or retry was performed. The saved trace establishes citation-validation failure, but the exact rejected markers in its private initial/final candidates were not recovered. Controlled regressions establish this contract repair, not guaranteed behavior from every live model. Retained workspace sources remain provenance; existing conversation/run and current external-action access semantics are unchanged.
Documentation
Added
docs/explanation/fixes/NATIVE_AUDIT_MULTI_SOURCE_CITATION_FIX.mdand linked it from the preceding reliability fix. No new feature surface requires a guide or inventory change. Release notes were explicitly left unchanged by the user.Security checklist
@swagger_route(security=get_auth_security())sanitize_settings_for_user()No routes, frontend settings payloads, or browser assets changed. Private investigation exports, console logs, and session artifacts are not included in this PR.