Crate jan_cli

Modules§

remote: HTTPS fetch with SHA256 verification and TTL-based local caching (wgex-inspired).

AliasesSpec: Shell aliases declared on a command node (jan alias emits them).
CommandNode
CommandTest: One Given/When/Then shell test on a command node.
ConfigSpec: Host configuration declared on a command node (jan config emit / link / apply / deps).
EnvSpec: Child-process environment declaration for a command node.
ExecSpec
GradlePackages: Gradle dependency declaration: pinned Maven coordinates or a locked project, with an optional minimum JDK (java: / jdk:).
HostComputer: Which computer id to use when filtering computer: lists on commands.
HostPlatform: Which platform string to use when filtering os: lists on commands.
IncludeLink: Retained include identity after load (not authored directly in YAML).
LocalInclude: Local include under the preferred jan directory (YAML subtree or script file).
MatchOutcome
Metadata
PackagesSpec: Package-manager deps for a command node (packages: in YAML).
PnpmPackages: pnpm dependency declaration: inline list or a project dir with a lockfile, with an optional minimum Node version (node:).
RemoteInclude
RootSpec
RunContext
SpecRootIdentity: Stable identity for where a YAML spec tree is rooted (directory of linked fragments + entry file).
UserConfig
UvPackages: uv dependency declaration: inline list, project dir, or requirements file, with an optional minimum Python version (python:).

ConfigLinkSource: One config.link source: relative path under the preferred dir, or inline file body.
ConfigShell: One shell fragment: a path under the preferred dir, or inline text.
GradleDeps
IncludeLinkKind: Whether an include link pointed at YAML (subtree graft) or a script file (exec leaf).
IncludeRef: Local path or remote HTTPS include target.
PnpmDeps
UvDeps

default_db_path
format_help
gherkin_test_name: True when name is given_…_when_…_then_… after normalizing spaces/hyphens.
load_spec
load_spec_from_str: Parse YAML from memory. Use include_base when the document uses include: (root or subtree).
load_user_config
match_commands
merge_specs_into: Deep-merge overlay.commands into base, letting included YAML fragments add or replace leaves and extend nested groups.
resolve_git_branch
resolve_preferred_spec: Resolve the preferred jan directory saved by jan use.
resolve_spec_dir_entry: Resolve a jan directory + entry file name into an absolute spec path and identity.
run_jan
run_matched
validate_spec: Validate every command in the tree (after merges or programmatic edits).