react-native-image-stitcher 0.3.0 → 0.4.1

package/dist/camera/PanoramaSettingsBridge.js

@@ -0,0 +1,208 @@
+"use strict";
+// SPDX-License-Identifier: Apache-2.0
+/**
+ * PanoramaSettingsBridge — JS-side adapters that convert the v0.4
+ * typed `PanoramaSettings` / `SlitscanSettings` / `HybridSettings`
+ * shape into the flat `configOverrides` dictionary the native
+ * bridges read.
+ *
+ * Why this file exists
+ * ────────────────────
+ *
+ * The v0.4 types use hierarchical sub-trees (`stitcher`,
+ * `frameSelection.flow`, `painting`, `registration.ncc1d`,
+ * `registration.ncc2d.emaSmoothing`, `plane`, …) to give consumers
+ * a clean, ergonomic settings surface that mirrors the native
+ * engine's domain.  But the native bridges (iOS Swift's
+ * `applyConfigOverrides`, Android Kotlin's `IncrementalStitcher.start`)
+ * read a FLAT dictionary of native-named keys (e.g. `nccSearchRadius1d`,
+ * `enable1dNcc`, `ncc2dEmaAlpha`, `flowMaxTranslationCm`).
+ *
+ * Two semantic gaps to bridge:
+ *
+ *   1. **Naming.**  JS `registration.ncc1d.searchRadius` →
+ *      native `nccSearchRadius1d`.  JS `painting.paintMode` →
+ *      native `paintMode` (same).  Etc.
+ *
+ *   2. **Presence-as-enable.**  The native side reads explicit
+ *      `enable1dNcc`, `enable2dNcc`, `enableNcc2dEmaSmoothing`,
+ *      `enableNcc2dPanAxisLock` booleans.  JS models these as
+ *      optional sub-objects (sub-object present ⇒ enabled).  This
+ *      adapter flattens the booleans for the wire.
+ *
+ *   3. **Skipped engine defaults.**  Hybrid engine presets internally
+ *      clobber most fields (see HybridSettings JSDoc), so we don't
+ *      send overrides that would be ignored — just the small useful
+ *      surface.
+ *
+ * The Camera component calls `panoramaSettingsToNativeConfig` once
+ * per capture start to produce the value passed as
+ * `incremental.start({ config: … })`.  Layer 2 callers building
+ * SlitscanSettings or HybridSettings call the matching adapter
+ * before reaching `incremental.start()`.
+ */
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.panoramaSettingsToNativeConfig = panoramaSettingsToNativeConfig;
+exports.slitscanSettingsToNativeConfig = slitscanSettingsToNativeConfig;
+exports.hybridSettingsToNativeConfig = hybridSettingsToNativeConfig;
+const PanoramaSettings_1 = require("./PanoramaSettings");
+/**
+ * Convert a v0.4 PanoramaSettings tree into the flat dict the
+ * batch-keyframe native side reads.  Maps every consumed field
+ * exactly once and skips fields the engine doesn't reach.
+ *
+ * Verified against:
+ *   - iOS  `IncrementalStitcher.swift:810-960` (batch path)
+ *   - Android `IncrementalStitcher.kt:280-430` (batch path)
+ */
+function panoramaSettingsToNativeConfig(s) {
+    const cfg = {
+        // ── Cross-cutting ────────────────────────────────────────────
+        captureSource: s.captureSource,
+        // ── BatchStitcherSettings → cv::Stitcher knobs ───────────────
+        stitchMode: s.stitcher.stitchMode,
+        warperType: s.stitcher.warperType,
+        blenderType: s.stitcher.blenderType,
+        seamFinderType: s.stitcher.seamFinderType,
+        enableMaxInscribedRectCrop: s.stitcher.enableMaxInscribedRectCrop,
+        // ── FrameSelectionSettings → KeyframeGate knobs ──────────────
+        frameSelectionMode: s.frameSelection.mode,
+        keyframeMaxCount: s.frameSelection.maxKeyframes,
+        keyframeOverlapThreshold: s.frameSelection.overlapThreshold,
+    };
+    // Flow strategy knobs — always serialised, regardless of
+    // `frameSelection.mode`.  Two reasons:
+    //
+    //   1. Mode-flip-mid-session: hosts can change `mode` without
+    //      restarting capture; consistent flow serialisation means
+    //      `'time-based' → 'flow-based'` mid-session doesn't slip
+    //      back to stale native-side defaults.  Native ignores these
+    //      keys when the active mode doesn't use them.
+    //
+    //   2. **Native compiled-in defaults disagree with the JS
+    //      defaults.**  Specifically: native sets `flowMaxTranslationCm
+    //      = 0` and `flowEvalEveryNFrames = 1` when the keys are
+    //      missing (iOS `IncrementalStitcher.swift:1003-1029`,
+    //      Android `IncrementalStitcher.kt:419-445`), whereas the JS
+    //      `DEFAULT_PANORAMA_SETTINGS.frameSelection.flow` values are
+    //      `50` and `5`.  Hosts who write sparse settings literals
+    //      (omitted `flow` sub-tree, legal per the optional `?`)
+    //      would silently get IMU translation gate disabled and
+    //      ~5× CPU on flow evaluation — a v0.3-style behaviour
+    //      regression on the wire that the type system can't catch.
+    //      Filling from `DEFAULT_FLOW_GATE_SETTINGS` here closes the
+    //      gap; the JS defaults become the canonical defaults across
+    //      both layers.
+    //
+    // See the F10 Phase 2 review (B1 + N3 + N6) for the full
+    // discussion of why this matters.
+    const f = s.frameSelection.flow ?? PanoramaSettings_1.DEFAULT_FLOW_GATE_SETTINGS;
+    cfg.flowNoveltyPercentile = f.noveltyPercentile;
+    cfg.flowEvalEveryNFrames = f.evalEveryNFrames;
+    cfg.flowMaxTranslationCm = f.maxTranslationCm;
+    cfg.flowMaxCorners = f.maxCorners;
+    cfg.flowQualityLevel = f.qualityLevel;
+    cfg.flowMinDistance = f.minDistance;
+    return cfg;
+}
+/**
+ * Convert a v0.4 SlitscanSettings tree into the flat dict the
+ * slit-scan / firstwins native engines read.  Handles the
+ * "presence-as-enable" boolean expansion: a non-undefined
+ * `registration.ncc1d` means `enable1dNcc: true` on the wire,
+ * with the sub-object's `searchRadius` carried alongside.
+ *
+ * Verified against:
+ *   - iOS  `IncrementalStitcher.swift:1006-1100` (applyConfigOverrides)
+ *   - iOS  `OpenCVSlitScanStitcher.mm` (all numbered references in
+ *          the audit ground-truth matrix)
+ */
+function slitscanSettingsToNativeConfig(s) {
+    const cfg = {
+        captureSource: s.captureSource,
+        // The native side reads `engine: 'slitscan-…'` at start time
+        // from a separate top-level field, NOT from configOverrides.
+        // We still serialise the variant here for hosts that want to
+        // round-trip a single settings object through both surfaces.
+        engineVariant: s.variant,
+        // ── Painting ─────────────────────────────────────────────────
+        paintMode: s.painting.paintMode,
+        sliverPosition: s.painting.sliverPosition,
+        firstFrameFullFrame: s.painting.firstFrameFullFrame,
+        // ── Registration (explicit booleans) ─────────────────────────
+        enableTriangulation: s.registration.enableTriangulation,
+        enableTriAccumulator: s.registration.enableTriAccumulator,
+        enableRansacHomography: s.registration.enableRansacHomography,
+        // ── Plane projection ─────────────────────────────────────────
+        planeSource: s.plane.source,
+    };
+    // ── 1D NCC: presence-as-enable ─────────────────────────────────
+    if (s.registration.ncc1d) {
+        cfg.enable1dNcc = true;
+        cfg.nccSearchRadius1d = s.registration.ncc1d.searchRadius;
+    }
+    else {
+        cfg.enable1dNcc = false;
+    }
+    // ── 2D NCC: presence-as-enable + nested optionals ──────────────
+    if (s.registration.ncc2d) {
+        const n2 = s.registration.ncc2d;
+        cfg.enable2dNcc = true;
+        cfg.nccSearchMargin2d = n2.searchMargin;
+        cfg.nccConfidenceThreshold2d = n2.confidenceThreshold;
+        if (n2.emaSmoothing) {
+            cfg.enableNcc2dEmaSmoothing = true;
+            cfg.ncc2dEmaAlpha = n2.emaSmoothing.alpha;
+        }
+        else {
+            cfg.enableNcc2dEmaSmoothing = false;
+        }
+        if (n2.panAxisLock) {
+            cfg.enableNcc2dPanAxisLock = true;
+            cfg.ncc2dCrossAxisLockPx = n2.panAxisLock.crossAxisLockPx;
+        }
+        else {
+            cfg.enableNcc2dPanAxisLock = false;
+        }
+    }
+    else {
+        cfg.enable2dNcc = false;
+    }
+    // ── Plane optionals ────────────────────────────────────────────
+    // Only emit when `source` actually consumes the field.  Native
+    // tolerates unsolicited keys but the modal also walks the dict
+    // to decide which sliders to render — extra keys would mislead.
+    if (s.plane.source !== 'Disabled' && s.plane.projectionStyle !== undefined) {
+        cfg.planeProjectionStyle = s.plane.projectionStyle;
+    }
+    if (s.plane.source === 'Virtual' && s.plane.virtualDepthMeters !== undefined) {
+        cfg.virtualPlaneDepthMeters = s.plane.virtualDepthMeters;
+    }
+    if (s.plane.source === 'ARKitDetected' && s.plane.alignmentThreshold !== undefined) {
+        cfg.arkitPlaneAlignmentThreshold = s.plane.alignmentThreshold;
+    }
+    // ── Advanced motion knobs (only emit if explicitly set) ────────
+    if (s.advanced?.panAxisFractionRect !== undefined) {
+        cfg.kPanAxisFractionRect = s.advanced.panAxisFractionRect;
+    }
+    if (s.advanced?.minAcceptDeltaPx !== undefined) {
+        cfg.kMinAcceptDeltaPx = s.advanced.minAcceptDeltaPx;
+    }
+    return cfg;
+}
+/**
+ * Convert a v0.4 HybridSettings tree into the flat dict the hybrid
+ * engine reads.  Minimal surface — hybrid presets internally clobber
+ * almost everything; see HybridSettings JSDoc for context.
+ *
+ * Verified against:
+ *   - iOS  `OpenCVIncrementalStitcher.mm:139-180` (preset paths)
+ *   - iOS  `IncrementalStitcher.swift:1034-1040` (hybridProjection override)
+ */
+function hybridSettingsToNativeConfig(s) {
+    return {
+        captureSource: s.captureSource,
+        hybridProjection: s.projection,
+    };
+}
+//# sourceMappingURL=PanoramaSettingsBridge.js.map

package/dist/camera/PanoramaSettingsModal.d.ts

@@ -1,307 +1,58 @@
 /**
- * PanoramaSettingsModal — runtime A/B testing surface for the
- * stitcher pipeline.  Operators in the field can toggle warper,
- * blender, and tuning constants between captures to see what
- * looks best on real shelf scenes.
+ * PanoramaSettingsModal — runtime tuning surface for <Camera>'s
+ * batch-keyframe panorama capture.
  *
- * The modal is presentational: the host owns the settings state
- * (typically `useState<PanoramaSettings>`) and renders the modal
- * with `visible` toggled by a gear-icon press in the capture
- * header.  Settings flow OUT via `onChange` for each tweak.
+ * v0.4 rewrite (Phase 2 of F10):
+ * ──────────────────────────────
  *
- * Why expose this as an SDK component instead of leaving it to
- * each host?  The set of tunable knobs IS the SDK's contract —
- * if a new setting is added (e.g. registration MP) the SDK ships
- * the UI for it in lockstep with the param itself, instead of
- * forcing every host app to update its settings screen.
+ * The v0.3 modal exposed a flat 45-field surface that mixed
+ * batch-keyframe knobs with slit-scan, hybrid, and video-recording
+ * fallback fields the engine never reads in <Camera>'s
+ * `engine: 'batch-keyframe'` path.  The 2026-05-22 audit (v0.3.0
+ * CHANGELOG) traced every field's native consumer and proved most of
+ * the cross-engine fields were dead surface in this modal.
+ *
+ * v0.4 narrows the modal to exactly the surface <Camera> consumes:
+ * the `PanoramaSettings` type defined in `./PanoramaSettings.ts`.  Each
+ * section in the modal mirrors a sub-tree of that type — operators see
+ * the same shape in the UI as the code, and host apps that want to
+ * tune slit-scan or hybrid engines build their own analogous
+ * SlitscanSettingsModal / HybridSettingsModal on top of those types.
+ *
+ * UI structure (matches the type tree):
+ *
+ *   - Debug                       (top-level, `debug`)
+ *   - Frame selection             (`frameSelection`, closed by default)
+ *       - Mode
+ *       - Max keyframes
+ *       - Overlap threshold
+ *       - Flow tunables           (`frameSelection.flow`, only when
+ *                                  mode === 'flow-based')
+ *           - Max corners
+ *           - Quality level
+ *           - Min distance
+ *           - Max translation cm
+ *           - Novelty percentile
+ *           - Eval every N frames
+ *   - Stitcher                    (`stitcher`, closed by default)
+ *       - Stitch mode
+ *       - Warper type
+ *       - Blender
+ *       - Seam finder
+ *       - Inscribed-rect crop
+ *   - Reset to defaults           (button)
+ *
+ * Note: `captureSource` (AR vs non-AR) is NOT surfaced here.  The
+ * camera-screen AR toggle owns that state — Camera.tsx overrides the
+ * native bridge's `captureSource` with the derived
+ * `effectiveCaptureSource` so settings and runtime stay in sync.
+ *
+ * The reusable `Accordion` + `SectionHeader` + `SegmentedControl` +
+ * `Tag` helpers from the v0.3 modal are preserved verbatim — only the
+ * data-binding layer changed.
  */
 import React from 'react';
-export interface PanoramaSettings {
-    warperType: 'plane' | 'cylindrical' | 'spherical';
-    blenderType: 'multiband' | 'feather';
-    /**
-     * Seam finder strategy.  "graphcut" finds optimal seams before
-     * blending (cleaner output, pairs with multiband, more memory).
-     * "skip" streams warp+feed (lower peak memory, fine with feather).
-     */
-    seamFinderType: 'graphcut' | 'skip';
-    /**
-     * V16 Phase 1b.fix5c (Ram's call 2026-05-10) — toggle the
-     * max-inscribed-rectangle crop on the batch-keyframe output
-     * panorama.  When false (default), the output is cropped to the
-     * bounding rectangle of non-black pixels only (cv::boundingRect)
-     * — preserves all stitched content at the cost of some black
-     * corners where cv::Stitcher's projection didn't fill.  When
-     * true, the post-stitch pipeline additionally runs
-     * `MaxInscribedRectFromMask` to find the largest axis-aligned
-     * rectangle entirely inside content, followed by the
-     * column-projection second-pass.  Inscribed-rect can be
-     * over-aggressive on lopsided masks (field log showed a
-     * 1146×1102 bbox shrinking to a 602×1102 strip), so default OFF
-     * lets the operator see the full stitched scene; flip ON to
-     * A/B against the cleaner-but-smaller output.
-     */
-    enableMaxInscribedRectCrop: boolean;
-    /**
-     * Phase 4.4 EXPERIMENTAL: when true, the host swaps the
-     * vision-camera-backed CameraView for an ARKit-backed ARCameraView
-     * during panorama capture.  Default false (keeps the existing
-     * stitcher flow untouched).  Phase 5 will add AR-backed photo /
-     * video capture and pose-driven stitching; until then this is
-     * preview-only — useful for verifying the AR session renders
-     * cleanly on the operator's device before we cut over.
-     */
-    useARPreview: boolean;
-    /**
-     * V15 — Incremental engine choice for live realtime stitching.
-     *   'hybrid'           — Whole-frame projection + feature matching;
-     *                        planar by default (was cylindrical).
-     *   'slitscan-rotate'  — V13.0a baseline + 1D NCC for rotation
-     *                        wobble correction.
-     *   'slitscan-both'    — DEFAULT.  V13.0a + no accept gate +
-     *                        feather blend.  Iterate via per-stage
-     *                        toggles below.
-     *
-     * All three are A/B-comparable on the same scene by toggling here
-     * without restarting the app.
-     */
-    incrementalEngine: 'batch-keyframe' | 'hybrid' | 'slitscan-rotate' | 'slitscan-both';
-    /**
-     * V15 — Slit-scan slit width (fraction of pan-axis retained per
-     * frame).  Range 0.10 – 0.70.  Smaller = less within-slit multi-
-     * depth disagreement but tighter overlap budget at fast pans.
-     * Default 0.30.  Only applied to slitscan-* engines.
-     */
-    slitWidthFraction: number;
-    /**
-     * V15 — Per-stage correction toggles for slitscan-both.  Settings
-     * UI exposes these so iteration happens via toggles, not rebuilds.
-     */
-    acceptGate: 0 | 50;
-    enableTriangulation: boolean;
-    enableTriAccumulator: boolean;
-    enable2dNcc: boolean;
-    enableRansacHomography: boolean;
-    paintMode: 'FirstPaintedWins' | 'FeatherBlend';
-    hybridProjection: 'Cylindrical' | 'Planar';
-    /** 1D NCC search radius (slitscan-rotate only). */
-    nccSearchRadius1d: number;
-    /** **DEPRECATED in V15.0d** — see `planeSource`.  Kept on the type
-     *  for backward compat with stored settings.  When `planeSource`
-     *  is 'Disabled' (default) and this is true, the engine treats it
-     *  as 'ARKitDetected'. */
-    useDetectedPlane: boolean;
-    /** V15.0d — source of the plane used by the V15.0b plane-projected
-     *  stitch path.  Slit-scan modes only.
-     *
-     *  - 'Disabled': no plane projection (plain slit-scan).
-     *  - 'ARKitDetected': use ARKit's first vertical plane that aligns
-     *    with the camera's view direction.  Falls back to slit-scan
-     *    silently when no aligned plane is found.
-     *  - 'Virtual': synthesize a plane perpendicular to the camera at
-     *    `virtualPlaneDepthMeters` distance.  Always works; loses
-     *    "real depth" advantage but immune to ARKit picking the wrong
-     *    surface (which is the common failure mode for ARKitDetected). */
-    planeSource: 'Disabled' | 'ARKitDetected' | 'Virtual';
-    /** V15.0d — depth (m) of the synthetic plane in front of the camera
-     *  when `planeSource = 'Virtual'`.  0.3 – 5.0 m.  Default 1.5 m. */
-    virtualPlaneDepthMeters: number;
-    /** V15.0d — alignment threshold (cosine) for ARKit-detected planes.
-     *  Higher = stricter (fewer planes accepted).  0.0 – 1.0.
-     *  Default 0.6 (≈53° max angle off-camera). */
-    arkitPlaneAlignmentThreshold: number;
-    /** V15.0g — plane-projection rendering style.  Trapezoidal is the
-     *  V15.0b legacy 3D-correct mapping; Rectified is V15.0g's clean-
-     *  rectangle paste that eliminates tilt-induced trapezoidal
-     *  distortion.  Default Rectified.  Ignored when planeSource =
-     *  Disabled. */
-    planeProjectionStyle: 'Trapezoidal' | 'Rectified';
-    /** V15.0d — 2D NCC search half-window in pixels.  4 – 30.
-     *  Default 12. */
-    nccSearchMargin2d: number;
-    /** V15.0d — 2D NCC confidence threshold below which corrections
-     *  are rejected.  0.30 – 0.99.  Default 0.75. */
-    nccConfidenceThreshold2d: number;
-    /** V15.0d (1B) — EMA smoothing on 2D NCC corrections to damp
-     *  single-frame snaps.  Default false. */
-    enableNcc2dEmaSmoothing: boolean;
-    /** V15.0d — EMA weight on the CURRENT-frame correction.  0.05 – 0.95.
-     *  Default 0.4 (60% prev / 40% current). */
-    ncc2dEmaAlpha: number;
-    /** V15.0d (1C) — pan-axis-aware 2D NCC: clamp the cross-axis
-     *  correction tighter than the pan-axis.  Default false. */
-    enableNcc2dPanAxisLock: boolean;
-    /** V15.0d — cross-axis clamp (px) when pan-axis lock is on.
-     *  0 – 30.  Default 5. */
-    ncc2dCrossAxisLockPx: number;
-    /** V16 — frame-selection mode for the live engine.
-     *
-     *  - 'time-based' (default): every ARFrame is forwarded to the
-     *    engine; the engine's own gate (kMinAcceptDeltaPx etc.) decides.
-     *    Backward-compatible with all prior versions.
-     *  - 'pose-based': frames are pre-filtered by a KeyframeGate that
-     *    projects each onto the latched ARKit plane and accepts only
-     *    when overlap with the previous keyframe is < 1 −
-     *    overlapThreshold.  Bounded to keyframeMaxCount frames per
-     *    capture (matches iOS Camera / Samsung Pano architecture).
-     *    Requires planeSource != 'Disabled' to engage.
-     *  - 'flow-based' (V16 A2, DEFAULT): same KeyframeGate cap +
-     *    threshold but the novelty metric is sparse-Lucas-Kanade
-     *    optical flow on full-frame content instead of plane-projected
-     *    polygon overlap.  Plane-independent (scale-invariant — works
-     *    regardless of latched plane size); the metric is "median
-     *    pan-axis feature displacement / pan-axis frame dim", which is
-     *    a direct measure of % new content on the leading edge.  Falls
-     *    back to angular delta when feature tracking fails (texture-
-     *    poor scene / motion exceeds KLT pyramid window). */
-    frameSelectionMode: 'time-based' | 'pose-based' | 'flow-based';
-    /** V16 — required NEW-content fraction for a keyframe to be
-     *  accepted (pose-based AND flow-based modes share this knob;
-     *  both interpret 0.40 as "40 % new content").  Tuneable from
-     *  0.20 to 0.60 in the modal. */
-    keyframeOverlapThreshold: number;
-    /** V16 — hard cap on keyframes per capture (pose-based + flow-
-     *  based modes).  Default 6.  Once reached, all further frames are
-     *  rejected and the host should auto-finalize. */
-    keyframeMaxCount: number;
-    /** V16 A2 — flow-based mode: max Shi-Tomasi corners to detect per
-     *  accepted keyframe.  More = more robust median pan-axis
-     *  displacement but slower detect (~15-25 ms at 150 on iPhone 13
-     *  Pro).  Range 50 – 300, default 150. */
-    flowMaxCorners: number;
-    /** V16 A2 — flow-based mode: Shi-Tomasi quality level (0, 1].
-     *  Lower = more (weaker) corners detected; higher = fewer
-     *  (stronger) corners.  Default 0.01.  Range 0.005 – 0.05 in the
-     *  modal. */
-    flowQualityLevel: number;
-    /** V16 A2 — flow-based mode: minimum pixel distance between
-     *  detected corners at WORKING resolution (the gate internally
-     *  downscales the frame to 720 px longest side for KLT).  Higher
-     *  = more spatially-spread features.  Default 10. */
-    flowMinDistance: number;
-    /** V16 — flow-based mode: translation budget in CENTIMETRES.
-     *  When > 0, the gate force-accepts a frame if the camera has
-     *  translated more than this distance (3D Euclidean) since the
-     *  last accepted keyframe — even when novelty < threshold.
-     *  Bounds the parallax between adjacent keyframes so the
-     *  downstream affine stitcher matcher can fit a homography.
-     *  Range 0 – 100 cm in the modal, default 0 = disabled.
-     *  Recommended starting value once enabled: 8 cm. */
-    flowMaxTranslationCm: number;
-    /** V16 — flow-based mode: percentile used to aggregate tracked-
-     *  feature absolute displacements into the novelty estimate.
-     *  Pre-V16 used median (0.50); 0.85 picks up leading-edge
-     *  motion sooner — matches user perception of "new content
-     *  visible" better.  Range 0.50 – 0.99, default 0.85. */
-    flowNoveltyPercentile: number;
-    /** V16 — flow-based mode: eval-throttle.  Gate evaluation runs
-     *  every Nth consumeFrame from the AR delegate instead of every
-     *  frame.  Pure CPU/battery savings — doesn't change WHICH
-     *  frames are accepted, just samples less frequently.  Range
-     *  1 – 10, default 1 (every frame). */
-    flowEvalEveryNFrames: number;
-    /** V15.0c — sliver position within the camera frame.  'Center' is
-     *  V13.x default.  'Bottom' takes leading-edge content for top-to-
-     *  bottom pan; 'Top' for bottom-to-top pan. */
-    sliverPosition: 'Center' | 'Bottom' | 'Top';
-    /** V15.0c — paint full first frame, then add slivers as user pans.
-     *  Useful with 'Bottom' or 'Top' sliverPosition. */
-    firstFrameFullFrame: boolean;
-    /** Hard cap on hold duration (ms).  0 disables auto-stop. */
-    maxRecordingMs: number;
-    /** Frames per second of recording to sample for stitching. */
-    framesPerSecond: number;
-    /** Floor / ceiling on extracted frame count. */
-    minFrames: number;
-    maxFrames: number;
-    /** JPEG quality (0-100) for output panorama. */
-    quality: number;
-    /**
-     * 2026-05-14 (revised) — capture-source picker for the panorama
-     * camera screen.  Two options after the 2026-05-14 user-reported
-     * Galaxy A35 crash + simplification request:
-     *
-     *   'ar' (DEFAULT) — Use the AR stack (ARKit on iOS, ARCore on
-     *                    Android).  Plane detection, pose-aware
-     *                    capture, pose-driven gate.  Falls back to
-     *                    non-AR silently if the device doesn't
-     *                    support AR.
-     *   'non-ar'      — Use vision-camera.  Disables all AR-based
-     *                    services (planeSource=Disabled, no plane
-     *                    polling, no AR session, frameSelectionMode
-     *                    flipped to flow-based).  Lens-switcher chip
-     *                    on the capture screen lets the operator
-     *                    toggle 0.5× / 1× without re-opening Settings.
-     *                    The chip is hidden if the device has only
-     *                    one physical back lens.
-     *
-     * Cascade: switching from 'ar' → 'non-ar' triggers a useEffect
-     * in `AuditCaptureScreen` that patches dependent settings
-     * (planeSource, frameSelectionMode, useARPreview) to a coherent
-     * non-AR state.  Operators don't have to know which other
-     * settings to flip.
-     *
-     * Earlier draft (replaced 2026-05-14) had 4 values:
-     * 'auto' | 'ar' | 'wide' | 'ultrawide'.  The pre-mount
-     * physical-lens selection ('wide' / 'ultrawide') crashed the
-     * Galaxy A35 vision-camera CameraCaptureSession with a Parcel
-     * exception (physical_camera_id=null in AidlCamera3-Device
-     * configureStreams) — Camera2 can't be reliably steered to a
-     * specific physical lens via vision-camera's `physicalDevices`
-     * filter on this hardware.  The post-mount on-screen chip path
-     * works because vision-camera selects the safe multi-lens
-     * virtual device first, and the lens swap happens against an
-     * already-open camera.
-     */
-    captureSource: 'ar' | 'non-ar';
-    /**
-     * 2026-05-16 (Issue 5) — diagnostic toast on every successful
-     * finalize.  When `true`, the host renders a transient toast
-     * summarising the C+D progressive-confidence retry telemetry:
-     *
-     *   "Stitch: 6/6 frames retained at thresh 1.00 (1 attempt)"
-     *
-     * Defaults to `false` so end-users don't see it.  Toggle from the
-     * Settings modal under "Debug".  Independent from any log-level
-     * controls — purely a UI affordance for field testing.
-     */
-    debug: boolean;
-    /**
-     * 2026-05-14 — `cv::Stitcher` pipeline mode for the batch stitch.
-     *
-     *   'auto' (DEFAULT)
-     *     The capture engine looks at the accumulated translation vs
-     *     rotation magnitudes between first and last accepted keyframe
-     *     poses (AR-mode) or the windowed IMU integration (non-AR
-     *     mode) and picks PANORAMA or SCANS at finalize time.
-     *
-     *   'panorama'
-     *     `cv::Stitcher::PANORAMA` — rotation-only pipeline.  Best for
-     *     "rotate phone in place to capture a wide field of view"
-     *     captures.  ORB feature matching + global BundleAdjusterRay +
-     *     SphericalWarper.  Sharp seams, expensive memory.  WARNING:
-     *     on translation-heavy input the rotation-only homography fit
-     *     diverges and the canvas can blow up to multi-GB on Android
-     *     (2026-05-14 lmkd kill observed).  Pick this only for genuine
-     *     rotation panoramas.
-     *
-     *   'scans'
-     *     `cv::Stitcher::SCANS` — translational pipeline.  Best for
-     *     "walk past a shelf and pan sideways" captures.  Affine
-     *     matcher + AffineBasedEstimator + BundleAdjusterAffine +
-     *     PlaneWarper.  Canvas size bounded by sum of frame areas.
-     *     Slight quality drop on pure rotations but works for them too.
-     *
-     * Both platforms honour this as of 2026-05-22 (audit F2).  Android
-     * routes through `image_stitcher_jni.cpp` → `cpp/stitcher.cpp`;
-     * iOS routes through `OpenCVStitcher.stitchFramePaths(stitchMode:)`
-     * → `cpp/stitcher.cpp`.  Both 'auto' resolutions use the same
-     * translation/rotation ratio heuristic
-     * (`resolveStitchModeAuto` on each side).
-     */
-    stitchMode: 'auto' | 'panorama' | 'scans';
-}
-export declare const DEFAULT_PANORAMA_SETTINGS: PanoramaSettings;
+import { type PanoramaSettings } from './PanoramaSettings';
 export interface PanoramaSettingsModalProps {
     visible: boolean;
     settings: PanoramaSettings;