Type Alias AnalyzeContinuationReason

Runtime evidence describing how an analyze artifact reached its final state.

Two categories:

Diagnostic causes — explain why a fallback path may have been entered. On their own, they do NOT degrade quality. They only degrade when paired with a fallback action reason from the second category.

• timeout_recovery — section recovered via timeout fallback
• preliminary_exhaustion — preliminary budget exhausted
• programmatic_conflict — programmatic validator violation triggered retry/repair path (entry evidence, not final failure)
• cross_file_reject — cross-file review rejected (advisory)
• targeted_patch — targeted patch executed (recovery path entered)

Fallback actions — actually executed degraded paths. Any one of these forces the final quality to degraded.

• placeholder_used — empty placeholder section used
• previous_section_reused — previous section reused (force-pass)
• stagnation_force_pass — repeated identical rejection forced through
• retry_limit_force_pass — max retry exceeded
• review_limit_force_pass — max review count exceeded
• cross_file_review_error_force_pass — cross-file review threw; pending files force-passed