Expand description
release-kit: a canonical release workflow, carried whole by one binary.
The library exists so the crate’s own tests can link the modules; the
rk binary in main.rs is the product. embedded holds the payload
and payload_roots its one inventory, cli the argument surface,
commands the handlers, skills the user-scope skill install,
digest the one hash type, and error the one exit-code matrix.
Modules§
- applog
- The application log: one rotating file for the whole binary.
- atomic
- The temp-plus-rename writer every landing write goes through.
- cli
- Command-line surface: clap derive types only, one module per
subcommand’s arguments. No behavior lives here; each variant routes to
its handler in
commands. - commands
- One handler per subcommand. Handlers hold the behavior;
mainonly dispatches, andclionly declares the argument surface. - detect
- Forge, repository, and technology detection.
- diagnostic
- Diagnostics as data: the closed reason vocabulary and the typed error report.
- digest
- SHA-256 digests in their hex text form.
- embedded
- The compile-time payload: everything the binary serves or lands.
- error
- Crate-level error type and exit-code mapping.
- events
- The NDJSON event envelope for long-running commands.
- landing
- The target-side landing model: file kinds, parameter rendering, and the routing block.
- output
- The output boundary every handler emits through.
- payload_
roots - probes
- The environment probe catalog.
- registry
- The pinned-tool registry, parsed from the embedded
versions.toml. - setup
- The executable half of
method/02-setup.md. - skills
- The agent skills: the payload, the user-scope record, and the installer.