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.38.0 and catalog SHA-256 cd13c658f65af295f9df3c6db86dc045ac06e9e040afc1f5f5b27c3184ab653d. Hidden implementation commands are omitted.
registry-render <COMMAND>Commands
Section titled “Commands”| Command | Description |
|---|---|
init | Scaffold a working starter bundle |
check | Verify source or package structure, labels, fonts, and schemas |
validate | Dry-run request data against a document’s schema, without rendering |
package | Build a new deployment package with the shared checksum envelope |
compile | Render one document offline |
serve | Serve the HTTP rendering API (see the runtime YAML) |
healthcheck | Probe a running server’s /health |
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.