fabric_backup includes the bridge node's storage (identity.json, endpoint-map.json, the matter.js store) in the archive under a bridge-node/ prefix, but restore deliberately skips those members — it warns, names the prefix and prints a manual recipe instead.
The reason was that restoring needs the bridge node stopped, and there was no stop seam. E7 added one (Stop the Matter export bridge… / the agent's stop path), so the blocker is gone.
Deferred item recorded in docs/HANDOVER.md. Losing that directory is the failure mode E5 exists to prevent, so a restore that silently omits it is the one to close.
fabric_backupincludes the bridge node's storage (identity.json,endpoint-map.json, the matter.js store) in the archive under abridge-node/prefix, but restore deliberately skips those members — it warns, names the prefix and prints a manual recipe instead.The reason was that restoring needs the bridge node stopped, and there was no stop seam. E7 added one (
Stop the Matter export bridge…/ the agent's stop path), so the blocker is gone.Deferred item recorded in
docs/HANDOVER.md. Losing that directory is the failure mode E5 exists to prevent, so a restore that silently omits it is the one to close.