Decision needed: the PyPI name `heed` is taken — pick a distribution name before first release

[thorwhalen]

Publishing is currently disabled in pyproject.toml ([tool.wads.ci.publish] enabled = false), which is correct for the design phase. The comment next to it used to say the PyPI name heed was reserved for this repo. It is not.

Evidence

https://pypi.org/pypi/heed/json today:

name    = heed
version = 0.1.0
summary = Python SDK for Heed - human-in-the-loop approval for AI agents
urls    = {Homepage: https://heed.run, Documentation: https://heed.run/docs}

That is an unrelated project. This repo has never published to PyPI, and it cannot publish under the name heed.

Two knock-on effects worth knowing about:

1. The repo-audit tool reports a false positive here. It sees "PyPI version (0.1.0) is AHEAD of pyproject (0.0.1)" and concludes the wads CI version-bump push-back failed. It did not - the two heeds are simply different projects. Nothing to fix in CI on that account.
2. A first release needs a decision. The import package can stay heed (that is a local namespace choice and costs nothing); only the distribution name has to change.

The decision

Pick the distribution name, then set [project] name accordingly and, when ready to release, flip [tool.wads.ci.publish] enabled = true. Candidates, availability unverified at the time of writing:

• heed-feedback
• i2mint-heed
• heedback
• something new entirely

Note that [project.scripts] heed = "heed.__main__:main" also installs a console script called heed, which would collide on a machine that has the other project installed. Worth renaming at the same time if the distribution name changes.

Filed during a fleet-wide CI modernization pass so the choice is not lost. Not urgent - nothing is blocked while publishing stays disabled.