@everframe/react-native 1.4.1 → 1.6.0

package/dist/NativeEverframe.d.ts

@@ -59,65 +59,21 @@ 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
@@ -134,7 +90,7 @@ 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.
@@ -232,8 +188,7 @@ 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`
@@ -320,23 +275,10 @@ interface Spec extends TurboModule {
      * non-fatal `reportCrash`, it may carry a session replay.
      */
     captureHandledException(crashJson: string): boolean;
-    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;
     /**
      * 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;

package/dist/index.d.ts

@@ -2,10 +2,10 @@ import * as React from 'react';
 import { EverframeUserSpec, ConfigOpts } from './NativeEverframe.js';
 export { Rect, Spec } from './NativeEverframe.js';
 import { E as EverframeIntegration } from './types-D5e4kWaw.js';
-import { R as ReportDeliveryStatus, E as ErrorCaptureStatus, P as PromiseRejectionStatus, a as ReporterOpenOptions, b as ReporterResult, c as ReporterTrigger, I as InteractionPolicyOptions, V as VitalsPlayerEventType, d as InteractionTargetAnnotation, e as InteractionHookOptions, C as ControlChangeInput, S as ScrollInput } from './launch-BvE4IjRk.js';
-export { A as AttachmentRef, f as ErrorCaptureCounters, g as ErrorCaptureOutcome, h as ErrorCapturePath, i as EverframeNotMountedError, j as EverframeReporterDisabledError, H as HelperType, L as LaunchContext, k as PermissionResult, l as PromiseRejectionCounters, m as RejectionReason, n as ReportCaptureOutcome, o as ReportCapturePath, p as ReportCapturePathStatus, q as ReportDeliveryReason, r as ReportEnvelope, s as ReportQueueOperation, t as ReportQueueStatus, u as ReportStorageFailure, v as ReportTransportOrigin, w as ReportTransportOutcome, x as ReportTransportStatus, U as UINode, y as UITree, z as observePermissionRequest, B as recordLaunchContext } from './launch-BvE4IjRk.js';
+import { R as ReportDeliveryStatus, E as ErrorCaptureStatus, P as PromiseRejectionStatus, a as ReporterOpenOptions, b as ReporterResult, c as ReporterTrigger, I as InteractionPolicyOptions, V as VitalsPlayerEventType, d as InteractionTargetAnnotation, e as InteractionHookOptions, C as ControlChangeInput, S as ScrollInput } from './launch-aXtOOfNU.js';
+export { A as AttachmentRef, f as ErrorCaptureCounters, g as ErrorCaptureOutcome, h as ErrorCapturePath, i as EverframeNotMountedError, j as EverframeReporterDisabledError, H as HelperType, L as LaunchContext, k as PermissionResult, l as PromiseRejectionCounters, m as RejectionReason, n as ReportCaptureOutcome, o as ReportCapturePath, p as ReportCapturePathStatus, q as ReportDeliveryReason, r as ReportEnvelope, s as ReportQueueOperation, t as ReportQueueStatus, u as ReportStorageFailure, v as ReportTransportOrigin, w as ReportTransportOutcome, x as ReportTransportStatus, U as UINode, y as UITree, z as observePermissionRequest, B as recordLaunchContext } from './launch-aXtOOfNU.js';
 import { z } from 'zod';
-import { ViewProps, EventSubscription } from 'react-native';
+import { ViewProps } from 'react-native';
 
 interface JsBundleConfig {
     buildId: string;
@@ -119,8 +119,7 @@ interface EverframeContextValue {
      * chance for the host to refresh a pushed snapshot first — see the fuller
      * rationale on `@everframe/sdk-core`'s `EverframeClient.setExtra`. The
      * resolver is stored, never called at registration time; native ASKS for
-     * it (a bounded round trip to JS, mirroring the companion
-     * `reportRequested` handshake) right before it drains pending attachments
+     * it (a bounded round trip to JS) right before it drains pending attachments
      * for a report, so it always sees current values with no effect to write
      * or keep in sync. A throwing resolver never breaks the report: it is
      * caught, warned, and `extra` is simply omitted from that report — same
@@ -219,18 +218,12 @@ declare function markReporterClosed(): Promise<void>;
  * host-defined, it's owned by the SDK and stamped per release on the native
  * side (`Everframe.SDK_VERSION`). See extractBridgeConfig.
  *
- * External review, finding NN4 — also OMITS `companionBadgeEnabled` /
- * `companionBadgePosition`, the FLAT wire-shaped fields `ConfigOpts` declares
- * for codegen (RN codegen cannot express the nested `{ enabled, position }`
- * object at all — see `companionBadge` below). Without this, `RuntimeConfig`
- * structurally inherited BOTH the flat wire fields AND the nested
- * `companionBadge` declared below, so `{ companionBadgeEnabled: false }`
- * type-checked as a valid host config and silently no-opped: `extractBridge
- * Config` only ever reads the nested `companionBadge` object, never the flat
- * keys, so a host reaching for the (also-valid-looking) flat shape got no
- * error and no effect. Omitting them here makes `companionBadge` the ONLY
- * public surface for this option — passing the flat form is now a
- * compile-time error, matching the runtime's actual (nested-only) behavior.
+ * External review, finding NN4 — also OMITS the FLAT wire-shaped fields
+ * `ConfigOpts` declares for codegen wherever a nested host-facing option
+ * exists below (RN codegen cannot express nested objects). Without the Omit,
+ * `RuntimeConfig` structurally inherits BOTH shapes, and the flat one
+ * type-checks as a valid host config and silently no-ops, because
+ * `extractBridgeConfig` only ever reads the nested object.
  * Deliberately NOT applied to `networkBodiesDisabled`, even though the same
  * shape of gap arguably exists there too (`RuntimeConfig` also declares its
  * own nested `networkBodies?: { disabled? }` below, alongside the inherited
@@ -238,7 +231,7 @@ declare function markReporterClosed(): Promise<void>;
  * review instruction, left as pre-existing behavior rather than folded in
  * here.
  */
-interface RuntimeConfig extends Omit<ConfigOpts, 'sdkVersion' | 'interactionsJson' | 'installIdentifierDisabled' | 'crashReportingDisabled' | 'companionBadgeEnabled' | 'companionBadgePosition' | 'shakeToReportEnabled' | 'reporterDisabled' | 'themeBackground' | 'themeSurface' | 'themeBorder' | 'themeText' | 'themeTextMuted' | 'themeAccent' | 'themeAccentForeground' | 'themeDestructive' | 'vitalsEnabled' | 'vitalsSampleRate' | 'vitalsCaptureSourceQuery' | 'releaseHealthEnabled' | 'releaseHealthLoadedBuildId' | 'releaseHealthUserId' | 'releaseHealthIncludeDebugBuilds'> {
+interface RuntimeConfig extends Omit<ConfigOpts, 'sdkVersion' | 'interactionsJson' | 'installIdentifierDisabled' | 'crashReportingDisabled' | 'shakeToReportEnabled' | 'quickCaptureEnabled' | 'reporterDisabled' | 'themeBackground' | 'themeSurface' | 'themeBorder' | 'themeText' | 'themeTextMuted' | 'themeAccent' | 'themeAccentForeground' | 'themeDestructive' | 'vitalsEnabled' | 'vitalsSampleRate' | 'vitalsCaptureSourceQuery' | 'releaseHealthEnabled' | 'releaseHealthLoadedBuildId' | 'releaseHealthUserId' | 'releaseHealthIncludeDebugBuilds'> {
     /**
      * Per-app SDK key (publishable, not secret). Required on the host-facing
      * config — narrows the bridge `ConfigOpts.sdkKey?` to required so a missing
@@ -324,49 +317,56 @@ interface RuntimeConfig extends Omit<ConfigOpts, 'sdkVersion' | 'interactionsJso
         disabled?: boolean;
     };
     /**
-     * Built-in attach-PIN surface mode (spec 2026-08-19). Narrows the bridge
-     * `ConfigOpts.attachPinUi?: string` to a literal union here — the flat
-     * `string` on `ConfigOpts` is a codegen constraint on the WIRE type only
-     * (RN codegen can't express a string-literal union in a struct field, see
-     * `NativeEverframe.ts`'s D-decision header note); this host-facing surface
-     * doesn't cross codegen and gets normal DX. `extractBridgeConfig` passes
-     * it through unchanged — the union is a subtype of `string`, so no
-     * conversion is needed, same as `captureScreenshot` above.
+     * Accepted and ignored.
+     *
+     * @deprecated Everframe Companion has been removed; this call does nothing. Link the device under Settings → Devices in the dashboard and use quick capture.
      */
     attachPinUi?: 'builtin' | 'custom' | 'off';
     /**
-     * Companion on-screen name-badge visibility/position (naming spec
-     * 2026-08-24, controller ruling / Task 6b) — lets a host that finds the
-     * badge intrusive turn it off in one line: `companionBadge: { enabled:
-     * false }`. Nested host-facing shape, unlike `attachPinUi` above: RN
-     * codegen cannot express a nested object in a struct field at all (not
-     * even a flat one with a narrowed literal-union member), so
-     * `extractBridgeConfig` flattens both fields onto the wire `ConfigOpts`
-     * (`companionBadgeEnabled`/`companionBadgePosition`) — the same
-     * flattening idiom `networkBodies.disabled` → `networkBodiesDisabled`
-     * above already uses for the same reason.
+     * Accepted and ignored.
+     *
+     * @deprecated Everframe Companion has been removed; this call does nothing. Link the device under Settings → Devices in the dashboard and use quick capture.
+     */
+    companionDeviceId?: string;
+    /**
+     * Accepted and ignored.
+     *
+     * @deprecated Everframe Companion has been removed; this call does nothing. Link the device under Settings → Devices in the dashboard and use quick capture.
      */
     companionBadge?: {
         enabled?: boolean;
         position?: 'bottom-right' | 'bottom-left' | 'top-right' | 'top-left';
     };
     /**
-     * Native mobile shake gesture. Enabled by default; the dashboard remains
-     * authoritative. React Native/Expo development builds should normally use
-     * `{ enabled: !__DEV__ }` to avoid overlapping with the development menu.
+     * Whether a shake opens the reporter on an unlinked release build. Enabled
+     * by default; the dashboard remains authoritative. It does not stop shake
+     * from taking a quick capture on a linked phone or a debug build, nor from
+     * answering a dashboard link window: that is `quickCapture`'s job. React
+     * Native/Expo development builds should normally use `{ enabled: !__DEV__ }`
+     * to avoid opening the reporter over the development menu.
      */
     shakeToReport?: {
         enabled?: boolean;
     };
+    /**
+     * Quick capture: a report filed with no UI and titled on the dashboard.
+     * Simulators and emulators use ⇧B in debug builds. Real phones use shake
+     * when the device is linked on the dashboard (any build) or the build is a
+     * debug build (`__DEV__`, or `debugBuild`); Android TV uses the remote
+     * gesture the dashboard sets, under the same rule. Enabled by default; the
+     * dashboard remains authoritative. `{ enabled: false }` opts this app out
+     * of quick capture everywhere, and of device linking.
+     */
+    quickCapture?: {
+        enabled?: boolean;
+    };
     /**
      * Crash-only session switch (spec 2026-10-12). CLIENT VETO only.
      * `disabled: true` turns off every on-device way to open the reporter
      * (shake, `open()`, which then rejects with
      * `EverframeReporterDisabledError`), keeps network bodies off and samples
      * session replay with the server's crash-only rate (default 0) instead of
-     * the normal one. A companion bond upgrades the session: replay and bodies
-     * then follow the normal server rules for the rest of the session, and
-     * reports come through the companion. Crash and error capture are
+     * the normal one. Crash and error capture are
      * unaffected. Flattened onto `ConfigOpts.reporterDisabled` by
      * `extractBridgeConfig`.
      */
@@ -378,8 +378,8 @@ interface RuntimeConfig extends Omit<ConfigOpts, 'sdkVersion' | 'interactionsJso
      * 8 optional `#rrggbb` role strings for the NATIVE report dialogs the RN
      * SDK presents (`open()`); RN itself renders no reporter UI. Nested
      * host-facing shape, flattened onto the 8 flat `ConfigOpts.theme*` wire
-     * fields by `extractBridgeConfig` — the same idiom (and codegen reason) as
-     * `companionBadge` above.
+     * fields by `extractBridgeConfig` (RN codegen cannot express nested
+     * objects).
      *
      * Rendering is entitlement-gated NATIVELY per the branding contract
      * (precedence server → inline → default): the theme applies only when the
@@ -509,151 +509,44 @@ declare function trackVitals(name: string, data?: unknown, player?: PlayerHandle
  */
 declare function useTrackPlayer(opts: TrackPlayerOptions): PlayerHandle;
 
-/**
- * SDK-facing listener surface. React Native 0.87 intentionally types raw
- * native payloads as `Object[]`; each Everframe event has a narrower bridge
- * contract, so the unchecked native boundary is centralized here instead of
- * repeated at every listener.
- */
-type EverframeNativeEventEmitter = {
-    addListener<Args extends readonly unknown[]>(eventType: string, listener: (...args: Args) => unknown): EventSubscription;
-};
-/**
- * Resolve the platform's RN event emitter source. iOS hands listeners to a
- * dedicated `RCTEventEmitter` subclass (`EverframeEventEmitter`); Android
- * uses the default `RCTDeviceEventEmitter` which `NativeEventEmitter`
- * routes to when constructed with no argument.
- */
-declare function getEmitter(): EverframeNativeEventEmitter;
-
-/**
- * Companion runtime state — mirrors `CompanionState` in iOS (rawValue) +
- * Android (mapped from the enum via `toRnString`). Keep this union in
- * lock-step with both native sides.
- */
+/** @deprecated Everframe Companion has been removed; this call does nothing. Link the device under Settings → Devices in the dashboard and use quick capture. */
 type CompanionState = 'unpaired' | 'paired' | 'report_in_progress' | 'phone_disconnected';
-/**
- * A pending dashboard-initiated attach-PIN challenge (spec 2026-08-19).
- * Mirrors iOS `CompanionAttachChallenge` / Android `AttachChallengeInfo`.
- * The natives forward this event in every `attachPinUi` mode, including
- * `'builtin'` (which renders the PIN natively AND still fires the event) —
- * it's only NEEDED by hosts configured with `'custom'`, which must read it
- * to build their own surface.
- */
+/** @deprecated Everframe Companion has been removed; this call does nothing. Link the device under Settings → Devices in the dashboard and use quick capture. */
 interface CompanionAttachChallenge {
     code: string;
     requestedByName: string;
-    /** Display lifetime — custom UIs should hide the code after this. */
     ttlMs: number;
 }
 /**
- * Open the relay WS connection. The native bridge owns at most one client
- * per process and `start()` is idempotent: calling it again while the
- * companion is already running is a no-op — the socket is NOT recreated.
- * Call `stop()` first, then `start()`, to tear the connection down and open
- * a fresh one.
+ * Logs the removal warning once. Reaches no native code and never throws.
  *
- * The ingest URL is no longer a JS-side argument — the native SDKs bake it
- * at compile time (Release: https://everframe.dev; Debug: optionally
- * overridden via EVERFRAME_DEV_INGEST_URL on each native build).
+ * @deprecated Everframe Companion has been removed; this call does nothing. Link the device under Settings → Devices in the dashboard and use quick capture.
  */
 declare function start(): void;
 /**
- * Close the relay WS. The observable state retains its last value — hosts
- * can still read `useCompanion().state` afterwards to render a "paused"
- * indicator. Re-call `start(...)` to reconnect.
- */
-declare function stop(): void;
-/**
- * Subscribe to the "is a session wanted" intent flag (see `_running` above).
- * Returns an unsubscribe function. Use this directly from imperative code;
- * React components should prefer `useCompanion().running`.
- */
-declare function onRunning(handler: (running: boolean) => void): () => void;
-/**
- * Subscribe to companion-state changes. Returns an unsubscribe function.
- * Use this directly from imperative code (e.g. an Activity-lifecycle hook);
- * React components should prefer `useCompanion()`.
- */
-declare function onState(handler: (state: CompanionState) => void): () => void;
-/**
- * Subscribe to pairUrl changes. The URL is set on `pair.created` and retained
- * for the life of the relay socket — it's nulled only when the socket closes
- * (terminal/permanent close). It does NOT flip to null on bond or expiry; drive
- * QR teardown off `state` (e.g. hide once `state === 'paired'`) instead, since
- * `state` is the reliably-delivered signal across the native bridge.
- */
-declare function onPairUrl(handler: (url: string | null) => void): () => void;
-/**
- * Subscribe to the announce display code — the short string the dashboard
- * shows next to this device in the project's Companion list, so a team member
- * can match what they read on the TV screen to a row in the list.
+ * Does nothing.
  *
- * `null` when companion discovery was never attempted (no SDK key configured
- * on the native side), when the announce call failed, and after the relay
- * socket closes terminally. A null code costs discovery only — pairing by QR
- * and report submission are unaffected, so never gate the QR on it.
+ * @deprecated Everframe Companion has been removed; this call does nothing. Link the device under Settings → Devices in the dashboard and use quick capture.
  */
-declare function onCode(handler: (code: string | null) => void): () => void;
-/**
- * Subscribe to the attached dashboard member's display name. Populated only
- * when someone attached to this device FROM the dashboard; an ordinary QR
- * bond carries no such name and leaves this `null`. Render it as e.g.
- * "Paired with <name>" — but drive the paired/unpaired chrome itself off
- * `state`, which is the reliably-delivered signal.
- */
-declare function onAttachedUserName(handler: (name: string | null) => void): () => void;
-/**
- * Subscribe to the server-resolved device display name (naming spec
- * 2026-08-24) — e.g. an org-configured friendly name for this device.
- * `null` before the first successful announce, and when discovery never ran
- * (no SDK key configured on the native side).
- *
- * REPLAY SEMANTIC (external review, finding N5): RN events don't replay to
- * listeners attached after they fired, so a name resolved by an announce
- * that ran before this call would otherwise be invisible to it until the
- * NEXT announce. If `start()` has already cached a resolved name, `handler`
- * is invoked synchronously, immediately, with that cached value — before
- * this function returns, in addition to firing on every later event. Mirrors
- * `onAttachChallenge`'s replay idiom exactly, minus the ttlMs
- * recomputation (a resolved name has no lifetime to recompute).
- */
-declare function onResolvedName(handler: (name: string | null) => void): () => void;
-/**
- * Subscribe to attach-PIN challenges (spec 2026-08-19). Fires with the live
- * challenge when a dashboard member requests attach, and null when it
- * clears (redeemed, expired, burned, superseded, socket closed). The
- * natives fire this event in every `attachPinUi` mode, including
- * `'builtin'` (which renders the PIN natively AND still fires the event) —
- * it's only NEEDED for `'custom'` hosts, which must read it to build their
- * own surface.
- *
- * REPLAY SEMANTIC: RN events don't replay to listeners attached after they
- * fired, so a challenge that arrived before this call would otherwise be
- * invisible to it. If `start()` has already cached a still-live challenge,
- * `handler` is invoked synchronously, immediately, with that cached value —
- * `ttlMs` recomputed as the time REMAINING until its deadline, never the
- * original duration (review finding 4) — before this function returns, in
- * addition to firing on every later event. A cached challenge whose deadline
- * has already passed replays nothing (`attachChallengeReplayValue()` returns
- * null), matching the semantics of a challenge that was never cached at all.
- */
-declare function onAttachChallenge(handler: (challenge: CompanionAttachChallenge | null) => void): () => void;
+declare function stop(): void;
+/** @deprecated Everframe Companion has been removed; this call does nothing. Link the device under Settings → Devices in the dashboard and use quick capture. */
+declare function onRunning(_handler: (running: boolean) => void): () => void;
+/** @deprecated Everframe Companion has been removed; this call does nothing. Link the device under Settings → Devices in the dashboard and use quick capture. */
+declare function onState(_handler: (state: CompanionState) => void): () => void;
+/** @deprecated Everframe Companion has been removed; this call does nothing. Link the device under Settings → Devices in the dashboard and use quick capture. */
+declare function onPairUrl(_handler: (url: string | null) => void): () => void;
+/** @deprecated Everframe Companion has been removed; this call does nothing. Link the device under Settings → Devices in the dashboard and use quick capture. */
+declare function onCode(_handler: (code: string | null) => void): () => void;
+/** @deprecated Everframe Companion has been removed; this call does nothing. Link the device under Settings → Devices in the dashboard and use quick capture. */
+declare function onAttachedUserName(_handler: (name: string | null) => void): () => void;
+/** @deprecated Everframe Companion has been removed; this call does nothing. Link the device under Settings → Devices in the dashboard and use quick capture. */
+declare function onResolvedName(_handler: (name: string | null) => void): () => void;
+/** @deprecated Everframe Companion has been removed; this call does nothing. Link the device under Settings → Devices in the dashboard and use quick capture. */
+declare function onAttachChallenge(_handler: (challenge: CompanionAttachChallenge | null) => void): () => void;
 /**
- * React hook returning the latest `{ state, pairUrl, code, attachedUserName, attachChallenge }`
- * snapshot. Mounts one NativeEventEmitter subscription per value and tears
- * them all down on unmount.
- *
- * Subscribing is safe to tie to a component; the SESSION is not. Binding
- * `stop()` to unmount means the device stops advertising the moment the
- * screen goes away — including when the user navigates off to the dashboard
- * to attach to it — so prefer starting on mount and ending on an explicit
- * user action. `examples/react-native/src/screens/Companion.tsx` shows that
- * shape, with a module-scoped flag carrying the user's intent across mounts.
+ * Returns the idle Companion snapshot — the same object on every render.
  *
- * Note that `stop()` retains the last `state` and `pairUrl` rather than
- * clearing them, so a stopped session must be rendered from your own flag —
- * rendering off `state` alone leaves a dead QR on screen.
+ * @deprecated Everframe Companion has been removed; this call does nothing. Link the device under Settings → Devices in the dashboard and use quick capture.
  */
 declare function useCompanion(): {
     state: CompanionState;
@@ -667,7 +560,6 @@ declare function useCompanion(): {
 
 type companion_CompanionAttachChallenge = CompanionAttachChallenge;
 type companion_CompanionState = CompanionState;
-declare const companion_getEmitter: typeof getEmitter;
 declare const companion_onAttachChallenge: typeof onAttachChallenge;
 declare const companion_onAttachedUserName: typeof onAttachedUserName;
 declare const companion_onCode: typeof onCode;
@@ -679,7 +571,7 @@ declare const companion_start: typeof start;
 declare const companion_stop: typeof stop;
 declare const companion_useCompanion: typeof useCompanion;
 declare namespace companion {
-  export { type companion_CompanionAttachChallenge as CompanionAttachChallenge, type companion_CompanionState as CompanionState, companion_getEmitter as getEmitter, companion_onAttachChallenge as onAttachChallenge, companion_onAttachedUserName as onAttachedUserName, companion_onCode as onCode, companion_onPairUrl as onPairUrl, companion_onResolvedName as onResolvedName, companion_onRunning as onRunning, companion_onState as onState, companion_start as start, companion_stop as stop, companion_useCompanion as useCompanion };
+  export { type companion_CompanionAttachChallenge as CompanionAttachChallenge, type companion_CompanionState as CompanionState, companion_onAttachChallenge as onAttachChallenge, companion_onAttachedUserName as onAttachedUserName, companion_onCode as onCode, companion_onPairUrl as onPairUrl, companion_onResolvedName as onResolvedName, companion_onRunning as onRunning, companion_onState as onState, companion_start as start, companion_stop as stop, companion_useCompanion as useCompanion };
 }
 
 /** Optional semantic metadata on an existing native host ref. Reporting works without it. */