Remove duplicate agent and tabular progress panels in V2

[Paul Lizer (paullizer)]

Summary

• Remove distracting Agent progress and Tabular analysis thought-summary panels in V2 using the same showsCard: false policy already used by orchestration.
• Preserve activity and failure details in the collapsed reasoning dropdown for live and saved responses. Keep V1, lightweight Thinking/Planning indicators, orchestration run status, and background-export progress with Continue/Cancel controls unchanged.
• Add lane-policy and desktop/mobile browser regression coverage, update related documentation, and bump the application version to 0.261.318.

Linked issue

N/A. The user requested no tracking issue for this change.

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

Release notes were offered but left unchanged because approval was unavailable. No Latest Feature card is proposed.

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 version: 0.261.317 -> 0.261.318. No deployer changes.

Testing / validation

• node --test .\functional_tests\test_v2_orchestration_progress_lane.mjs .\functional_tests\test_v2_agent_tabular_progress_cards.mjs - passed: 20 tests.
• npm --prefix .\application\v2_ui run build -- --outDir ..\..\ui_tests\artifacts\orchestration-plan-editor --logLevel error - passed, including TypeScript checking.
• python -m pytest .\ui_tests\test_v2_orchestration_streaming_bubble.py -q - passed: 8 tests in local Chromium. Covers desktop/mobile agent and tabular turns, mouse/keyboard dropdown interaction, failed activity, finished/remounted reasoning, and unchanged orchestration behavior.
• python .\functional_tests\test_v2_tabular_parity.py - 13/14 checks passed, including all 70 TypeScript logic checks. The existing confirmation-ordering check fails with Could not locate the composer submit handler; running that same check against the unchanged HEAD version of Composer.tsx reproduced the failure. Composer.tsx is not changed by this PR.
• python .\functional_tests\test_docs_app_surface_coverage.py - passed: 7/7 checks; committed inventory is current.
• python .\functional_tests\test_docs_site_quality.py - passed: 6/6 checks.
• git -c core.whitespace=blank-at-eol,blank-at-eof,space-before-tab,cr-at-eol diff --check - passed.
• Before the fix, the new lane-policy checks failed on showsCard: true and the desktop-agent browser regression detected the unwanted progress bar. They pass after the fix.

Documentation

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

Updated V2_TABULAR_ANALYSIS.md and added V2_AGENT_TABULAR_DUPLICATE_PROGRESS_CARD_FIX.md. Release notes remain unchanged as noted above.

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 routes, settings payloads, browser asset sources, or authorization behavior changed.