Separate stage submission from whole-journey completion

A successful submission event can mark an intermediate stage rather than completion of every configured task. When workflows conditionally continue after submission, define persisted stage completion and whole-journey completion separately, carrying the effective requirement configuration into analysis. Otherwise a chart can correctly count submissions while overstating end-to-end completion. Preserve historical event semantics and introduce an explicit new completion boundary instead of relabeling old observations. Eligibility for later stages must also be separate from completion; a stage never made available is not a driver drop-off. Applies when: Configurable workflows can continue after an initial successful submission. Keywords: journey analytics stage submission completion requirements eligibility funnel