Explicitly declare py.typed in the wheel manifest

Hatchling's default file selection already picks up py.typed via
the ``packages`` directory, but declaring it explicitly via
force-include is the documented PEP 561 pattern and keeps the
intent obvious to anyone auditing the wheel contents (or to any
future refactor of the source layout).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: antoineleclair

pyproject.toml

@@ -34,6 +34,12 @@ dev = ["pytest>=8.0", "pytest-cov>=4.0", "mypy>=1.0", "ruff>=0.4"]
 [tool.hatch.build.targets.wheel]
 packages = ["src/dqlitewire"]
 
+# Hatchling's default file-selection would already ship ``py.typed`` via
+# ``packages``, but declaring it explicitly is the documented PEP 561
+# pattern and makes the intent obvious to anyone auditing the wheel.
+[tool.hatch.build.targets.wheel.force-include]
+"src/dqlitewire/py.typed" = "dqlitewire/py.typed"
+
 [tool.pytest.ini_options]
 testpaths = ["tests"]
 pythonpath = ["src"]