Phase 7: Add tabular parity lifecycle coverage metadata - #1216
Merged
Paul Lizer (paullizer) merged 1 commit intoAug 12, 2026
Conversation
Paul Lizer (paullizer)
merged commit Aug 12, 2026
57873f4
into
microsoft:feature/tabular-analyze-search-parity
2 checks passed
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
Phase 7 starts lifecycle hardening for the tabular Analyze/Search parity roadmap.
canceledas a first-class mixed-source terminal evidence status with separate counts, safe reason codes, and aggregate reducer handling.lifecycle_state,execution_state,evidence_status,terminal,required_for_composition,safe_reason_code) for queued, retrying, finalizing, completed, failed, and canceled states.0.250.163.Refs #1031
Refs #1055
Refs #1058
Explicit Non-Goals
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_modeenable_tabular_search_shared_preflightenable_tabular_analyze_durable_preflightenable_tabular_mixed_deferred_compositionenable_tabular_multifile_durable_preflightExisting 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.pypython functional_tests/test_tabular_phase7_lifecycle_coverage.pypython functional_tests/test_mixed_source_deferred_composition_phase5.pypython functional_tests/test_tabular_shared_request_planner.pypython functional_tests/test_tabular_background_generated_exports.pygit -c core.whitespace=blank-at-eol,blank-at-eof,space-before-tab,cr-at-eol diff --checkAttempted but not green in this workspace:
functional_tests/test_mixed_source_hardening.pyran past dependency import after using the configured.venv, then failed an existing Foundry context opt-out assertion around preservingSafe task.. That path is outside the Phase 7 changed files.Security And Source Scope
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.163Release Notes
Not updated in this commit.