[gauntface]

Bump detail-cli from 0.2.12 to 0.2.13 in Cargo.toml and Cargo.lock. Merging triggers the release workflow, which tags v0.2.13 and publishes the release.

This release ships #339 and #344. With #344, the vendored openapi.json includes category on Vuln, so detail vulns list --format json and detail vulns show --format json now include each finding's category. In v0.2.12 the field is dropped because the generated Vuln type does not have it.

Validation:

• cargo fmt --check, cargo check, cargo clippy -- -D warnings, cargo test (371 unit tests) and cargo xtask check pass locally.
• Integration tests were skipped locally (no DETAIL_API_KEY); they passed in CI on 7d2d752.
• Manual check with the 0.2.13 build: detail vulns list usedetail/detail --format json returns a non-null category on all 50 findings on the first page, and detail vulns show <id> --format json returns "category": "vulnerable-dependency".

🤖 Generated with Claude Code

[aviator-app]

Current Aviator status

Aviator will automatically update this comment as the status of the PR changes.
Comment /aviator refresh to force Aviator to re-examine your PR (or learn about other /aviator commands).

This pull request is currently open (not queued).

How to merge

To merge this PR, comment /aviator merge or add the mergequeue label.

---

See the real-time status of this PR on the Aviator webapp.

Use the Aviator Chrome Extension to see the status of your PR within GitHub.

[cubic-dev-ai]

No issues found across 2 files

<sub>Tip: Get a Slack DM when cubic finishes reviewing your PRs. Connect Slack

View guided diff | Turn on auto-fix | Re-trigger cubic</sub>