[tmcfarlane]

At an initial or replacement account commit, a pending logout action could be cleared by the later passive owner-reset effect. That erased pending feedback, admitted duplicate actions and suppressed the current owner's failure message. Reset ownership in the layout phase so it is settled before the committed controls can be used. The product change is two lines; same-account session renewal and stale-owner completion behavior stay covered.

Validation: a phase-controlled probe against the unchanged hook passes all seven existing controls and fails all seven new regressions. The exact same private 14-case source passes after the minimal fix. The committed regression adaptation and six existing actual-SDK logout UI cases pass all 20 cases on Node 20.20.2. Types, scoped lint and original-config production build pass. Six freshly compiled desktop/mobile browser cases pass once with zero retries; four actual failure/retry captures are verified against published exact-head bytes. A mismatched disposable build hostname caused an earlier six-case failure before sign-out; that separate harness failure is preserved.. The earlier combined 981-pass/one-failure run remains preserved; its exact chronology was not instrumented, so it is consistent with this proven race rather than uniquely attributed to it. Full exact-head CI is required before merge into v0.8.

These are actual compiled disposable SDK transport fixtures, showing retained Account failure feedback and explicit retry. They do not sign out a human production account.

Controlled source/evidence receipt · Compiled browser receipt.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
zeroclickboards	Ready	Preview	Oct 2, 2026 1:56pm UTC