The PyPI name this repo would publish under belongs to Martijn Faassen's Sprout

[ChelseaKR]

What is wrong

pyproject.toml declares name = "sprout". That name is already taken on PyPI by an unrelated project:

$ curl -s https://pypi.org/pypi/sprout/json | jq '.info.version, .info.home_page, .info.author'
"1.1.1"
"http://infrae.com/download/Sprout"
"Martijn Faassen"

So a first publish under sprout will be rejected — and any automated check that asks "is this on PyPI?" by name gets back yes, at 1.1.1, describing a package that has nothing to do with this repository.

Also true right now

• CITATION.cff says 0.1.0-dev; pyproject.toml says 0.1.0. Those are not the same version.
• .github/workflows/release.yml exists on main and has never run (total_count: 0).
• No tag, no GitHub release, nothing on PyPI.

None of that is wrong on its own for a project that has not shipped yet. The name collision is the part that has to be settled before any of it can be, because it decides what the artifact would even be called.

What would help

Pick a distinguishing distribution name before the first publish — this portfolio already did exactly that for cairn-assistant, gauntlet-evals, nearmiss-safety, plumbline-eval, chalkline-ctdl and encore-plex, each of which had the same collision risk on its bare name. The import package name need not change with it.

Choosing a name is a product call, so nothing has been renamed, tagged or published here.

Found by a release-reality checker run across the portfolio on 2026-09-06 (conditions INDEX_NAME_TAKEN, VERSION_SOURCES_DISAGREE, RELEASE_MACHINERY_NEVER_RAN).

Prepared with AI assistance; reviewed before submission.

[ChelseaKR]

Status on dd084f0, and what is left. Checked each of the three reported
conditions against origin/main rather than re-reporting them.

INDEX_NAME_TAKEN — addressed, pending your word. #167 renamed the
distribution to sprout-plantcare, and pyproject.toml says in its own comment
that this is "a placeholder pending confirmation, not a claim already made"
(checked against pypi.org on 2026-09-07, HTTP 404). The import package, the
sprout command and src/sprout/ are unchanged. The comment also names the two
other places that must move with the name: metadata.version(...) in
src/sprout/__init__.py, and the [[package]] entry in uv.lock.

VERSION_SOURCES_DISAGREE — not a real disagreement. CITATION.cff carries
0.1.0-dev and pyproject.toml carries 0.1.0, and that is deliberate and
mechanically enforced. tests/test_release_versions.py (#152) requires the
-dev marker and the absence of date-released exactly while no tag exists,
and requires both the other way once one does; the base of the cited version
must equal the manifest's, which it does. Nothing to change.

RELEASE_MACHINERY_NEVER_RAN — still true, and blocked on two things that are
yours. Both are recorded in the drain's OWNER-DECISIONS.md:

1. Confirm or replace sprout-plantcare. A PyPI upload cannot be undone or
   renamed.
2. Register the Trusted Publishing pending publisher for that name (owner
   ChelseaKR, repository sprout, workflow release.yml, environment
   pypi). Without it the upload is refused with invalid-publisher — the same
   failure ChelseaKR/gauntlet's first release hit — and because
   publish-release declares needs: publish-pypi, a refused upload means no
   GitHub Release either.

One thing found while checking, which is worth knowing before any tag is
pushed here. release.yml's publish job declares environment: pypi, which
reads as an approval gate. That environment does not exist in this
repository: gh api repos/ChelseaKR/sprout/environments lists only
github-pages. GitHub creates a named environment implicitly on first use, with
no protection rules, so there is nothing to approve — and this workflow triggers
on push: tags, meaning the tag push is itself the publish. Adding a
required reviewer on a pypi environment, or deciding deliberately that the
signed tag is the only gate the way ctdl-validate and tods-validate do, is a
prerequisite rather than a detail.

No tag was cut and nothing was renamed here.

Prepared with AI assistance; reviewed before submission.