urma-mcp 0.1.0-rc.1

package/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/README.md

@@ -0,0 +1,389 @@
+# Urma
+
+<div align="center">
+  <img src="assets/urma-banner.png" alt="Urma" width="100%" />
+  <br /><br />
+  <strong>Retrieve video captions and frames through MCP.</strong>
+  <br />
+  A stdio MCP server for bounded caption and visual evidence.
+  <br /><br />
+  <a href="#install-and-connect-a-host">Install</a>
+  ·
+  <a href="#tools">Tools</a>
+  ·
+  <a href="#configuration">Configuration</a>
+  ·
+  <a href="#documentation">Documentation</a>
+  <br /><br />
+  <sub><code>urma-mcp</code> · MCP stdio · Node.js 24 LTS</sub>
+</div>
+
+<br />
+
+Urma retrieves captions and sampled frames from videos with a known end time.
+Each result identifies its source snapshot and requested timestamps or range.
+The MCP host chooses what to retrieve and interprets the results.
+
+Urma runs locally and stores its cache on your filesystem. Remote videos still
+require network access. The host receives the requested evidence and controls
+how it is processed or sent to a model.
+
+Urma exposes five tools:
+
+| Tool | Returns |
+| --- | --- |
+| `inspect_video` | A source snapshot and a new investigation reference. |
+| `search_transcript` | Literal matches in one selected caption track. |
+| `read_transcript` | Timestamped caption segments in a bounded interval. |
+| `get_overview` | A visual overview with up to 12 sampled cells. |
+| `get_frames` | Exact JPEG points, ordered sparse points, or a fixed-cadence schedule. |
+
+The server uses MCP stdio. A host starts one Urma process for a session and
+owns its lifecycle. Urma does not run a daemon or expose an HTTP API.
+
+## Install and connect a host
+
+### Requirements
+
+- Native Node.js 24 LTS (`>=24 <25`).
+- A user-owned local filesystem for Urma's data root.
+- One of these runtime targets: Windows x64 or arm64, macOS x64 or arm64, or
+  Linux x64 or arm64 with glibc.
+
+Urma installs the pinned FFmpeg, ffprobe, and yt-dlp artifacts it needs. Do
+not install those tools separately for the packaged runtime. Urma does not
+install or manage Node.js.
+
+### Install the runtime
+
+Run the npm bootstrap with Node.js 24:
+
+```sh
+npx -y urma-mcp@latest setup
+```
+
+Setup downloads and verifies the pinned native tools, checks that the installed
+runtime can serve MCP requests, and selects the new installation for future
+launches. Each installation is stored in a separate directory called a
+generation. If setup fails during an update, the previously active generation
+remains selected.
+
+The default data roots are:
+
+| Platform | Root |
+| --- | --- |
+| Windows | `%LOCALAPPDATA%\Urma` |
+| macOS | `~/Library/Application Support/Urma` |
+| Linux | `${XDG_DATA_HOME:-~/.local/share}/urma` |
+
+Use `--data-dir PATH` with `setup`, or set `URMA_DATA_DIR`, to select another
+user-owned local directory. Network and UNC paths are outside the supported
+installation boundary.
+
+### Register a generic JSON host
+
+If the host uses the usual `mcpServers` JSON shape, setup can add the `urma`
+entry and preserve the other entries in the file:
+
+```sh
+npx -y urma-mcp@latest setup --client generic --config "/absolute/path/to/mcp.json"
+```
+
+The configuration file path must be absolute. The resulting entry has this
+shape; use the absolute paths printed by setup:
+
+```json
+{
+  "mcpServers": {
+    "urma": {
+      "command": "/absolute/path/to/node",
+      "args": ["/absolute/path/to/Urma/launcher-v1.mjs"],
+      "env": {
+        "URMA_DATA_DIR": "/absolute/path/to/Urma"
+      }
+    }
+  }
+}
+```
+
+On Windows, use the path escaping required by JSON. The `command` and the
+launcher path must be absolute. The launcher selects the installed generation
+and starts the local Urma runtime; use the npm package only for setup and
+version checks.
+
+Host registration and runtime installation are reported separately. A healthy
+runtime can be left installed when the configuration file cannot be written.
+After registration, restart the host and check that it lists the five tools
+above.
+
+For a host with a different configuration format, create the equivalent
+stdio entry with the same absolute Node executable, launcher path, and
+`URMA_DATA_DIR` value.
+
+## Tools
+
+Call `inspect_video` first for a new source. It accepts an HTTP(S) URL, an
+allowed local path, or a previously returned `sourceRef`. It rejects sources
+that do not define one finite video timeline. The default `freshness: "reuse"`
+reuses a stored snapshot for a known remote URL or `sourceRef`. A local path
+is read again to check the video and sidecar content. Set `freshness: "refresh"`
+to resolve the source again. Every evidence request then uses the returned
+`investigationRef`.
+
+Use captions to locate likely time ranges, `get_overview` to locate visual
+moments, and `get_frames` to verify selected moments. These tools expose
+different observations:
+
+- Caption search and reads are limited to the selected source-provided track.
+- An overview is a sparse locator with up to 12 returned cells.
+- A frame burst is an ordered set of requested points.
+- A cadence request is a finite list of exact point requests. It reports each
+  page slot as `success`, `error`, or `unfinished`.
+
+A source cache can be reused across investigations, but evidence presentation
+is recorded per investigation.
+
+### Source and caption inputs
+
+Urma accepts:
+
+- A generic HTTP(S) video URL admitted by the remote source policy.
+- A supported single-video YouTube URL.
+- A local video path under a root listed in `URMA_LOCAL_ROOTS`.
+
+Local caption sidecars are optional. Urma checks the video basename with `.vtt`
+first and `.srt` second. Local paths remain disabled when
+`URMA_LOCAL_ROOTS` is empty.
+
+`search_transcript` accepts either one `query` or a `queries` array. Its
+default mode is `phrase`; `terms` requires every normalized term to occur in a
+cue. Search is literal and case-insensitive after NFKC normalization. A
+matching caption is a lead for visual verification, not visual proof.
+
+`read_transcript` requires a source-global half-open interval,
+`[startMs,endMs)`. It returns at most 200 segments or 16,000 caption
+characters per page. To continue, pass `nextCursor` as `cursor` with the same
+investigation, interval, and selected track.
+
+### Visual inputs
+
+`get_overview` accepts an optional source-global interval. It requests 12
+temporally distributed cells. The returned timestamps are the samples that
+were observed; they do not describe continuous coverage.
+
+`get_frames` accepts one of these requests:
+
+| Request | Contract |
+| --- | --- |
+| `points` | 1–12 unique timestamps, each before the source duration. |
+| `burst` | A half-open interval and 2–12 ordered samples. |
+| `cadence` | A half-open interval and a positive integer `cadenceMs`. |
+
+Times are nonnegative integer milliseconds from the start of the source.
+Intervals require `startMs < endMs` and must fit within its duration. An exact
+frame request asks for the first decodable frame at or after the target; it
+does not guarantee a frame with precisely that presentation timestamp.
+
+For `points` and `burst`, the default presentation is `individual`. Set
+`presentation: "panel"` to receive one derived JPEG panel plus links to the
+canonical frame artifacts. A panel contains at most 12 cells and preserves
+request order.
+
+Cadence requests are paged. The default page maximum is 12 targets and the
+default schedule maximum is 120 targets. Continue with the returned opaque
+`nextCursor`; do not construct a cursor yourself. A cadence schedule is
+discrete evidence and does not cover the time between its targets.
+
+### Example tool arguments
+
+For a local video, first add its parent directory to `URMA_LOCAL_ROOTS` in the
+host's Urma environment and restart the host. Call `inspect_video` with the
+absolute path to your file:
+
+```json
+{ "source": "/absolute/path/to/video.mp4" }
+```
+
+Use the returned `investigationRef` in subsequent calls. For example, these
+`get_frames` arguments request a panel at 1 and 5 seconds from a video longer
+than 5 seconds. Replace the example reference with the value from inspection:
+
+```json
+{
+  "investigationRef": "urma:investigation:0123456789abcdef0123456789abcdef",
+  "request": { "kind": "points", "timesMs": [1000, 5000] },
+  "presentation": "panel"
+}
+```
+
+To continue a cadence page, pass `investigationRef` and the returned
+`nextCursor` as `cursor`, without a new `request`.
+
+## Resources and errors
+
+Successful evidence results include investigation-scoped resource links. An
+artifact can be reopened through
+`urma://investigation/{investigationId}/artifact/{artifactHash}` only after
+that investigation has received it in a tool result. Reopening an artifact
+does not add temporal coverage.
+
+The state resource is
+`urma://investigation/{investigationId}/state`. It contains persisted
+acquisition, cache, and presentation state for that investigation.
+
+Top-level MCP failures return `isError: true` with a JSON text object containing
+`code`, `retryable`, and `detail`. A cadence page can instead return an error
+in an individual slot and continue with other targets.
+
+## Evidence rules
+
+For caption search, `partial: false` means all matches under the selected
+track's matching rules were returned. It says nothing about uncaptioned
+speech or visual events. Sampled frames describe only the returned points,
+and reopening cached artifacts adds no coverage.
+
+See [Evidence Model](docs/EVIDENCE_MODEL.md) for the full contract.
+
+## Limits
+
+Runtime defaults are:
+
+| Limit | Default |
+| --- | ---: |
+| Single caption search result limit | 5, maximum 20 |
+| Caption query length | 256 characters |
+| Batched caption queries | 20 queries, 20 merged hits, 16,000 returned characters |
+| Caption read page | 200 segments or 16,000 characters |
+| Overview request | 12 requested cells |
+| Explicit frame request | 12 points or burst samples |
+| Cadence page | 12 targets |
+| Cadence schedule | 120 targets |
+| Inline image response | 8 MiB |
+| Resource read | 32 MiB |
+| Targeted media acquisition | 64 MiB |
+| Navigation media acquisition | 256 MiB |
+| Reusable evidence media | 512 MiB |
+| Remote acquisition wall time | 180,000 ms |
+
+The environment variables below override the tunable limits. Values for byte
+limits are bytes; the remote wall limit is milliseconds. Each value must be a
+positive integer. `URMA_MAX_FRAME_SCHEDULE_PAGE_TARGETS` cannot exceed 12.
+
+| Variable | Overrides |
+| --- | --- |
+| `URMA_MAX_TARGETED_MEDIA_BYTES` | Targeted media limit. |
+| `URMA_MAX_NAVIGATION_COPY_BYTES` | Navigation media and timeline-validation limit. |
+| `URMA_MAX_REUSABLE_EVIDENCE_MEDIA_BYTES` | Reusable evidence media limit. |
+| `URMA_MAX_REMOTE_ACQUISITION_WALL_MS` | Remote acquisition wall-time limit. |
+| `URMA_MAX_FRAME_SCHEDULE_PAGE_TARGETS` | Cadence page limit. |
+| `URMA_MAX_FRAME_SCHEDULE_TARGETS` | Cadence schedule limit. |
+
+## Configuration
+
+| Variable | Purpose |
+| --- | --- |
+| `URMA_DATA_DIR` | Selects the persistent Urma data root. |
+| `URMA_LOCAL_ROOTS` | Platform-delimited list of roots allowed for local videos and sidecars. |
+| `URMA_ALLOW_UNC` | Allows UNC paths when set to `1` or `true`; the path must still be under an allowed root. |
+| `URMA_DEBUG` | Writes opt-in acquisition and subprocess diagnostics to stderr when set to `1` or `true`. |
+| `URMA_DEBUG_FILE` | Appends diagnostics to a JSONL file when `URMA_DEBUG` is enabled. |
+
+Set these variables in the host's Urma `env` entry, then restart the host.
+Separate local roots with `;` on Windows and `:` on macOS/Linux. Use absolute
+paths so root selection does not depend on the host's working directory.
+
+The packaged launcher uses the selected generation's absolute native-tool
+paths. It does not look up FFmpeg, ffprobe, or yt-dlp through `PATH`.
+
+## CLI and maintenance
+
+The npm entry point exposes setup and version checks:
+
+```sh
+npx -y urma-mcp@latest --version
+npx -y urma-mcp@latest setup
+```
+
+After setup, run the read-only doctor through the persistent launcher:
+
+```sh
+"/absolute/path/to/node" "/absolute/path/to/Urma/launcher-v1.mjs" doctor
+```
+
+In PowerShell, prefix the quoted executable path with `&`:
+
+```powershell
+& "C:\path\to\node.exe" "C:\path\to\Urma\launcher-v1.mjs" doctor
+```
+
+Doctor checks the selected runtime, Node version, SQLite/FTS5, native-tool
+versions, storage, blob access, local roots, and frame-schedule limits. It
+prints its report to stderr and exits with status 0 when no check fails
+(warnings are allowed), or 1 when a check fails.
+
+The launcher also provides local generation recovery:
+
+```sh
+"/absolute/path/to/node" "/absolute/path/to/Urma/launcher-v1.mjs" rollback
+"/absolute/path/to/node" "/absolute/path/to/Urma/launcher-v1.mjs" recover
+```
+
+`rollback` selects the retained previous generation after integrity and state
+compatibility checks. `recover` restores the selection recorded in
+`ACTIVE.backup.json`. Set `URMA_DATA_DIR` for a non-default data root.
+
+Normal MCP startup selects one generation for the process. It does not invoke
+npm, make a network request, check for updates, modify `PATH`, or download
+dependencies. A later setup affects new processes only.
+
+## Boundaries
+
+Urma v0.1 does not transcribe audio, recognize objects or actions, or call a
+model. It supports finite videos without authentication or DRM. See
+[Product scope](docs/PRODUCT_SCOPE.md) for supported sources and exclusions.
+
+## Security
+
+Local paths require explicit allowed roots. Remote HTTP(S) work uses a
+process-local Safe Proxy that validates destinations and DNS results before
+connecting. Installed native tools are receipt-bound and hash-checked before
+first use. Subprocesses use argument arrays, `shell: false`, an allowlisted
+environment, bounded output, deadlines, cancellation, and process-tree
+cleanup.
+
+These controls protect the local application boundary under the trusted
+Node/FFmpeg/ffprobe/yt-dlp runtime model. They are not an operating-system
+sandbox against a compromised trusted executable.
+
+See [Security](docs/SECURITY.md) for the full boundary and failure behavior.
+
+## Development
+
+Use Node.js 24 and the pnpm version declared in `package.json`. See the
+[development prerequisites](docs/CONTRIBUTING.md#development-setup) for native
+tools used by the tests. From the repository root:
+
+```sh
+pnpm install --frozen-lockfile
+pnpm check
+```
+
+Contributions are welcome. Follow the [contribution guide](docs/CONTRIBUTING.md)
+for code structure, documentation standards, and pull request expectations.
+
+## License
+
+Urma is licensed under [Apache License 2.0](LICENSE). Third-party dependencies
+and downloaded native tools retain their own licenses. The installed
+generation's `licenses/` directory records native component licenses and
+upstream references; preserve the accompanying upstream notices when
+redistributing those tools. Urma's license does not grant rights to videos or
+captions retrieved from other sources.
+
+## Documentation
+
+- [Product scope](docs/PRODUCT_SCOPE.md) — current v0.1 behavior and exclusions.
+- [Architecture](docs/ARCHITECTURE.md) — runtime layers, persistence, caching, and acquisition decisions.
+- [Evidence Model](docs/EVIDENCE_MODEL.md) — what each result means and what it cannot establish.
+- [Security](docs/SECURITY.md) — path, network, subprocess, installation, and cache controls.
+- [Contributing](docs/CONTRIBUTING.md) — local setup, validation commands, and change expectations.

package/dist/src/acquisition/frame-panel.d.ts

@@ -0,0 +1,22 @@
+import type { UrmaConfig } from "../config.js";
+import type { ResolvedSource } from "../sources/types.js";
+import { BlobStore } from "../store/blob-store.js";
+import type { StoredArtifact, UrmaStore } from "../store/store.js";
+import { type PanelDimensions } from "./panel.js";
+type ExactFrame = Readonly<{
+    atMs: number;
+    artifact: StoredArtifact;
+}>;
+type FramePanelResult = Readonly<{
+    artifact: StoredArtifact;
+    dimensions: PanelDimensions;
+    cacheHit: boolean;
+}>;
+export declare class FramePanelAcquirer {
+    readonly config: UrmaConfig;
+    readonly store: UrmaStore;
+    readonly blobs: BlobStore;
+    constructor(config: UrmaConfig, store: UrmaStore, blobs: BlobStore);
+    get(source: ResolvedSource, frames: readonly ExactFrame[], signal?: AbortSignal): Promise<FramePanelResult>;
+}
+export {};