migration: setup-to-pyproject output rough edges + v-prefix pin examples

[thorwhalen]

Found during the first repo-improvement rollout pilot (a real Old→stub migration). Code-level fixes that need golden/doctest updates, so filing rather than drive-by-fixing:

wads-migrate setup-to-pyproject output:

1. Emits the deprecated [project.license] text = ... table — should emit the PEP 639 SPDX string (license = "Apache-2.0").
2. Leaves project_name = "" in [tool.wads.ci] — should fill it with the package name (empty string risks a wrong --cov target).
3. Writes testpaths = ["tests"] unconditionally — when the repo has no tests/ dir (doctest-only suites are common), it should point at the package dir so CI collects doctests instead of falling back to rootdir-wide collection (which can import docsrc/conf.py and other non-test files).

v-prefix in pin examples (i2mint tags are bare versions like 0.1.81; @v0.1.81 references a nonexistent ref):
4. wads/data/github_ci_uv_stub.yml comment: change \@master` to a wads tag (e.g. `@v0.1.81`)— golden-pinned inwads/tests/data/golden/python_lib/.github/workflows/ci.yml, so fixing requires regenerating goldens. 5. wads/migration.py: docstrings, doctests (pin='@v0.1.81'), and the ci-to-stubhint string — which also suggestsgh release list -R i2mint/wads, but wads publishes tags, not GitHub releases (gh api repos/i2mint/wads/tags` works).

The shipped skills already document workarounds (wads-migrate SKILL.md post-conversion review note; wads-ci-health pin pitfall) — this issue is about fixing the sources so the workarounds become unnecessary.

[thorwhalen]

Triage / plan

Five concrete, independently-fixable rough edges, still current against `wads/migration.py`:

1. PEP 639 SPDX `license = "..."` instead of `[project.license] text = ...` -- straightforward, but touches the golden-pinned `wads/tests/data/golden/python_lib/.github/workflows/ci.yml` migration output and needs a matching update to the main scaffolder template's own license handling (currently also emits the deprecated table form, per fix: declarable CI install timeout + Windows-blocking knobs; ship wads_configs.json in the wheel #91-era `pyproject_toml_tpl.toml`) for consistency -- worth doing together, not just in `wads-migrate`.
2. Fill `project_name` from the package name instead of leaving `""` -- small, low-risk.
3. Point `testpaths` at the package dir when no `tests/` exists -- same doctest-collection hazard class as run-tests-uv: testpaths silently overrides root-dir — package doctests never run, CI stays green #56 (a repo could go from "collects nothing, green" to "collects doctests that hang/fail"); should land after run-tests-uv: testpaths silently overrides root-dir — package doctests never run, CI stays green #56's warn-first step, not before, for the same reason.
   4/5. v-prefix pin examples + `gh release list` hint (wads publishes tags, not releases) -- pure docstring/string fixes, no behavior change, safe to land now.

Not implementing this pass (time-boxed toward several smaller independent fixes this session -- see #90, #75, #57, #58, #59, #96 landed above). Items 4/5 are the safest immediate pick if you want a small follow-up PR; items 1/2 need the golden regeneration dance; item 3 should wait on #56's resolution.

[thorwhalen]

Cloud sweep (PR #99): items 1, 2, 4 and 5 are done. Item 3 stays open until the #56 rollout decision.

1. setup-to-pyproject and populate now write a PEP 639 license = "<SPDX>" string through the new wads.toml_util.pep639_license. A name that is not valid SPDX keeps the table form, because Hatchling rejects a non-SPDX license string. The same fallback applies when packaging is older than 24.2. A freshly populated project builds with hatchling 1.32 (License-Expression: MIT) and passes twine check. The golden pyproject.toml was regenerated.
2. No code change was needed: CIConfig already falls back from an empty project_name to [project].name, so --cov never gets an empty target. A test now pins that behaviour.
3. This was already fixed on master: the stub comment uses @0.2.15.
4. The fleet-stub --pin help and the ci-to-stub hint no longer suggest @v... pins or gh release list. They now suggest gh api repos/i2mint/wads/tags, and a test guards the source.

Tests: wads/tests/test_migration_rough_edges.py.

---

Generated by Claude Code