Tighten licenses --help shape and unify the unknown-crate error wording

Three small UX fixes surfaced by manual exercise of the subcommand.

* `gix licenses -h` was rendering the entire `--verbose` no-op
  documentation inline because the doc-comment was a single paragraph.
  clap-derive treats the first paragraph as the short-help text and
  any subsequent paragraphs as the long-help-only details. Split the
  `--verbose` doc-comment so `-h` shows just "In the default summary
  view, also list workspace members whose license and authorship
  match the root `gitoxide` package's" and the no-op caveat block
  appears only under `--help`. Same shape applied to the `crate_name`
  positional argument's doc-comment so its `-h` line is the
  one-sentence summary, not the full "May be a third-party
  dependency, a workspace member with separate attribution, or a
  workspace member whose license and authorship match …" detail.

* The unknown-crate error wording diverged between the human and
  JSON output paths — the human path used `{name:?}`-style
  `"name"` quoting from `render::render_crate`, while the JSON
  path used backtick quoting from `emit_single_crate_json_against`'s
  `anyhow::bail!`. A user flipping `--format` between the two saw
  inconsistent inner phrasing for the same condition. Unify on
  backticks (matching the rest of the subcommand's error wording).
  Add a regression test (`unknown_crate_error_uses_backtick_form_in_both_paths`)
  that checks both paths against the same backticked-name substring,
  so a future drift between them surfaces here.

Test counts after this commit:
* `cargo test --features max-pure --test licenses_cli` — 27 (was 26).
* Other counts unchanged.

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: EliahKagan

gitoxide-core/src/licenses/render.rs

@@ -384,9 +384,13 @@ pub fn render_crate(w: &mut (impl Write + ?Sized), manifest: &Manifest, name: &s
             if manifest.is_covered_by_root_license(name) {
                 return write_root_license_attribution(w, name);
             }
+            // Match the JSON path's wording (`emit_single_crate_json_against`
+            // uses `anyhow::bail!("no dependency named `{name}` in the
+            // manifest")`) so a user who flips `--format` between human and
+            // JSON sees the same inner error message.
             Err(io::Error::new(
                 io::ErrorKind::NotFound,
-                format!("no dependency named {name:?} in the manifest"),
+                format!("no dependency named `{name}` in the manifest"),
             ))
         }
         1 => write_crate(w, hits[0]),

src/licenses/cli.rs

@@ -25,6 +25,7 @@ use super::embedded;
 )]
 pub struct Command {
     /// The name of a single crate whose full attribution should be printed.
+    ///
     /// May be a third-party dependency, a workspace member with separate
     /// attribution, or a workspace member whose license and authorship
     /// match the root `gitoxide` package's (in which case the root's
@@ -49,12 +50,13 @@ pub struct Command {
     #[clap(long, conflicts_with = "crate_name")]
     pub all: bool,
     /// In the default summary view, also list workspace members whose
-    /// license and authorship match the root `gitoxide` package's. Has no
-    /// effect when `--all` is set (the full attribution always includes
-    /// that listing), when a crate name argument is given, or in `--format
-    /// json` mode (the JSON manifest already carries
-    /// `workspace_members_same_attribution` directly, with no
-    /// summary/full distinction).
+    /// license and authorship match the root `gitoxide` package's.
+    ///
+    /// Has no effect when `--all` is set (the full attribution always
+    /// includes that listing), when a crate name argument is given, or in
+    /// `--format json` mode (the JSON manifest already carries
+    /// `workspace_members_same_attribution` directly, with no summary/full
+    /// distinction).
     #[clap(long, short = 'v')]
     pub verbose: bool,
     /// Override the output format for this subcommand specifically.

tests/licenses_cli.rs

@@ -377,6 +377,29 @@ fn unknown_crate_name_in_json_path_also_exits_nonzero() {
     );
 }
 
+/// The human and JSON output paths share the same inner phrasing for the
+/// "unknown crate name" error — both reference the missing crate with
+/// backtick quoting. The wording previously diverged (the human path used
+/// `{name:?}`-style `"name"` quoting; the JSON path used backticks); a
+/// regression that re-introduced that drift would surface here.
+#[test]
+fn unknown_crate_error_uses_backtick_form_in_both_paths() {
+    let bogus = "test-no-such-crate-xyzzy";
+    let human = run_licenses_raw(env!("CARGO_BIN_EXE_gix"), &[bogus]);
+    let json = run_licenses_raw(env!("CARGO_BIN_EXE_gix"), &["--format", "json", bogus]);
+    let human_stderr = String::from_utf8_lossy(&human.stderr);
+    let json_stderr = String::from_utf8_lossy(&json.stderr);
+    let backticked = format!("`{bogus}`");
+    assert!(
+        human_stderr.contains(&backticked),
+        "human-mode error should reference the crate with backticks (`{bogus}`):\n{human_stderr}"
+    );
+    assert!(
+        json_stderr.contains(&backticked),
+        "json-mode error should reference the crate with backticks (`{bogus}`):\n{json_stderr}"
+    );
+}
+
 // ---------------------------------------------------------------------------
 // JSON output end-to-end — the unit tests in `src/licenses/cli.rs` cover
 // the JSON shape against synthetic manifests, but never against the real