@everframe/react-native 1.4.1 → 1.6.0

package/ios/Sources/EverframeEventEmitter.swift

@@ -1,7 +1,8 @@
 // SPDX-License-Identifier: MIT
 // SPDX-FileCopyrightText: 2026 ScriptX
 //
-// Plan 06.2-11 — RCTEventEmitter subclass for the phone-companion bridge.
+// RCTEventEmitter subclass for the bridge's native → JS events (today: the
+// extra-resolver ask, spec 2026-09-17).
 //
 // iOS RN event emission requires an `RCTEventEmitter` subclass (one per
 // module — the base class enforces a single supportedEvents() list). We
@@ -23,63 +24,20 @@
 // Objective-C base.
 //
 // Threading: `sendEvent(withName:body:)` is thread-safe across the RN core
-// (the internal bridge enqueues the event on the JS thread). Combine sinks
-// installed in `EverframeBridge` may fire on the URLSession delegate queue;
-// we forward straight to the emitter without a main-thread hop.
+// (the internal bridge enqueues the event on the JS thread); we forward
+// straight to the emitter without a main-thread hop.
 //
-// Event names — duplicated in JS facade `src/companion.ts`. Keep in lock-step.
+// Event names — duplicated in the JS facade (`src/runtime.ts`). Keep in
+// lock-step.
 import Foundation
 import React
 
 @objc(EverframeEventEmitter)
 public final class EverframeEventEmitter: RCTEventEmitter {
 
-    /// Event name forwarded as `everframe.companion.state`.
-    /// Payload: String — one of "unpaired" | "paired" | "report_in_progress" | "phone_disconnected".
-    public static let stateEvent = "everframe.companion.state"
-
-    /// Event name forwarded as `everframe.companion.pairUrl`.
-    /// Payload: String | NSNull (NSNull crosses to JS as `null`).
-    public static let pairUrlEvent = "everframe.companion.pairUrl"
-
-    /// Event name forwarded as `everframe.companion.code`.
-    /// The short display code returned by `/api/companion/announce`
-    /// (spec 2026-08-07) — hosts render it beside the QR so a team member
-    /// reading the TV screen can pick this device out of the dashboard list.
-    /// Payload: String | NSNull (NSNull crosses to JS as `null`).
-    public static let codeEvent = "everframe.companion.code"
-
-    /// Event name forwarded as `everframe.companion.attachedUserName`.
-    /// The dashboard member who attached to this device; nil on an ordinary
-    /// QR bond. Payload: String | NSNull (NSNull crosses to JS as `null`).
-    public static let attachedUserNameEvent = "everframe.companion.attachedUserName"
-
-    /// Event name forwarded as `everframe.companion.resolvedName` (naming spec
-    /// 2026-08-24). The server-resolved device display name for THIS device
-    /// (e.g. an org-configured friendly name), or nil before the first
-    /// successful announce / when discovery never ran. Payload: String |
-    /// NSNull (NSNull crosses to JS as `null`).
-    public static let resolvedNameEvent = "everframe.companion.resolvedName"
-
-    /// Event name forwarded as `everframe.companion.attachChallenge` (spec
-    /// 2026-08-19). The pending dashboard-initiated attach-PIN challenge, or
-    /// nil when none is outstanding. Forwarded in every `attachPinUi` mode,
-    /// including `'builtin'` (which renders the PIN natively AND still
-    /// fires this event) — it's only NEEDED by hosts configured with
-    /// `'custom'`, which must read it to build their own surface.
-    /// Payload: `{ code, requestedByName, ttlMs }` | NSNull.
-    public static let attachChallengeEvent = "everframe.companion.attachChallenge"
-
-    /// Fired when a `report.request` arrives from the paired phone. The event
-    /// and the bridge's brief wait are the companion's JS-ready handshake
-    /// (see CompanionCaptureBridge.awaitJsReactTreeAttach).
-    /// Payload: String — the correlation_id of the inbound request.
-    public static let reportRequestedEvent = "everframe.companion.reportRequested"
-
     /// Fired right before native drains pending attachments for ANY report
-    /// (spec 2026-09-17 setExtra-resolver) — NOT just the companion flow:
-    /// the plain in-app `openReporter()` and native shake both trigger this
-    /// too, since both funnel through `Everframe.shared.report.open()` →
+    /// (spec 2026-09-17 setExtra-resolver): the plain in-app `openReporter()`
+    /// and native shake both trigger this, since both funnel through `Everframe.shared.report.open()` →
     /// `__consumePendingAttachments()`. Only fires when JS has a resolver
     /// CURRENTLY registered (`EverframeBridge.setExtraResolverActive`) — see
     /// `EverframeBridge.awaitJsExtraResolve`. Payload: String — the
@@ -111,89 +69,14 @@ public final class EverframeEventEmitter: RCTEventEmitter {
     /// adding it here is the exact failure this comment exists to prevent.
     public override func supportedEvents() -> [String] {
         return [
-            Self.stateEvent,
-            Self.pairUrlEvent,
-            Self.codeEvent,
-            Self.attachedUserNameEvent,
-            Self.resolvedNameEvent,
-            Self.attachChallengeEvent,
-            Self.reportRequestedEvent,
             Self.extraResolveRequestedEvent,
         ]
     }
 
     // MARK: - Static helpers used by EverframeBridge
 
-    /// Forward a companion-state change to JS. Silently dropped if no
-    /// emitter instance is alive (e.g. before any listeners attached). The
-    /// RN base class also warns when `sendEvent` fires with zero listeners,
-    /// which is the documented behavior — our JS facade attaches listeners
-    /// inside `useCompanion()`, so the warning surfaces only when no React
-    /// subtree is rendering the companion screen.
-    @objc public static func sendState(_ state: String) {
-        shared?.sendEvent(withName: stateEvent, body: state)
-    }
-
-    /// Forward a pairUrl change to JS. `nil` is passed across the bridge as
-    /// `NSNull()` so the JS handler receives an actual `null`. Note: pairUrl is
-    /// now nulled only on socket close, so this `nil` branch fires rarely —
-    /// hosts drive QR teardown off `state`, the reliably-delivered signal.
-    @objc public static func sendPairUrl(_ url: String?) {
-        if let url = url {
-            shared?.sendEvent(withName: pairUrlEvent, body: url)
-        } else {
-            shared?.sendEvent(withName: pairUrlEvent, body: NSNull())
-        }
-    }
-
-    /// Forward an announce display-code change to JS. `nil` crosses as
-    /// `NSNull()` so the JS handler receives an actual `null` — that happens
-    /// when companion discovery was never attempted (no SDK key configured),
-    /// when the announce failed, or when the relay socket closed terminally.
-    @objc public static func sendCode(_ code: String?) {
-        if let code = code {
-            shared?.sendEvent(withName: codeEvent, body: code)
-        } else {
-            shared?.sendEvent(withName: codeEvent, body: NSNull())
-        }
-    }
-
-    /// Forward an attached-dashboard-user change to JS. `nil` crosses as
-    /// `NSNull()` — an ordinary QR bond carries no `companion_user` block, so
-    /// the nil branch is the common case here (unlike `sendPairUrl`).
-    @objc public static func sendAttachedUserName(_ name: String?) {
-        if let name = name {
-            shared?.sendEvent(withName: attachedUserNameEvent, body: name)
-        } else {
-            shared?.sendEvent(withName: attachedUserNameEvent, body: NSNull())
-        }
-    }
-
-    /// Forward a resolved device display-name change to JS (naming spec
-    /// 2026-08-24). `nil` crosses as `NSNull()` — before the first successful
-    /// announce, or when discovery never ran, this is the common case.
-    @objc public static func sendResolvedName(_ name: String?) {
-        if let name = name {
-            shared?.sendEvent(withName: resolvedNameEvent, body: name)
-        } else {
-            shared?.sendEvent(withName: resolvedNameEvent, body: NSNull())
-        }
-    }
-
-    /// Forward a `report.request` correlation id to JS. JS signals the
-    /// bridge back via `signalCompanionReportRequestReady` when it is
-    /// ready for capture to proceed.
-    @objc public static func sendReportRequested(_ correlationId: String) {
-        shared?.sendEvent(withName: reportRequestedEvent, body: correlationId)
-    }
-
-    /// Forward an attach-PIN challenge to JS. nil crosses as NSNull() → JS null.
-    @objc public static func sendAttachChallenge(_ payload: [String: Any]?) {
-        shared?.sendEvent(withName: attachChallengeEvent, body: payload ?? NSNull())
-    }
-
     /// Forward an extra-resolver ask correlation id to JS (spec 2026-09-17
-    /// setExtra-resolver). Mirrors `sendReportRequested` exactly — JS signals
+    /// setExtra-resolver). JS signals
     /// the bridge back via `signalExtraResolverReady` when it has pushed a
     /// freshly resolved value (or given up) for this correlation id.
     @objc public static func sendExtraResolveRequested(_ correlationId: String) {

package/ios/Sources/EverframeModule.mm

@@ -187,32 +187,11 @@ RCT_EXPORT_MODULE(Everframe)
   BOOL installIdentifierDisabled = opts.installIdentifierDisabled().value_or(false);
   // `crashReportingDisabled` — same `std::optional<bool>` shape. Absent keeps capture on.
   BOOL crashReportingDisabled = opts.crashReportingDisabled().value_or(false);
-  // `attachPinUi` (spec 2026-08-19) is a plain optional STRING field —
-  // `opts.attachPinUi()` returns a nullable NSString*, same shape as
-  // `opts.sdkKey()` above, NOT the `std::optional<bool>` shape
-  // `networkBodiesDisabled()` uses. `EverframeBridge.configure` coerces a
-  // nil/unrecognised value to `.builtin`.
-  NSString *attachPinUi = opts.attachPinUi();
-  // `companionDeviceId` (naming spec 2026-08-24) is a plain optional STRING
-  // field — same nullable-NSString* shape as `attachPinUi` above, not the
-  // `std::optional<bool>` shape `networkBodiesDisabled()` uses.
-  NSString *companionDeviceId = opts.companionDeviceId();
-  // `companionBadgeEnabled`/`companionBadgePosition` (naming spec
-  // 2026-08-24, controller ruling / Task 6b) — flat fields on ConfigOpts;
-  // RN codegen cannot express the nested `{enabled, position}` shape the JS
-  // facade's `RuntimeConfig.companionBadge` uses, so `extractBridgeConfig`
-  // flattens it before it crosses. `companionBadgeEnabled()` is
-  // `std::optional<bool>`, same shape as `networkBodiesDisabled()` above;
-  // absent defaults to `true` (badge shown), matching
-  // `CompanionBadgeOptions.enabled`'s own default. `companionBadgePosition()`
-  // is a nullable NSString*, same shape as `attachPinUi`/`companionDeviceId`
-  // above; `EverframeBridge` coerces nil/unrecognised to `.bottomRight`.
-  BOOL companionBadgeEnabled = opts.companionBadgeEnabled().value_or(true);
   BOOL shakeToReportEnabled = opts.shakeToReportEnabled().value_or(true);
+  BOOL quickCaptureEnabled = opts.quickCaptureEnabled().value_or(true);
   // Crash-only session switch (spec 2026-10-12) — `std::optional<bool>`, same shape as
   // `networkBodiesDisabled()`. Absent means a normal report session.
   BOOL reporterDisabled = opts.reporterDisabled().value_or(false);
-  NSString *companionBadgePosition = opts.companionBadgePosition();
   // Inline reporter theme (reporter branding spec 2026-08-25, RN slice) —
   // 8 flat optional STRING fields on ConfigOpts (RN codegen cannot express
   // the nested `theme: { … }` shape the JS facade's `RuntimeConfig.theme`
@@ -253,11 +232,8 @@ RCT_EXPORT_MODULE(Everframe)
                networkBodiesDisabled:networkBodiesDisabled
            installIdentifierDisabled:installIdentifierDisabled
               crashReportingDisabled:crashReportingDisabled
-                         attachPinUi:attachPinUi
-                   companionDeviceId:companionDeviceId
-               companionBadgeEnabled:companionBadgeEnabled
                   shakeToReportEnabled:shakeToReportEnabled
-              companionBadgePosition:companionBadgePosition
+                   quickCaptureEnabled:quickCaptureEnabled
                                theme:(theme.count > 0 ? theme : nil)
                        vitalsEnabled:vitalsEnabled
                     vitalsSampleRate:vitalsSampleRate
@@ -389,8 +365,7 @@ RCT_EXPORT_MODULE(Everframe)
   [EverframeBridge setExtraResolverActive:active];
 }
 
-// JS handshake ack — mirrors `signalCompanionReportRequestReady` below
-// exactly. Releases `EverframeBridge.awaitJsExtraResolve`'s bounded wait for
+// JS handshake ack. Releases `EverframeBridge.awaitJsExtraResolve`'s bounded wait for
 // this correlation id.
 - (void)signalExtraResolverReady:(NSString *)correlationId {
   [EverframeBridge signalExtraResolverReady:(correlationId ?: @"")];
@@ -560,33 +535,10 @@ RCT_EXPORT_MODULE(Everframe)
   return @([EverframeBridge captureHandledException:(crashJson ?: @"")]);
 }
 
-// MARK: - startCompanion / stopCompanion (Plan 06.2-11)
-
-// Opens a relay WS connection against the build-time-baked ingest URL
-// (sdk-ios IngestEndpoint.url) and starts forwarding `Everframe.shared
-// .companion` signals (state + pairUrl) to JS via the
-// `EverframeEventEmitter` RCTEventEmitter subclass.
-- (void)startCompanion {
-  [EverframeBridge startCompanion:@""];
-}
-
-- (void)stopCompanion {
-  [EverframeBridge stopCompanion];
-}
-
-// MARK: - signalCompanionReportRequestReady(correlationId)
-
-// Companion handshake: JS calls this when it is ready for capture to
-// proceed, releasing the native bridge's bounded wait
-// (CompanionCaptureBridge.awaitJsReactTreeAttach).
-- (void)signalCompanionReportRequestReady:(NSString *)correlationId {
-  [EverframeBridge signalCompanionReportRequestReady:(correlationId ?: @"")];
-}
-
 // MARK: - addListener / removeListeners (RN NativeEventEmitter contract)
 //
 // These are intentional no-ops on `EverframeModule` — the JS facade
-// (`src/companion.ts`) constructs `NativeEventEmitter(NativeModules
+// (`src/events.ts`) constructs `NativeEventEmitter(NativeModules
 // .EverframeEventEmitter)`, NOT NativeModules.Everframe, so the real
 // addListener/removeListeners traffic flows to the `EverframeEventEmitter`
 // subclass via RCTEventEmitter's built-in implementations. We still need

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@everframe/react-native",
-  "version": "1.4.1",
+  "version": "1.6.0",
   "description": "React Native SDK for Everframe — AI-ready in-app bug reporting, bridging the native iOS and Android reporter to your RN app. Supports phone, Apple TV, and Android TV.",
   "author": {
     "name": "Scriptx, UAB",
@@ -100,7 +100,7 @@
   "dependencies": {
     "bippy": "^0.5.39",
     "zod": "^4.3.0",
-    "@everframe/react": "^1.4.0"
+    "@everframe/react": "^1.6.0"
   },
   "devDependencies": {
     "@arethetypeswrong/cli": "^0.18.0",
@@ -113,8 +113,8 @@
     "react-native-url-polyfill": "4.0.0",
     "tsup": "^8.0.0",
     "vitest": "^4.0.0",
-    "@everframe/protocol": "0.9.0",
-    "@everframe/sdk-core": "0.6.1"
+    "@everframe/sdk-core": "0.6.3",
+    "@everframe/protocol": "0.10.1"
   },
   "codegenConfig": {
     "name": "EverframeSpec",

package/src/NativeEverframe.ts

@@ -14,8 +14,7 @@
 //   It is imported from our structural compatibility alias because React
 //   Native 0.87 hides the old deep-import declaration by default.)
 // - The 4 report methods below (configure/openReporter/registerSensitiveRect/
-//   setExtra) plus the Plan 06.2-11 companion methods were the
-//   COMPLETE surface — adding another report method requires a phase
+//   setExtra) were the COMPLETE surface — adding another report method requires a phase
 //   D-decision (Plan 02/03 native impls inherit codegen headers).
 //   `addBreadcrumb` (Plan 4 / Task 14) IS that new D-decision: a manual
 //   breadcrumb escape hatch forwarding to the native singleton's coercion
@@ -50,24 +49,6 @@
 //   `UnsafeObject`, same split `addBreadcrumb`'s `data` already uses.
 //   `T | null` stays forbidden; CLEARING is expressed by calling with no
 //   argument.
-//   `ConfigOpts.attachPinUi` (spec 2026-08-19) is the next D-decision after
-//   that — a flat optional STRING, not `'builtin' | 'custom' | 'off'`: RN
-//   codegen cannot express a string-literal union in a struct field any more
-//   than `setUser`'s D-decision above could express one as a bridge method
-//   parameter type — same codegen ceiling, different call site (a
-//   `ConfigOpts` field here, rather than a whole method's parameter there).
-//   Unlike `setUser`'s escape hatch, this one needs no `UnsafeObject`
-//   widening: it's a plain `string`, which codegen already handles natively
-//   in a struct field — the union is only lost at the TYPE level, not the
-//   VALUE level. Each native side re-parses the string into its own
-//   `AttachPinUi` enum (`enum AttachPinUi: String` on iOS, `enum class
-//   AttachPinUi` on Android) and coerces anything unrecognised — including
-//   an absent field, which decodes as `undefined` and never reaches native
-//   at all — to `.builtin`/`BUILTIN`. This rides `configureSync()`, not a new
-//   bridge method: the flag is a startup-time preference, not a per-call
-//   argument, so it belongs beside `sdkKey`/`networkBodiesDisabled` on
-//   `ConfigOpts` — see `companion.ts`'s `everframe.companion.attachChallenge`
-//   event, the JS-facing half of this same D-decision.
 //   Session Vitals (spec 2026-09-06) is the next D-decision after that —
 //   FIVE methods (trackPlayer/detachPlayer/recordPlayerEvent/
 //   updatePlayerStats/trackVitals) and three flat ConfigOpts fields
@@ -81,10 +62,8 @@
 //   `setExtraResolverActive`/`signalExtraResolverReady` (spec 2026-09-17
 //   setExtra-resolver) is the next D-decision after that — RN parity for
 //   the resolver form of `setExtra` core/web already have. Native asks JS
-//   for a fresh value right before draining pending attachments (mirrors
-//   the companion `reportRequested`/`signalCompanionReportRequestReady`
-//   handshake below exactly), bounded and fail-open; see both methods' own
-//   doc comments.
+//   for a fresh value right before draining pending attachments, bounded
+//   and fail-open; see both methods' own doc comments.
 import type { TurboModule } from 'react-native';
 import { TurboModuleRegistry } from 'react-native';
 import type { UnsafeObject } from './codegen-types';
@@ -141,65 +120,21 @@ export type ConfigOpts = {
    * Absent means capture stays on.
    */
   crashReportingDisabled?: boolean;
-  /**
-   * Built-in attach-PIN surface mode (spec 2026-08-19): 'builtin' (default —
-   * the native SDK presents the code itself), 'custom' (host renders it from
-   * onAttachChallenge; the device still announces the capability), 'off'
-   * (legacy one-click dashboard attach, no PIN). Flat string, not a union —
-   * codegen cannot express string-literal unions; the natives coerce unknown
-   * values to 'builtin'.
-   */
-  attachPinUi?: string;
-  /**
-   * Explicit companion device-identity override (naming spec 2026-08-24) —
-   * an MDM id or provisioning serial the host already trusts. Hashed
-   * (SHA-256 → UUID shape) natively before it ever reaches the announce
-   * `device` block — see `CompanionDeviceId.resolve` (iOS) /
-   * `CompanionDeviceId.resolve` (Android). Flat optional string, same
-   * codegen shape as `attachPinUi` above. `undefined`/absent falls through
-   * to each native side's own Keychain/SSAID-then-stored-UUID chain.
-   */
-  companionDeviceId?: string;
-  /**
-   * Companion on-screen name-badge visibility (naming spec 2026-08-24,
-   * controller ruling / Task 6b) — "a production app that finds it
-   * intrusive turns it off in one line". `undefined`/absent defaults to
-   * `true` (badge shown) on both natives, matching
-   * `CompanionBadgeOptions.enabled`'s own default. Flat because RN codegen
-   * rejects nested objects, same constraint `networkBodiesDisabled` above
-   * documents — the host-facing nested `companionBadge: { enabled }` is
-   * flattened here by `extractBridgeConfig`.
-   */
-  companionBadgeEnabled?: boolean;
-  /** Local veto for native mobile shake-to-report. Absent defaults to enabled. */
+  /** Local veto for shake opening the reporter (not for shake quick capture). Absent defaults to enabled. */
   shakeToReportEnabled?: boolean;
+  /** Local veto for quick capture (simulators, emulators and real phones) and device linking. Absent defaults to enabled. */
+  quickCaptureEnabled?: boolean;
   /**
    * Crash-only session switch. `true` turns off every on-device way to open the reporter, keeps
-   * network bodies off and samples replay with the server's crash-only rate until a companion
-   * bond upgrades the session. Flattened by `extractBridgeConfig` from `reporter: { disabled }`.
+   * network bodies off and samples replay with the server's crash-only rate. Flattened by `extractBridgeConfig` from `reporter: { disabled }`.
    * Absent means a normal report session.
    */
   reporterDisabled?: boolean;
-  /**
-   * Companion on-screen name-badge corner (naming spec 2026-08-24,
-   * controller ruling / Task 6b). Flat optional STRING, not a literal
-   * union — same codegen ceiling as `attachPinUi` above (RN codegen cannot
-   * express a string-literal union in a struct field): the host-facing
-   * `RuntimeConfig.companionBadge.position` narrows to the real
-   * `'bottom-right' | 'bottom-left' | 'top-right' | 'top-left'` union and
-   * `extractBridgeConfig` passes it through unchanged onto this wire field.
-   * Each native side re-parses the string into its own
-   * `CompanionBadgePosition` enum, coercing `undefined`/an unrecognised
-   * value to `.bottomRight`/`BOTTOM_RIGHT` — the same default
-   * `CompanionBadgeOptions.position` already uses.
-   */
-  companionBadgePosition?: string;
   /**
    * Inline reporter theme (reporter branding spec 2026-08-25, RN slice) —
    * 8 optional `#rrggbb` role strings, flattened from the host-facing nested
    * `RuntimeConfig.theme` by `extractBridgeConfig` (RN codegen cannot express
-   * a nested object in a struct field — the `companionBadge` constraint
-   * above). Pure passthrough: NO hex validation happens on the RN side; each
+   * a nested object in a struct field). Pure passthrough: NO hex validation happens on the RN side; each
    * native ThemeResolver revalidates per-field and ignores invalid values.
    * The theme only ever renders once the server entitles it (server
    * `watermark: false`) — the entitlement gate lives natively and cannot be
@@ -216,7 +151,7 @@ export type ConfigOpts = {
   /**
    * Session Vitals local config (spec 2026-09-06, RN). Three FLAT fields
    * flattened from the host-facing nested `RuntimeConfig.vitals` by
-   * `extractBridgeConfig` — same codegen reason as `companionBadge*`.
+   * `extractBridgeConfig` — RN codegen rejects nested objects.
    * `vitalsEnabled`: absent = follow the dashboard toggle; `false` = opt out
    * locally; `true` never forces it on. `vitalsSampleRate`: [0, 1], min()'d
    * with the server rate, clamped natively; absent = server rate.
@@ -329,8 +264,7 @@ export interface Spec extends TurboModule {
    */
   setExtraResolverActive(active: boolean): void;
   /**
-   * Companion-precedent-shaped ack (mirrors `signalCompanionReportRequestReady`
-   * below exactly): called by the JS-side `everframe.extra.resolveRequested`
+   * Ack: called by the JS-side `everframe.extra.resolveRequested`
    * listener once it has — IF a resolver is currently registered — invoked
    * it, budgeted the result exactly like `@everframe/sdk-core`'s
    * `resolveClientExtra`, and pushed it through the existing `setExtra`
@@ -434,39 +368,11 @@ export interface Spec extends TurboModule {
    */
   captureHandledException(crashJson: string): boolean;
 
-  // ---------------- Phone-companion (Plan 06.2-11) ----------------
-  //
-  // Opens a TV-side RelayWSClient against the build-time-baked ingest URL
-  // (IngestEndpoint.url on each native SDK) and forwards
-  // `Everframe.shared.companion` state + pairUrl signals to JS via the
-  // platform's RN event-emitter (RCTDeviceEventEmitter on Android, a
-  // dedicated RCTEventEmitter subclass on iOS). The bridge owns at most ONE
-  // RelayWSClient per process.
-  //
-  // Emitted events (both platforms — see `src/companion.ts`):
-  //   • `everframe.companion.state`            → 'unpaired' | 'paired' | 'report_in_progress' | 'phone_disconnected'
-  //   • `everframe.companion.pairUrl`          → string | null
-  //   • `everframe.companion.code`             → string | null
-  //   • `everframe.companion.attachedUserName` → string | null
-  //   • `everframe.companion.resolvedName`     → string | null (naming spec 2026-08-24)
-  //   • `everframe.companion.attachChallenge`  → { code, requestedByName, ttlMs } | null (spec 2026-08-19)
-  startCompanion(): void;
-  stopCompanion(): void;
-  /**
-   * Companion handshake: called by the JS-side `onReportRequested` listener
-   * once it is ready for native capture to proceed. (It used to walk the
-   * React fiber tree and attach it via `attachReactTree` first; both are
-   * gone — spec 2026-08-29.) Releases the native bridge's bounded wait.
-   *
-   * Bounded: if JS never calls back, the native side times out after
-   * ~250ms and captures anyway.
-   */
-  signalCompanionReportRequestReady(correlationId: string): void;
+  // ---------------- Native event emitter ----------------
   /**
    * RN's `NativeEventEmitter` contract requires `addListener` /
    * `removeListeners` to exist on the underlying native module — RN warns
-   * loudly otherwise. Both are intentional no-ops at the spec level: the
-   * native event-emitter subscriptions are installed by `startCompanion`.
+   * loudly otherwise. Both are intentional no-ops at the spec level.
    */
   addListener(eventName: string): void;
   removeListeners(count: number): void;