[marioolf]

Summary

The Python package is annotated throughout, but it shipped no PEP 561 py.typed marker. So mypy treats offline_protocol_sdk as untyped: every import fails with import-untyped, and every value the SDK returns is Any in the application.

This PR:

• adds the empty bindings/python/offline_protocol_sdk/py.typed;
• lists it in [tool.setuptools.package-data], which otherwise carries only the native libraries, so setuptools would leave the marker out of the wheel;
• adds the Typing :: Typed classifier;
• adds the marker to the list of files scripts/build-wheel.sh requires in the wheel, so the release build fails if it ever goes missing.

Before and after

A consumer script against the installed wheel:

from offline_protocol_sdk.relay_answer_prefixes import is_relay_answer

reveal_type(is_relay_answer)
is_relay_answer(42)  # wrong argument type: a str is expected

Without the marker (the current release):

app.py:1: error: Skipping analyzing "offline_protocol_sdk.relay_answer_prefixes": module is installed, but missing library stubs or py.typed marker  [import-untyped]
app.py:3: note: Revealed type is "Any"

With the marker:

app.py:3: note: Revealed type is "def (prefix: str) -> bool"
app.py:4: error: Argument 1 to "is_relay_answer" has incompatible type "int"; expected "str"  [arg-type]

Related issues

None.

Type of change

• fix: bug fix

Checklist

• Commits follow Conventional Commits
• CHANGELOG.md updated (Unreleased, Fixed)
• No Rust, UDL or binding-generation change, so the cargo gates and binding regeneration don't apply.

Breaking changes

None. An application already running mypy on code that uses the SDK will start getting real type errors where it used to get Any. That is the intended effect, and mypy does not report errors inside an installed package's own source.

Notes for reviewers

How I verified it:

• Built the wheel with uv build --wheel and checked it contains offline_protocol_sdk/py.typed and carries Classifier: Typing :: Typed in its metadata.
• Ran the same required-files check build-wheel.sh uses against that wheel and against a copy with the marker removed: the first passes, the second reports ['offline_protocol_sdk/py.typed'] missing. bash -n passes on the script.
• The mypy before and after above, run against that wheel installed in a clean venv.
• I did not run build-wheel.sh end to end, since it needs the native library built for each platform. CI's wheel job runs it.

[github-actions]

All contributors have signed the CLA ✍️ ✅
_{Posted by the CLA Assistant Lite bot.}

[marioolf]

I have read the CLA Document and I hereby sign the CLA

[bahdotsh]

Thank you so much for raising the PR!

LGTM!