[kipyin]

Summary

test + fmt + clippy
  Format
  Test
  Clippy
  Smoke --help and --version
    GITEE_CONFIG_DIR = empty temp dir
    unset GITEE_TOKEN
    cargo run --quiet --locked -- --help
    cargo run --quiet --locked -- --version
    stdout contains the Cargo.toml version

The existing CI job runs both commands after test and clippy so the debug build is reused. There is one bin target (gitee), so the step does not pass --bin. --help and --version exit in clap before any API work. Config is an empty GITEE_CONFIG_DIR and GITEE_TOKEN is unset, so startup does not read the runner's config. HOME stays as the runner set it: rustup looks up the toolchain in $HOME/.rustup.

No CHANGELOG entry: the file has no Unreleased section.

Closes #6

Evidence

• Before: CI ended at clippy. A clap setup panic or a bin target that fails to start could still pass unit tests.
  After: locally, cargo run --quiet --locked -- --help and --version both exit 0. --version prints gitee 0.2.3, which matches version in Cargo.toml. The same binary exits 0 for both flags inside a network namespace (15s timeout). Overriding HOME without RUSTUP_HOME reproduces the first CI failure (rustup could not choose a version of cargo); the step no longer does that.

Merge Danger

Door: two-way

Deleting the new step restores the previous workflow.

Blast Radius: CI

The job gains two cargo run invocations of the binary already built by test and clippy. A smoke failure fails that job. No CLI or dependency changes.