Skip to content

RC12: BLE connection ownership and credential-safe diagnostics - #3

Draft
danoev wants to merge 7 commits into
codex/rc10-sdk-v0.1.11-basefrom
codex/rc12-connection-safety
Draft

danoev wants to merge 7 commits into
codex/rc10-sdk-v0.1.11-basefrom
codex/rc12-connection-safety

Conversation

@danoev

@danoev danoev commented Sep 27, 2026

Copy link
Copy Markdown
Owner

This is a hosted-validation draft PR for the preserved SDK 0.1.11 lineage. Its base is codex/rc10-sdk-v0.1.11-base at 0d2b156eceb15c5ac30bafe632d883cdc1f66171. It is not intended to merge into current SDK main, which uses a newer transport lineage. No auto-merge is requested.

Integration RC12 pins exactly 65a196a4415516039fd98fe40ccdccc7dccfec23 through its immutable hosted GitHub archive. The validation head must remain at that exact SHA. GitHub comparison against the frozen base confirms seven commits ahead and zero behind: the original configurable-attempts commit 53c7818, followed by six accepted RC12 corrective commits.

  • Retain ownership of the connector-created public Bleak backend before connection setup awaits. Failed or cancelled setup retains the handle so cleanup remains possible. Cleanup evidence requires successful owned-backend disconnect, a false public connected flag, and release of the SDK handle, or explicit evidence setup never started.
  • Exercise cancellation during connection setup and disconnect, including pending setup, backend disconnect when the connected flag is false, and uncertain cleanup. These changes support the integration's conservative replacement/unload decisions.
  • Redact credential-bearing payloads, wire frames, authentication tokens, parser/cloud-row exception text, and malformed-frame diagnostics. Keep opcode/status/count/size information useful without exposing secrets; wire protocol behavior remains unchanged.
  • Cover the ownership contract with actual connector compatibility and transient-retry tests, including retry behavior beyond max_attempts=1 and tests against connector 4.6.3 and isolated 4.7.0.

Local SDK validation: 288 tests passed, 98.28% coverage, with Ruff, Ruff formatting, and mypy passing. Integration validation against the actual hosted immutable SDK: 443 tests passed, 96.70% coverage; its hosted CI, HACS, hassfest, version checks, and CodeQL pass at integration head 49f4243b88bb490facaa96ed5e656a9c66a4c968 (integration PR #4). This PR exists to obtain the SDK's existing hosted CI and CodeQL results at the pinned head without changing workflow triggers or code.

Hardware validation remains pending and must use the eventual GitHub RC12 prerelease, release-generated ZIP, HACS, actual Home Assistant, and physical locks. Public backend cleanup evidence does not independently attest radio/proxy-slot release. No stable-readiness claim is made.

Original Rodrigo Roque / roquerodrigo/ttlock-ble project provenance, copyright, authorship, and Git history remain preserved. Existing SDK PRs #1 and #2 remain separate and untouched. No merge, main change, tag, or release is authorised by this validation PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant