What happens to the source's Durable Object namespaces.
fresh: the fork declares the same classes and gets its own empty namespaces. The default,
because a new environment usually wants its own data.
shared: the fork's bindings carry script_name pointing at the source, so both Workers address
one namespace. Useful for a read-only preview of live data, and dangerous for anything that
writes.
transfer: the namespace MOVES. The target declares expecting-transfer and the source declares
transferred, in two deploys. This is not a copy, and the source loses the data.
What happens to the source's Durable Object namespaces.
fresh: the fork declares the same classes and gets its own empty namespaces. The default, because a new environment usually wants its own data.shared: the fork's bindings carryscript_namepointing at the source, so both Workers address one namespace. Useful for a read-only preview of live data, and dangerous for anything that writes.transfer: the namespace MOVES. The target declaresexpecting-transferand the source declarestransferred, in two deploys. This is not a copy, and the source loses the data.