Issue #50: document client packaging

clients/python/README.md

@@ -47,6 +47,28 @@ The tests import the generated gateway and worker stubs, run fake async gateway
 stubs, verify API key metadata, exercise stream cancellation, load shared value
 and command fixtures, and check deterministic CLI output.
 
+## Packaging
+
+Install the package in editable mode for local development:
+
+```powershell
+python -m pip install -e ".[dev]"
+```
+
+Build a wheel from `clients/python`:
+
+```powershell
+python -m pip wheel . --no-deps --wheel-dir "$env:TEMP\mxgateway-python-wheel"
+```
+
+Install the generated wheel into a target environment:
+
+```powershell
+python -m pip install <wheel-path>
+```
+
+The wheel exposes the `mxgw-py` console script.
+
 ## Library Usage
 
 The library is async-first:
@@ -105,3 +127,27 @@ mxgw-py write --session-id <id> --server-handle 1 --item-handle 2 --type int32 -
 Use `--api-key` or `--api-key-env MXGATEWAY_API_KEY` to attach API key
 metadata. `smoke` opens a session, registers, adds an item, advises, streams a
 bounded event count, and closes the session in a `finally` block.
+
+Use TLS options for a secured gateway:
+
+```powershell
+mxgw-py smoke --endpoint mxgateway.example.local:5001 --tls --ca-file C:\certs\mxgateway-ca.pem --server-name-override mxgateway.example.local --api-key-env MXGATEWAY_API_KEY --item Object.Attribute --json
+```
+
+## Integration Checks
+
+Run live checks only when a gateway and MXAccess-backed worker are available:
+
+```powershell
+$env:MXGATEWAY_INTEGRATION = '1'
+$env:MXGATEWAY_ENDPOINT = 'localhost:5000'
+$env:MXGATEWAY_API_KEY = 'mxgw_key_id_secret'
+$env:MXGATEWAY_TEST_ITEM = 'Object.Attribute'
+mxgw-py smoke --endpoint $env:MXGATEWAY_ENDPOINT --plaintext --api-key-env MXGATEWAY_API_KEY --item $env:MXGATEWAY_TEST_ITEM --json
+```
+
+## Related Documentation
+
+- [Client Packaging](../../docs/ClientPackaging.md)
+- [Client Proto Generation](../../docs/client-proto-generation.md)
+- [Python Client Detailed Design](../../docs/clients-python-design.md)