Registry stack documentation: machine-readable Markdown.
Index of all pages: https://docs.registrystack.org/v/0.38.0/llms.txt
Full corpus: https://docs.registrystack.org/v/0.38.0/llms-full.txt

# relay check command reference

> Generated syntax and options for relay check.

{/* Generated from Clap command definitions by scripts/generate-cli-reference.mjs. Run npm run generate. */}

Validate the sealed package and every deployment dependency without taking the listener socket.

## Contract status

This page is generated from the public Clap command tree for Registry Stack source version `0.38.0` and catalog SHA-256 `cd13c658f65af295f9df3c6db86dc045ac06e9e040afc1f5f5b27c3184ab653d`. Hidden implementation commands are omitted.

## Usage

```text
relay check [OPTIONS] --runtime-config <FILE>
```

## Options

| Option | Always required | Default | Values | Environment | Description |
| --- | --- | --- | --- | --- | --- |
| `--runtime-config <FILE>` | Yes | n/a | n/a | n/a | Absolute path of the runtime configuration that binds the sealed package to local resources |
| `--require-audit-under <ABSOLUTE_DIRECTORY>` | No | n/a | n/a | n/a | Also prove the configured audit file resolves inside this absolute directory, which the deployment declares persistent. The declared root is a storage boundary, not a second audit setting. Relay resolves the runtime audit path exactly as startup resolves it and refuses when the result is not at or below the root, which is what stops a container from mounting durable storage at the conventional prefix while writing audit somewhere ephemeral. A `stdout` audit destination has no path to prove and is refused. |
| `-h, --help` | No | n/a | n/a | n/a | Print help (see a summary with '-h') |

## Generation contract

Run `npm run generate` from `docs/site` after changing a public command, argument, option, default, environment binding, or help description.