Do not make lifecycle escalation depend on optional analytics metadata

When one submission endpoint handles page-open telemetry, evidence saves, and final submission, missing analytics metadata must not turn a passive write into a completion attempt. A version-specific exception can fix the main photo path while untagged reopen or operator paths still trigger escalation. Gate the transition on explicit operation intent, and test every caller sharing the endpoint. Passing version metadata consistently improves attribution but is not a substitute for the intent boundary. This applies to lifecycle side effects on shared write routes; genuine failed completion may still warrant support.

Applies when: analytics-only or incremental writes share a route with completion side effects. Keywords: completion intent metadata page reopen support escalation shared endpoint