[Paul Lizer (paullizer)]

Summary

• Replace the automatic, internally named analysis block inside V2 answers with on-demand saved findings and supporting passages in the existing per-message Sources inspector. Citations, findings, and source counts stay distinct; technical labels and diagnostic JSON links belong to Details.
• Preserve authorization, masking, unavailable-result notices, pagination, downloads, whole-review follow-ups, and classic chat behavior. Document links reuse the existing identity-aware citation viewer, and conflicting identities remain non-clickable.
• Add content-free, debug-gated publication telemetry after durable message read-back, correlating conversation, run, producer step, and assistant message through hashes. Bump the application to 0.261.419 and update user, control, logging, and fix documentation.

This changes presentation and observability, not native Word comment extraction. The investigated body findings are not native comment records; the missing-comment cause remains unproven. No deployment, historical conversation rerun, new route, runtime dependency, or Azure configuration change is included.

Linked issue

N/A. The user declined creating an issue.

Release Notes & Latest Features

• New Feature
• Bug Fix
• UI Enhancement
• Breaking Change
• Internal only

Is this visible to end users?

• Yes
• No

Is this admin-facing (Admin Settings, governance, deployment, config)?

• Yes
• No

Should this become a Latest Feature card?

• Yes
• No
• Already added

Screenshot needed for the card?

• Yes
• No
• Attached

Version bump

• application/single_app/config.py VERSION third segment bumped, or not needed because this is docs-only
• deployers/version.txt bumped, or not needed because deployers/ was not changed

Application: 0.261.418 -> 0.261.419. No deployer changes.

Testing / validation

• npm --prefix .\application\v2_ui run typecheck - passed.
• npm --prefix .\application\v2_ui run build -- --outDir ..\..\ui_tests\artifacts\saved-analysis - passed; existing large-chunk warning remains.
• python -m pytest .\ui_tests\test_chat_saved_analysis.py -q --tb=short -x - 74 passed.
• python -m pytest .\ui_tests\test_chat_saved_analysis.py -q --tb=short -k "unified_sources or citations_without_saved or conflicting_recorded" - final focused run: 6 passed, including measured 4.5:1 text contrast across desktop/mobile and light/dark themes.
• python -m pytest .\functional_tests\test_orchestration_analysis_citation_delivery.py -q --tb=short -x - 22 passed, including debug-off/on publication and failed-persistence behavior.
• python .\scripts\check_cosmos_response_boundaries.py - passed: 1,094 owners, 425 doubles, zero review gaps. All five execution-module owners were explicitly reviewed.
• python .\functional_tests\test_docs_app_surface_coverage.py - 7/7 checks passed; regenerated inventory is unchanged.
• python .\functional_tests\test_docs_site_quality.py - 6/6 checks passed.
• git -c core.whitespace=blank-at-eol,blank-at-eof,space-before-tab,cr-at-eol diff --check - passed.

Affected-owner network-blocked storage contracts also passed (161 cases). The repository-wide storage-contract run was stopped in favor of affected-owner checks; no full-suite pass is claimed. Desktop/mobile screenshots were visually inspected using synthetic fixtures, not reconstructed historical conversation records.

Documentation

• Release notes updated, or not needed
• Feature documentation updated, or not needed
• Fix documentation updated, or not needed

Updated the Analyze guide, chat-control reference, logging reference, and docs/explanation/fixes/UNIFIED_SOURCES_SAVED_FINDINGS_FIX.md. Release-note approval was requested, but the user was unavailable; release notes remain unchanged pending approval.

Security checklist

• New Flask routes include @swagger_route(security=get_auth_security())
• Settings sent to non-admin frontends use sanitize_settings_for_user()
• Browser JavaScript is served from local SimpleChat static assets only; no CDN-hosted JS
• No secrets, keys, connection strings, or local-only artifacts are included

No Flask routes or settings-delivery paths were added or changed. Existing saved-result access controls remain in effect; telemetry excludes record contents and raw identifiers, and browser previews/build artifacts are not committed.