Fix three issues found reviewing the 1.0.1 lifecycle work

[yosriady]

Follow-up to #70 and #71, from a Codex review sweep. All three are real; one is a genuine severity concern.

1. CrashReporter could sever the handler chain

The installed handler read this.previousHandler, a mutable field that cleanup() cleared. With two reporters alive — the provider re-initialising, or a customer's own reporter wrapping ours:

A.start()   → A wraps original
B.start()   → B wraps A
A.cleanup() → cannot restore (B is installed), clears A.previousHandler
crash       → B reports → calls A → A reports AGAIN → forwards to undefined

Net effect: the real RN/default handler never runs (no redbox, no crash-reporter chain) and a stopped reporter emits a duplicate Application Crashed.

Fixed by capturing the previous handler in the closure at install time, not clearing it on cleanup, and having a stopped reporter forward without reporting.

2. buildScreenUrl let the screen name change URL structure

screen("Checkout?coupon=SUMMER") produced app://bundle/Checkout?coupon=SUMMER, which parses with pathname /Checkout — the rest of the screen name silently dropped. '?' and '#' are now percent-encoded. '/' deliberately is not: router-style names like /tabs/leaderboard are meant to be path segments.

Dot segments (a/../Admin) are knowingly left alone. Encoding them is not possible — the URL spec decodes %2E before resolving path segments, so a JS new URL() collapses them either way. It also doesn't matter: the ingestion pipeline parses with ClickHouse's path(), which performs no dot-segment normalisation. Verified directly against the real parser:

path('app://com.acme.wallet/a/../Admin')  ->  /a/../Admin

3. Deep Link Opened was disabled by an unrelated flag

The event was gated on attribution.deeplinks, because that check also guarded the Linking hook both features share. So autocapture: { deepLinks: true } with attribution: { deeplinks: false } emitted nothing, with no indication that a different setting was responsible.

The hook is now installed if either consumer needs it, and each behaviour checks its own flag independently.

Tests

297 passing (6 new), typecheck / lint / build clean. The crash tests cover the nested-reporter sequence specifically: the original handler is still reached after the inner reporter is cleaned up, and the cleaned-up reporter does not double-report.

🤖 Generated with Claude Code

---

^{Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.}

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: fa993d915e

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Escape literal percent signs before encoding delimiters

When a screen name already contains the literal text %3F or %23, it now produces exactly the same page_url as a distinct name containing ? or # (for example, Checkout%3Fx and Checkout?x both become app://<bundle>/Checkout%3Fx). This causes URL-based screen analytics to merge distinct screen names; encode existing % characters first, or encode each slash-separated path segment with a standard component encoder.

Useful? React with 👍 / 👎.