@@ -131,7 +131,7 @@ this app's data, local data, WebView storage, caches and plugin storage. It cann
131131reach the clipboard, exported keys or relay data, and the dialog says so. Sign out
132132is unavailable with the development broker (` BUZZ_DEV_VIEWER ` ). Development
133133builds can sign out but not wipe: they have their own human key, but share agent
134- keys and plugin storage with the installed app, so the native command refuses
134+ keys with the installed app, so the native command refuses
135135wipe. The dialog asks the native side (` sign_out_wipe_refusal ` ) whether wipe is
136136available and, when it isn't, disables wipe up front with the reason; this holds
137137for any Rust debug build, including a debug bundle with a production frontend. A development-build sign-out signs out every
@@ -147,7 +147,32 @@ before it looks for a pending sign-out:
147147 by every copy using that key whatever its identifier; and
148148- the ** all-Buzz lock** (` .dev.local.buzz.foundation.instance.lock ` ), named for
149149 the storage all builds share (the default plugin folder and the agent key
150- service), not for the app identifier.
150+ service), not for the app identifier. It keeps the identifier Buzz used before
151+ 1.0, so those builds and later ones exclude each other.
152+
153+ Before 1.0, Buzz's identifier was ` dev.local.buzz.foundation ` . Before taking these
154+ locks, a launch as ` xyz.block.buzz.desktop ` renames what the old identifier names:
155+ app data (with plugin storage), config, local data, caches, macOS WebKit storage,
156+ their sign-out trash and a pending sign-out marker, so the update keeps
157+ everything and finishes a sign-out the old build committed. It takes the all-Buzz
158+ lock alone and waits for every agent ownership lock, so it never moves storage
159+ another copy or a stopping agent still uses. If any legacy path sits beside its
160+ new-identifier counterpart, after a rollback for instance, the launch moves
161+ nothing, finishes no pending sign-out, and exits naming every such pair; neither copy
162+ is safely the one to keep, and an erase would miss the legacy one. A failure exits
163+ with a native alert, and the next launch moves what is left. Development launches
164+ (` just desktop ` , ` just desktop-bundle ` ) use ` xyz.block.buzz.desktop.dev ` , so they
165+ keep their own app data and plugin storage and never take or block the installed
166+ app's. The first one copies the installed app's app data (without the release-only
167+ ` archive ` ), config, local data and macOS WebKit storage, each from
168+ ` xyz.block.buzz.desktop ` , else ` dev.local.buzz.foundation ` , under the same locks,
169+ so the installed app must be closed once, and takes a pending development
170+ sign-out marker. It refuses while the installed app has a sign-out pending, so it
171+ never copies storage being erased. A linked folder copies what it links to; links
172+ inside are left out, so the copy shares nothing with the installed app's storage,
173+ which stays in place. Copied folders keep who else may read them, but stay
174+ writable by their owner. An interrupted copy finishes at the next launch. Credential service
175+ names don't change; on macOS, Keychain may ask once to allow the renamed app to use each saved item.
151176
152177A sign-out needs its key lock alone, so every other copy using that key must be
153178closed. A wipe also needs the all-Buzz lock alone, so every other Buzz must be
0 commit comments