fix: decode IDNA labels in non-leading position

[mbeijen]

Supersedes #979 — uses the new idna.decode(..., display=True) added in idna 3.18 (kjd/idna#248, kjd/idna@1a5bf80, released 2026-06-02), so the per-label recovery lives in idna where Kludex preferred it.

---

AI-assisted: change drafted by Claude under my review.

[codspeed-hq]

Merging this PR will not alter performance

✅ 15 untouched benchmarks
⏩ 7 skipped benchmarks¹

---

_{Comparing mbeijen:fix-url-host-nested-idna-display (91e7c3c) with main (26dd31e)}

Footnotes

1. 7 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩

[cubic-dev-ai]

1 issue found across 5 files

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="pyproject.toml">

<violation number="1" location="pyproject.toml:6">
P2: `exclude-newer-package` uses a hardcoded timestamp that will permanently cap `idna` versions after the temporary workaround period expires</violation>
</file>

<sub>Reply with feedback, questions, or to request a fix.

Re-trigger cubic</sub>

[cubic-dev-ai]

P2: exclude-newer-package uses a hardcoded timestamp that will permanently cap idna versions after the temporary workaround period expires

Prompt for AI agents

Check if this issue is valid — if so, understand the root cause and fix it. At pyproject.toml, line 6:

<comment>`exclude-newer-package` uses a hardcoded timestamp that will permanently cap `idna` versions after the temporary workaround period expires</comment>

<file context>
@@ -3,6 +3,7 @@ package = false
 default-groups = ["dev", "docs", "bench"]
 required-version = ">=0.8.6"
 exclude-newer = "7 days"
+exclude-newer-package = { idna = "2026-06-03T00:00:00Z" }
 
 [tool.uv.workspace]
</file context>