Log the version-provenance change under 0.0.10

[blooop]

The shipped 0.0.10 notes omit a change that is in the shipped code.

What happened

Release PR #86 was cut at 22:15Z. PR #85 (--version reports install provenance) merged at 22:31Z. #86 merged at 22:32Z at its original head, so it never picked up a changelog entry for #85 — the merge landed before an amendment to that branch registered.

Merge order means the code is fine: beaa5b2 (#85) precedes f27698a (#86) on main, and the released artifact has it. Verified against the installed build — ~/.pixi/envs/devpod/.../devlaunch/dl.py:1042 carries the change, and dl --version prints dl 0.0.10. Only the notes are wrong.

Change

Adds the missing ### Added entry to the ## [0.0.10] section. Documentation only.

No version bump, so etils-actions/pypi-auto-publish sees no version increase and will not republish; conda-publish.yml triggers on release: published and is likewise untouched.

The published GitHub release body for v0.0.10 was generated from the old file and has been corrected separately in place.

🤖 Generated with Claude Code

Summary by Sourcery

Documentation:

• Add a 0.0.10 changelog entry noting that dl --version now reports install provenance and that aid --version inherits this behavior.

[sourcery-ai]

Sorry @blooop, you have reached your weekly rate limit of 500000 diff characters.

Please try again later or upgrade to continue using Sourcery

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Documentation-only PR that backfills a missing changelog entry under v0.0.10 for the install-provenance-aware --version behavior, without touching any release automation or code artifacts.

File-Level Changes

Change	Details	Files
Add a detailed 'Added' entry under the 0.0.10 section documenting the new install-provenance-aware --version behavior.	Introduce a '### Added' subsection within the 0.0.10 changelog section. Describe how dl --version now reports whether it is a released build or an editable install and names the resolved tree when editable. Explain the provenance detection mechanism via PEP 610 direct_url.json through importlib.metadata, including its additive, non-failing fallback behavior. Note that aid --version inherits the same behavior.	CHANGELOG.md

---

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.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 89.28%. Comparing base (f27698a) to head (2fda695).
⚠️ Report is 2 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main      #89   +/-   ##
=======================================
  Coverage   89.28%   89.28%           
=======================================
  Files          12       12           
  Lines        1661     1661           
=======================================
  Hits         1483     1483           
  Misses        178      178           

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.