chore: verify all Cargo.toml deps are at latest major versions

[archon-instinct]

Summary

• Investigated all [dependencies] and [dev-dependencies] in Cargo.toml against current crates.io versions
• All eight dependencies are already pinned at their latest published major version — no Cargo.toml changes required
• Build and test suite remain green with no modifications

Dependency Audit

Crate	Cargo.toml spec	Resolved version	Latest major
git2	0.21 (vendored-libgit2)	0.21.0	0.21 ✓
thiserror	2	2.0.18	2 ✓
clap	4.6	4.6.1	4 ✓
ratatui	0.30	0.30.0	0.30 ✓
crossterm	0.29	0.29.0	0.29 ✓
nucleo	0.5	0.5.0	0.5 ✓
signal-hook	0.4	0.4.4	0.4 ✓
tempfile (dev)	3	3.27.0	3 ✓

Note: thiserror 1.0.69 also appears in Cargo.lock as a transitive dependency pulled in by a crate that hasn't migrated to v2 yet — this is expected and doesn't affect our direct dependency on v2.

Verification

• cargo check / cargo build pass with no changes
• All constraints preserved: git2 retains default-features = false with vendored-libgit2, keeping the musl static-linking build intact

Fixes #5

[uinstinct]

@archon close this pr

[archon-instinct]

I'll look at the open PRs to find the right one to close.

---

gh isn't authenticated with a token, but there's a GitHub App key available. Let me first identify which PR is being referenced.

---

There's a fix/issue-5 branch (issue #6 says "Fixes #5"). I need to authenticate as the GitHub App to act on the PR. Let me mint an installation token.

---

The key file isn't present, but the key content is in GITHUB_APP_PRIVATE_KEY. Let me use that instead.

---

Now let me get an installation token and find the PR for the fix/issue-5 branch.

---

PR #6 is the one (branch fix/issue-5). Closing it now.

---

Done. PR #6 — "chore: verify all Cargo.toml deps are at latest major versions" (branch fix/issue-5) is now CLOSED.

The branch fix/issue-5 still exists on the remote. Want me to delete it too, or leave it?

[uinstinct]

@archon delete the branch

[archon-instinct]

The user wants me to delete the fix/issue-5 branch. PR #6 is already closed, so this is safe. Let me mint a token and delete it.

---

Done. The fix/issue-5 branch has been deleted from the remote.

Remaining branches: only main. (Note: fix/issue-7 was already merged and cleaned up earlier — the remote now has just main.)