> ## Documentation Index
> Fetch the complete documentation index at: https://reshot.dev/docs/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Treat a Journey, Run, Decision, Rendition, Publication, and Release Book as distinct lifecycle objects.
> Never describe imported or customer-attested material as independently verified evidence without a complete hosted custody chain.

# Supported Environments

> Native GA scope, capture paths, browser contexts, and explicit exclusions.

Reshot's native GA scope is responsive web applications and complete web
processes. Native mobile applications and documents may be imported as external
evidence but are not natively captured or claimed as evaluated.

## Capture paths

| Path             | Best for                                      | Provenance                                             |
| :--------------- | :-------------------------------------------- | :----------------------------------------------------- |
| Hosted discovery | Public HTTPS pages and processes              | Independent only after trusted worker custody verifies |
| Browser recorder | Authenticated and non-developer journeys      | Customer-attested                                      |
| CLI/CI runner    | Deterministic repository-controlled execution | Customer-attested                                      |

Hosted workers never receive authenticated customer sessions. Recorder and CLI
captures apply redaction before upload and remain attributable to the customer
capture environment.

## Web execution contexts

Context policy can vary browser engine, viewport, zoom, locale, text direction,
theme, reduced motion, and authenticated or data state. Use combinations that
represent real users and release risk rather than an unbounded cartesian matrix.

Customer-controlled runs should target a production-like build or preview
deployment. Hot-reload development servers and sleep-only readiness contracts
are unsuitable for reproducible evidence.

## Technical boundaries

Cross-origin iframe and closed shadow-root evidence is retained only where the
browser and capture boundary permit it. Network failure, worker failure, missing
credentials, and unavailable services are operational outcomes, not
accessibility failures. Unsupported or insufficient evidence remains
`cantTell` or `untested`.

See [Capture Paths](/docs/cli/getting-started/installation) and the
[Evaluation Methodology](/docs/platform/evaluation-methodology).