Scale tabular row orchestration exports - #1145
Merged
Merged
Conversation
…e-manifest-pr Phase 1: add authorized mixed-source manifest contracts
…d-source-consistency Phase 2: honor explicit mixed-source Chat selections
…-csv-artifacts Fix CSV artifacts for non-tabular documents
…lyze Phase 3: mixed-source combined Analyze
…rmat-compare Phase 4: cross-format Compare orchestration
…tinuity Phase 5: preserve mixed-source context across follow-up turns
…dening Harden mixed-source orchestration and CSV exports
…tion Add universal CSV generation across response paths
Promote current-turn structured function results into a format-neutral CSV, DOCX, and PDF artifact pipeline across chat, agents, document actions, and workflows. Preserve durable CSV handling and coverage-aware tabular exports.\n\nRefs #1071
Increase bounded search, metadata, directory, workflow, assigned-knowledge, and mixed-source candidate retrieval limits while preserving authorization and existing maximum constraints. Update affected functional coverage and release notes.
…tion Add generated file export framework
…ar-row-orchestration-scale # Conflicts: # application/single_app/config.py # docs/explanation/release_notes.md
Contributor
Author
|
CodeQL remediation update for alert 30 / plan item 10: removed the duplicate local \json\ import from \chat_stream_api, relying on the existing module-level import. Bumped app version to \ |
Contributor
Author
|
Resolved the PR branch conflicts by merging latest \Development\ into \ix/1031-tabular-row-orchestration-scale\ and pushed merge commit \ |
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
Validation
git -c core.whitespace=blank-at-eol,blank-at-eof,space-before-tab,cr-at-eol diff --check origin/Development...HEADpython -m py_compilefor changed Python filesnode --checkfor changed JavaScript filespython scripts/check_swagger_routes.py application/single_app/app.py application/single_app/route_backend_chats.py application/single_app/route_backend_collaboration.py application/single_app/route_backend_conversations.py application/single_app/route_backend_data_management.pypython 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 functional_tests/test_tabular_row_orchestration_scale.pypython scripts/check_xss_sinks.py --base-sha origin/Development --head-sha HEAD <changed application files>python scripts/check_broken_access_control.py --base-sha origin/Development --head-sha HEAD <changed Python application files>Notes
Developmentfix/1031-tabular-row-orchestration-scale