caseworkctl provider pair command reference
Verify native context and reader authority, then optionally retain its provider export.
Contract status
Section titled “Contract status”This page is generated from the public Clap command tree for Registry Stack source version 0.44.0 and catalog SHA-256 1577fc2512d840ed27fdd70f4b3829f9f7796ab1a3a9a426c283904b3bf1a885. Hidden implementation commands are omitted.
caseworkctl provider pair [OPTIONS] --provider-id <PROVIDER_ID> --breg-package <DIRECTORY> --action-id <ACTION_ID> <PROJECT>Arguments
Section titled “Arguments”| Argument | Always required | Default | Values | Environment | Description |
|---|---|---|---|---|---|
<PROJECT> | Yes | n/a | n/a | n/a | Existing Casework project with the exact vendored schema and context pin |
Options
Section titled “Options”| Option | Always required | Default | Values | Environment | Description |
|---|---|---|---|---|---|
--provider-id <PROVIDER_ID> | Yes | n/a | n/a | n/a | Declared Casework context provider to pair |
--breg-package <DIRECTORY> | Yes | n/a | n/a | n/a | Sealed native Base Registry Engine (BReg) package containing the action’s context export |
--action-id <ACTION_ID> | Yes | n/a | n/a | n/a | Base Registry Engine (BReg) action that declares the required review context |
--bregctl-bin <BINARY> | No | bregctl | n/a | n/a | Matching bregctl executable used to verify the producer package |
--apply | No | n/a | n/a | n/a | Write the verified provider export and description reference after validation |
--format <FORMAT> | No | human | human, json | n/a | Write human diagnostics and reports, or one typed JSON report |
-h, --help | No | n/a | n/a | n/a | Print help |
Generation contract
Section titled “Generation contract”After changing a public command, argument, option, default, environment binding, or help description, run cargo run --locked -p registry-cli-docs -- --write, commit crates/registry-cli-docs/catalog.json, then run npm run generate from docs/site.