Skip to content

Require live Bluetooth health for syauth panel readiness - #9

Merged
dmytrogajewski merged 1 commit into
mainfrom
fix/syauth-transport-health
Nov 7, 2026
Merged

dmytrogajewski merged 1 commit into
mainfrom
fix/syauth-transport-health

Conversation

@dmytrogajewski

@dmytrogajewski dmytrogajewski commented Nov 6, 2026 •

Copy link
Copy Markdown
Owner

The panel showed a blue ready key while syauth retained a removed Bluetooth controller and could no longer advertise. Require daemon.transport_ready: true before showing readiness. A reported transport failure overrides pending authentication; a daemon without health reporting prompts an update. Ordinary unanswered approvals remain request history when transport is healthy.

The companion transport repair is Mewplane/syauth#6. It detects controller loss, exits for managed-service recovery, and rebuilds GATT and advertising on the available controller with the existing bond. This PR adds renderer and executable regressions, troubleshooting guidance, and the incident report.

Validation: the isolated PR worktree passes make lint, make test (1,670 passing results, zero failures, 12 ignored), make lint-spark, and all 17 Spark bridge tests. Markdown and spelling checks pass for the changed documents. Native RPM builds and package verification pass. The installed panel consumes the new health field, the phone resubscribed, and a fresh sudo challenge succeeded through phone approval in 2.135 seconds. All seven bond/key files retain their original contents, ownership, and modes.

All applicable GitHub checks pass on d141754, including Fedora 43/44/45 RPM builds, Rust documentation, Markdown, spelling, links, prose, and the documentation site. Package matrix: https://github.com/dmytrogajewski/sy/actions/runs/42307879861

@dmytrogajewski
dmytrogajewski merged commit e941de1 into main Nov 7, 2026
11 checks passed
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.

2 participants