ragleap-agents v0.4.1 release notes

Patch release of ragleap-agents. Install: pip install ragleap-agents==0.4.1.

Changed

Project links in the package metadata (Homepage, Repository, Issues) now point at https://github.com/ragleap/ragleap-core, the repository's new home in the ragleap organization.
The OpenAI-compatible adapter's default User-Agent header now names the new address (ragleap-agents (+https://github.com/ragleap/ragleap-core)); it named the old owner before.
Nothing else changed. This release is the 0.4.0 tag plus those links and the version string. Work that is on the main branch but unreleased (the tainted argument of Agent.run and the sub-agent building blocks) is not in it and will come in the next minor release.

The differences from the 0.4.0 tag are five files: the version string, the README status line, the CHANGELOG, the project links in pyproject.toml and the DEFAULT_USER_AGENT constant. 151 tests pass on Python 3.10 with that content.
The published 0.4.1 wheel differs from the published 0.4.0 wheel only in ragleap_agents/__init__.py (the version), ragleap_agents/providers.py (the single DEFAULT_USER_AGENT line) and the .dist-info folder (compared with diff -rq on the unpacked wheels).
The published wheel and sdist digests match the publish log and PyPI (below).
The published wheel installed into a fresh virtual environment on Python 3.10, run from outside the repository: pip check clean, the version is 0.4.1, the default User-Agent shows the new address, and an empty run returns status="stopped" with stop_reason="no_task_or_tools".
The merge-back pull request (#863), which carries this release plus the current main branch, had no failing or pending checks when it was last looked at.

CI did not run on the tagged commit itself: the workflow runs for pushes to main and for pull requests into main, and this tag points at a commit on a release branch cut from the 0.4.0 tag.
The published wheel was not installed on Python 3.11 or 3.12 for this release.
The changed User-Agent string was not tried against a live provider. Only the address inside it changed; Groq's gateway rejected Python's default User-Agent in an earlier test, which is why the adapter sends its own.
Unchanged since 0.4.0: the prompt wording was not touched, so the real-model results of 0.3.0 stand and were not re-run. JSON mode on the model tested is still intermittent, and the taint rule has still never been triggered by a real model.

PyPI shows a "Change of provenance" banner on this release. Its detail lists the repository as the only difference: 0.4.0 was published from antonyrag/ragleap-core and 0.4.1 from ragleap/ragleap-core, the repository's new location. It was published by the repository's trusted-publishing workflow (run 39379150990, below).

Release branch commit 0a61e87 (tag ragleap-agents-v0.4.1), cut from the 0.4.0 tag plus the link changes from commit 9c6075b; merge-back pull request #863.
Publish: tag run 39379150990, trusted publishing with attestations; the log shows the upload, with no "skipping" line, so this was the first upload.
Digests (sha256), identical on PyPI and in the run log:
- ragleap_agents-0.4.1-py3-none-any.whl: 61717b1a52f5bfe2b0a74548931a030d87b688a07948f49975b54dee43834806
- ragleap_agents-0.4.1.tar.gz: df59328616e678478b916d731616e2f2d0eda856d6b72182ae263d96acc621d4