v0.4.2

Bug-fix patch plus release-tooling automation. Two changes:

• Fix: updateDataModel.patch shape was silently bypassed by the chash resolver walker (only value was enumerated). Producers using sparse data-model updates with chash references now get them resolved through wrap_as_mcp_ui_resource like value-shaped payloads do (palinex-e7z).
• CI: .github/workflows/release.yml now builds the .mcpb Claude Desktop extension bundle automatically on every v* tag push and attaches it to the GitHub Release alongside the wheel + sdist (palinex-hg3). v0.4.2 is the first release exercising this workflow.

Added

• .github/workflows/release.yml now builds and attaches the .mcpb Claude Desktop extension bundle on every v* tag push, closing the gap RDR-003 §Item 3a flagged (mcpb pack mcpb /tmp/palinex-<version>.mcpb via @anthropic-ai/mcpb, plus an mcpb/manifest.json version-vs-tag parity check that fails loud on drift). Inlined into the existing release workflow rather than a separate release-mcpb.yml — single release job prevents two workflows racing on the GitHub Release creation step. Future tags will see palinex-<version>.mcpb as a downloadable asset alongside the wheel and sdist. (palinex-hg3)

Fixed

• _pre_resolve_payload now recognises updateDataModel.patch (src/palinex/__init__.py). a2ui v0.9 updateDataModel may carry either value (full state at path) or patch (sparse update). The pre-fix _data_model_locations walker only yielded value locations, so payloads using patch were silently passed through with no chash resolution. Fix extends the walker to yield both shapes for messages[].updateDataModel and for the top-level updateDataModel variant. Three new tests in tests/test_builders.py cover envelope-shape patch, top-level patch, and mixed value+patch in the same payload. (palinex-e7z)