Skip to content

Phase 4: cross-format Compare orchestration - #1069

Merged
Paul Lizer (paullizer) merged 1 commit into
microsoft:fix/1031-tabular-row-orchestration-scalefrom
paullizer:feature/1059-phase-4-cross-format-compare
Jul 23, 2026
Merged

Phase 4: cross-format Compare orchestration#1069
Paul Lizer (paullizer) merged 1 commit into
microsoft:fix/1031-tabular-row-orchestration-scalefrom
paullizer:feature/1059-phase-4-cross-format-compare

Conversation

@paullizer

@paullizerPaul Lizer (paullizer) commented Jul 23, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Add default-off native mixed-source Compare orchestration for one Source plus an initially single Target.
  • Reuse the Phase 1 authorized manifest, capability partitions, bounded evidence envelopes, document-window analysis, existing tabular runner, and established pairwise/final comparison prompts.
  • Preserve target order, source roles, native engine labels, source-version coverage, artifacts/citations, token aggregation, and partial target visibility.
  • Fail closed with a clear limitation while the flag is off, preventing tables from being silently routed through narrative chunk analysis.
  • Add Phase 4 functional coverage, documentation, release note, and bump the application version to 0.250.067.

Validation

  • functional_tests/test_cross_format_compare_workflow.py
  • functional_tests/test_tabular_document_actions_workflow.py (6/6)
  • functional_tests/test_mixed_source_analyze_workflow.py
  • functional_tests/test_mixed_source_manifest_contracts.py (13/13)
  • Python compilation for all changed Python files
  • Editor diagnostics clean
  • Scoped broken-access-control and XSS scans passed
  • CRLF-aware git diff --check passed

Rollout / Remaining Gate

  • enable_cross_format_compare and enable_cross_format_compare_one_to_many both default to false.
  • The initial enabled stage permits one Source plus one Target; one-to-many mixed targets remain staged off.
  • Validated multi-file structured overlap/delta operations, full authorization and source-version runtime matrix, Foundry/streaming parity, and frontend Playwright coverage remain rollout-gate follow-up work.

Fixes#1059
Refs #1055
Refs #1056
Refs #1057
Refs #1058

@paullizer
Paul Lizer (paullizer) merged commit b504f3b into microsoft:fix/1031-tabular-row-orchestration-scaleJul 23, 2026
2 checks passed
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

@paullizer