Rename Python distribution to `markdown-script` (import `markdown_script`) + register on PyPI

[dean0x]

crates/mds-python/README.md advertises pip install markdown-script (the package was renamed to markdown-script per ADR-012; see also #306). As of 2026-09-02, markdown-script is unregistered on PyPI (https://pypi.org/pypi/markdown-script/json returns 404). An unregistered name is a squatting risk — a third party could claim it before the first wheel is published. A PyPI pending publisher was filed 2026-08-25 for project markdown-script (repo dean0x/mdscript, workflow release.yml) — pending publishers do not reserve the name and this one lapses unused around 2026-09-24. Only a real upload claims the name.

Note: mdscript on PyPI is an unrelated dormant 2021 project (owner Inoft.Robinson) with a colliding top_level.txt — it is not available and cannot be used. ADR-012 explicitly rejected mdscript and selected markdown-script as the distribution name; this is not up for re-litigation. markdown-script is the correct target name. The rename fully landed in PR #308; pyproject.toml name = "markdown-script", CI installs and imports it end-to-end. Only PyPI registration remains.

The full publishing pipeline (cross-platform wheel matrix + PyPI publish) is tracked in #132. release.yml has no PyPI step and mds-python is publish = false, so v0.4.0 shipped nothing to PyPI. This issue covers name registration only; the CI wiring is #132's scope. It is a name-squatting risk that widens on announcement.

Acceptance Criteria

• Log in to PyPI as the package maintainer
• Register the markdown-script name by publishing a first release to PyPI (PyPI has no name-reservation mechanism — only a real upload claims the name; the wheel matrix and full publish pipeline are tracked in Python bindings: cross-platform wheel matrix + PyPI publishing (+ cp314t) #132)
• Confirm the name appears at https://pypi.org/project/markdown-script/ and is owned by the designated maintainer account
• Update RELEASING.md to note the name is registered (prerequisite for Python bindings: cross-platform wheel matrix + PyPI publishing (+ cp314t) #132)

[dean0x]

Re-scoped: original premise falsified — this is not a v0.4.0 blocker

Research has falsified the premise this issue was filed on. The original framing was
"mdscript is unregistered on PyPI, so announcing v0.4.0 widens a squatting window."
Both halves of that are wrong.

Evidence

mdscript on PyPI is a genuine project, not an unclaimed name and not a squat.

• 5 releases in April 2021
• Real, working code: runner.py, watcher.py, cli.py; dependencies on click and watchdog
• Summary: "Brings powerful scripting to markdown files with hot reload."
• Dormant ~5 years, ~16 downloads/month, 0 stars

That is a direct topical collision — same name, same problem space — which is the
worst case for user confusion, not a drive-by name grab.

PEP 541 offers no route to the name. PEP 541 states: "Under no circumstances will a
name be reassigned against the wishes of a reachable owner." The owner's GitHub profile
showed activity 12 days ago, so the owner is reachable. A PEP 541 claim would fail.

The name cannot be worked around by only changing the distribution name. Publishing
under a different distribution name while keeping import mdscript does not work: their
sdist ships mdscript/__init__.py and their top_level.txt is exactly mdscript. Both
packages would install a top-level mdscript/ directory into site-packages, and
whichever is installed second silently overwrites the first — no pip error, no conflict
warning, just a broken import for one of them. Both the distribution name and the
module name must change.

No release window is being widened. The name has been taken since 2021. The v0.4.0
announcement changes nothing about its availability. Nothing in v0.4.0 publishes to PyPI
at all — PyPI publishing is deferred work tracked in #132.

Conclusion: this is not a v0.4.0 release blocker. Milestone moved from v0.4.0 to
v0.5.0.

Decision (ADR-012)

The Python distribution ships as:

	Value
Distribution name (PyPI)	markdown-script
Import / module name	markdown_script

Both change together, for the top_level.txt collision reason above.

Verified PyPI Trusted Publisher values (for #132)

To be configured when #132 lands the publishing job:

Field	Value
Owner	dean0x
Repository	mdscript
Workflow filename	release.yml
Environment name	(blank)

If #132 later adds environment: pypi to that job, the trusted-publisher record must
be updated to match, or publishing will be rejected.

Remaining work (supersedes the original acceptance criteria)

The original acceptance criteria in the issue body are void — the mdscript name cannot
be registered. The real work is:

• Rename the distribution to markdown-script in crates/mds-python/pyproject.toml
• Rename the module to markdown_script (PyO3 #[pymodule] name, Cargo.toml
[lib] name, and any maturin module-name setting)
• Update crates/mds-python/tests imports and any example/doc snippets
• Update crates/mds-python/README.md — it currently advertises pip install mdscript
• Update RELEASING.md and CLAUDE.md references to the Python package name
• Register markdown-script on PyPI (first publish happens as part of Python bindings: cross-platform wheel matrix + PyPI publishing (+ cp314t) #132)
• Configure the trusted publisher with the values above

This issue stays open: the rename is real work and the registration still has to happen.

[dean0x]

Deferred from v0.4.0 code review

Finding: python-05 from wave-v0.4.0-wave1 review (2026-08-19_1216)

File:Line: crates/mds-python/Cargo.toml:42

Issue: Wheel-only vs vendored-sdist decision belongs to design in issues #132 and #292.

Reason for deferral: This cross-issue decision should be made alongside the wheel matrix planning.

Related: PR #308 (wave/v0.4.0-wave1), issue #132

[dean0x]

Status check 2026-09-02: markdown-script still returns 404 from both /pypi/markdown-script/json and /simple/markdown-script/ (nobody has it). The pending trusted publisher filed 2026-08-25 (project markdown-script, dean0x/mdscript, workflow release.yml, environment blank) does NOT reserve the name (PyPI docs: a pending publisher creates nothing until first use, and a third party registering first invalidates it), and pending publishers expire after 30 days unused (warehouse PENDING_PUBLISHER_EXPIRY_DAYS = 30 with a 5-day reminder, pypi/warehouse PR #19996, 2026-05-04; not mentioned in the docs). Expect a reminder email around 2026-09-19 and deletion around 2026-09-24 unless a first upload happens; re-filing is a two-minute form. v0.4.0 publishes nothing to PyPI (release.yml has no PyPI job; mds-python is publish = false).

[dean0x]

Satisfied by the v0.4.2 release on 2026-09-03: markdown-script is live on PyPI at https://pypi.org/project/markdown-script/ with 8 distributions (7 cp311-abi3 wheels + sdist) published via trusted publishing with PEP 740 attestations. Note: this issue's body refers to mdscript; that text predates ADR-012, which selected the markdown-script distribution name (import as markdown_script).