What I observed
Google connection showed an unverified-app warning and a reported scope-change failure after consent, leaving OpenHome disconnected. Discord displayed test-app branding; Slack displayed an approval warning, although the user reported the integration worked. Historical W01/W02 observations were not reproduced in the follow-up and are excluded from this priority.
Why it matters
Consent and connection health guide consequential user decisions. Granting permission at a provider does not by itself establish that OpenHome has a usable connection.
Recommended behavior
Distinguish consent granted, connection usable, partial permissions and disconnected states. Explain missing permissions and provide a clear recovery path. Complete applicable provider verification and use consistent production-facing integration names.
Acceptance
After save and reload, privacy labels agree with server state. Each activity card belongs to the current invocation. Full, partial, cancelled and previously granted consent flows produce accurate connection status and a useful next step; verify usability with a read-only integration check.
Evidence limits: W01 and W02 were not exact-fixture reproducible in the follow-up and are retained only as unverified observations. The Slack warning did not establish an integration failure. Google recovery and provider-token handling need a controlled retest. Evidence references: W11–W14.