Push Deep Link Lifecycle

---
name: push-deep-link-lifecycle
description: Implement push notifications and deep links across cold start, background, foreground, authentication, navigation, duplication, and stale content states.
---
# Push Deep Link Lifecycle

Use when this procedure is the primary professional method needed for the assignment.

## Procedure
1. Confirm the decision or outcome this work must support, its scope, owner, constraints, and definition of success.
2. Establish the evidence baseline using notification provider contract, URL scheme/universal links, navigation map, auth state, and product permissions. Do not fill material gaps with assumptions when they can change the result.
3. Define canonical link payload, validate origin/content, route through app initialization/auth gates, deduplicate handling, and test all lifecycle entry states.
4. Exercise realistic edge, failure, transition, or exception cases that could invalidate the result; record unresolved uncertainty explicitly.
5. Validate the output against the original outcome and any neighboring professional contracts so this skill does not silently absorb another specialist's authority.
6. Record the resulting artifact, measurements, decisions, provenance, and handoff information needed for another owner to reproduce or continue the work.

## Quality gate
The same link reaches the intended safe destination once across all supported lifecycle states.