You have commit messages with errors ⧗ input: debug: add coreMQTT logging and hex dump for MQTTBadResponse Root cause identified: stale CONNACK data in networkBuffer persists across reconnections of the same handler. The handler is reused when MqttClient reconnects, but networkBuffer retains data from the previous connection's ProcessLoop calls. Need to either: 1. Create a fresh handler for each connection attempt, or 2. Fully reset the MQTTContext_t (including networkBuffer content) at the start of each new connection. ✖ type must be one of [build, chore, ci, docs, feat, fix, perf, refactor, revert, style, test] [type-enum] ✖ found 1 problems, 0 warnings ⓘ Get help: https://github.com/conventional-changelog/commitlint/#what-is-commitlint ⧗ input: debug: SUBACK processing works, future completion issue remains - ProcessLoop successfully processes SUBACK (no more MQTTBadResponse) - Event callback fires with correct packet IDs (1, 2) - Pending ACK lookup succeeds (found=1) - But Java subscribe futures aren't completing - Issue is in s_complete_java_future JNI upcall - Also: second connection uses same client ID (duplicate ID issue) ✖ subject must not be sentence-case, start-case, pascal-case, upper-case [subject-case] ✖ type must be one of [build, chore, ci, docs, feat, fix, perf, refactor, revert, style, test] [type-enum] ✖ found 2 problems, 0 warnings ⓘ Get help: https://github.com/conventional-changelog/commitlint/#what-is-commitlint ⧗ input: feat: PoC proven - subscribe succeeds end-to-end with IoT Core Confirmed via IoT Core logs: - Subscribe to jobs/get/accepted: Success (reasonCode=1) - Subscribe to shadow/update/accepted: Success (reasonCode=1) - Java future completion works (rc=1, no JNI exceptions) Remaining issue: nucleus creates second connection with same client ID because it needs more subscriptions. This is a Java-side connection pooling issue, not a coreMQTT issue. The MQTT protocol layer works. ✖ subject must not be sentence-case, start-case, pascal-case, upper-case [subject-case] ✖ found 1 problems, 0 warnings ⓘ Get help: https://github.com/conventional-changelog/commitlint/#what-is-commitlint ⧗ input: cleanup: remove committed build artifacts, add .gitignore ✖ type must be one of [build, chore, ci, docs, feat, fix, perf, refactor, revert, style, test] [type-enum] ✖ found 1 problems, 0 warnings ⓘ Get help: https://github.com/conventional-changelog/commitlint/#what-is-commitlint ⧗ input: cleanup: remove all debug fprintf statements ✖ type must be one of [build, chore, ci, docs, feat, fix, perf, refactor, revert, style, test] [type-enum] ✖ found 1 problems, 0 warnings ⓘ Get help: https://github.com/conventional-changelog/commitlint/#what-is-commitlint ⧗ input: cleanup: remove optimize(O0) and volatile init hack ✖ type must be one of [build, chore, ci, docs, feat, fix, perf, refactor, revert, style, test] [type-enum] ✖ found 1 problems, 0 warnings ⓘ Get help: https://github.com/conventional-changelog/commitlint/#what-is-commitlint ⧗ input: cleanup: remove unused bootstrap_handle parameter from connect ✖ type must be one of [build, chore, ci, docs, feat, fix, perf, refactor, revert, style, test] [type-enum] ✖ found 1 problems, 0 warnings ⓘ Get help: https://github.com/conventional-changelog/commitlint/#what-is-commitlint ⧗ input: cleanup: remove unused s_jstring_to_cstr helper ✖ type must be one of [build, chore, ci, docs, feat, fix, perf, refactor, revert, style, test] [type-enum] ✖ found 1 problems, 0 warnings ⓘ Get help: https://github.com/conventional-changelog/commitlint/#what-is-commitlint ⧗ input: cleanup: remove debug log from MqttClient.getConnection ✖ type must be one of [build, chore, ci, docs, feat, fix, perf, refactor, revert, style, test] [type-enum] ✖ found 1 problems, 0 warnings ⓘ Get help: https://github.com/conventional-changelog/commitlint/#what-is-commitlint ⧗ input: cleanup: disable coreMQTT logging macros for pr

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/