registry-render command reference
Governed, byte-stable PDF documents from registry data, rendered with Typst.
Contract status
Section titled “Contract status”This page is generated from the public Clap command tree for Registry Stack source version 0.34.0 and catalog SHA-256 c9eb944fbb64b3beca0250dc0dee945ea12d5c5f92ffeab2f7c21d9eeb888c6c. Hidden implementation commands are omitted.
registry-render <COMMAND>Commands
Section titled “Commands”| Command | Description |
|---|---|
init | Scaffold a working starter bundle |
check | Verify a bundle (structure, hashes, label coverage), optionally sealing it only after verification passes |
validate | Dry-run request data against a document’s schema, without rendering |
seal | Write per-file hashes into the manifest, sealing the bundle |
compile | Render one document offline |
serve | Serve the HTTP rendering API (see the runtime YAML) |
healthcheck | Probe a running server’s /health |
audit-verify | Verify a sealed audit chain end to end |
Options
Section titled “Options”| Option | Always required | Default | Values | Environment | Description |
|---|---|---|---|---|---|
-h, --help | No | n/a | n/a | n/a | Print help |
-V, --version | No | n/a | n/a | n/a | Print version |
Generation contract
Section titled “Generation contract”Run npm run generate from docs/site after changing a public command, argument, option, default, environment binding, or help description.