chore(workspace): refresh Cargo.lock for stella-time after the 0.9.417 sync

[macanderson]

What & why

main is red (#6495): Cargo.lock names stella-time at 0.9.416 while the workspace version is 0.9.417, so every --locked build fails. #6488 added the crate with a lock refreshed against the 0.9.416 sync, and the 0.9.417 sync (#6494) landed between that PR's last rebase and its merge; the merge check ran on the older merge commit. This is the #5939 shape.

The fix is the one-line lock refresh (cargo update -w): stella-time 0.9.416 → 0.9.417, nothing else.

Refs #6495 (the canary closes it once main is green again). Trivial change, closes no issue (no-issue).

The witness

• No witness needed (lockfile only) — cargo metadata --locked fails on main and passes here.

The gate

• cargo fmt --check (no Rust touched)
• CI — lockfile-sync and compile are the checks that were red
• CLA signed

Summary by Sourcery

Bug Fixes:

• Synchronize Cargo.lock with the workspace's stella-time 0.9.417 version so locked builds and metadata checks succeed.

[sourcery-ai]

Sorry @macanderson, you've used your own review budget of 250,000 diff characters for the last 7 days.

You can request another review in 2 days and 3 hours by commenting @sourcery-ai review. Upgrade to get a review now.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Refreshes the single Cargo.lock entry for stella-time from 0.9.416 to 0.9.417, restoring compatibility with --locked builds without changing other dependencies.

File-Level Changes

Change	Details	Files
Synchronize the lockfile package version with the workspace after the 0.9.417 release sync.	Update the locked stella-time version from 0.9.416 to 0.9.417. Leave all other dependency resolutions unchanged.	Cargo.lock

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[macanderson]

Already on main. #6497 landed the identical one-line change and is main's current head (544573f), where Cargo.lock now reads stella-time 0.9.417.

The file comparison on this PR still shows the change only because the branch was cut before #6497 merged, so the merge base predates it. Rebased onto current main the diff is empty.

Three sessions independently wrote this same line within half an hour. That is worth noting on #6495 rather than in three closed PRs: the canary tells everyone at once, and nothing tells them somebody is already on it. No action needed here.