Skip to content

Phase 7: Add tabular parity lifecycle coverage metadata - #1216

Merged
Paul Lizer (paullizer) merged 1 commit into
microsoft:feature/tabular-analyze-search-parityfrom
paullizer:feature/tabular-analyze-search-parity-phase-7-lifecycle
Aug 12, 2026
Merged

Phase 7: Add tabular parity lifecycle coverage metadata#1216
Paul Lizer (paullizer) merged 1 commit into
microsoft:feature/tabular-analyze-search-parityfrom
paullizer:feature/tabular-analyze-search-parity-phase-7-lifecycle

Conversation

@paullizer

Copy link
Copy Markdown
Contributor

Summary

Phase 7 starts lifecycle hardening for the tabular Analyze/Search parity roadmap.

  • Add explicit planner source lifecycle coverage fields so replayable tabular sources begin as planned, pending, nonterminal evidence.
  • Add canceled as a first-class mixed-source terminal evidence status with separate counts, safe reason codes, and aggregate reducer handling.
  • Add normalized generated-output public lifecycle metadata (lifecycle_state, execution_state, evidence_status, terminal, required_for_composition, safe_reason_code) for queued, retrying, finalizing, completed, failed, and canceled states.
  • Document the Phase 7 lifecycle coverage contract and bump the app version to 0.250.163.

Refs #1031
Refs #1055
Refs #1058

Explicit Non-Goals

  • No new durable runner, source resolver, authorization model, or artifact UI.
  • No Phase 8 UI rollout changes.
  • No restart recovery or terminal notification replay implementation beyond the additive lifecycle status contract.

Behavior Gates And Defaults

This change is additive to existing Phase 2-6 gates. New parity assignment remains controlled by the existing backend settings, including:

  • tabular_request_planner_mode
  • enable_tabular_search_shared_preflight
  • enable_tabular_analyze_durable_preflight
  • enable_tabular_mixed_deferred_composition
  • enable_tabular_multifile_durable_preflight

Existing generated-output runs still load through the existing public status builder.

Validation

Passed:

  • python -m py_compile application/single_app/functions_mixed_source_orchestration.py application/single_app/functions_tabular_orchestration.py application/single_app/functions_tabular_generated_exports.py application/single_app/config.py functional_tests/test_tabular_phase7_lifecycle_coverage.py
  • python functional_tests/test_tabular_phase7_lifecycle_coverage.py
  • python functional_tests/test_mixed_source_deferred_composition_phase5.py
  • python functional_tests/test_tabular_shared_request_planner.py
  • python functional_tests/test_tabular_background_generated_exports.py
  • VS Code diagnostics on changed Python files
  • New-file hygiene check for final newline/trailing whitespace
  • git -c core.whitespace=blank-at-eol,blank-at-eof,space-before-tab,cr-at-eol diff --check

Attempted but not green in this workspace:

  • functional_tests/test_mixed_source_hardening.py ran past dependency import after using the configured .venv, then failed an existing Foundry context opt-out assertion around preserving Safe task.. That path is outside the Phase 7 changed files.

Security And Source Scope

  • Canceled durable tabular evidence is terminal but incomplete and cannot count as completed factual coverage.
  • Pending durable tabular work remains nonterminal and continues to block required mixed-source reduction.
  • Generated-output public metadata exposes only normalized safe lifecycle/status reason codes.
  • Existing user-scoped generated-output status, resume, cancel, rollback, and artifact deletion helpers are reused.

Rollback

Disable new parity assignment with the existing backend gates. Keep the additive lifecycle readers in place while any accepted generated-output run or deferred composition descriptor can still reference them.

Version

  • application/single_app/config.py: 0.250.162 -> 0.250.163

Release Notes

Not updated in this commit.

@paullizer
Paul Lizer (paullizer) merged commit 57873f4 into microsoft:feature/tabular-analyze-search-parity Aug 12, 2026
2 checks passed
Sign up for free to 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