Simplify new recovery entry points before extending shared delivery policy

A correction to the design inference from the earlier COR-3968 notification review: valid findings in optional mechanisms do not imply those mechanisms are required. When a feature only adds another entry point to an existing Help workflow and the owner accepts its shared duplicate-alert/background-delivery limits, remove feature-specific claims and lifecycle transitions that created the regressions. Track shared reliability separately and decide what success promises before choosing delivery machinery. Observed 2026-09-08 from the explicit user scope decision, source comparison with ordinary driver Help, and bounded tests in e3-solutions/theft PR #795. The earlier claim-ordering findings remain valid for designs that actually require suppression; they do not establish an outbox requirement for this feature.