Fix CI

Fix CI

1. Read the check state with gh pr checks, then pull the failing job logs with gh run view <run-id> --log-failed. Logs fetched through gh are reproducible; browser-only inspection is not. Pending checks can usually wait unless the failure is already clear.

2. Reproduce locally. CI runs almost everything through Nix, so the failing step maps onto a just recipe:

   CI job / step	Local
   preflight, or Run nix flake check	just check
   Run Rust tests (nix build .#ccusage-tests)	just rust::test
   JS test	just test-node
   Babashka performance harness test	apps/ccusage/scripts/compare-pr-performance_test.clj

   Start with the narrowest command that reproduces the failure — a single cargo test filter — before the recipe above.

3. Fix the smallest cause that explains the failed check, using the skill for the area being changed: testing, development, docs, or the nearest package AGENTS.md. When the failure was generated output or formatting, commit the regenerated result the check requires rather than hand-editing it.

4. Commit with the commit skill; a manifest change and its lockfile update belong in the same commit, and unrelated cleanups belong in separate ones. Let the git hooks run.

5. Push, then use create-pr to comment or request another review pass when appropriate.