<?xml version="1.0" encoding="UTF-8"?><oembed><type>video</type><version>1.0</version><html>&lt;iframe src=&quot;https://www.loom.com/embed/dfbc2b34f33d46d0827f4b471f6c5183&quot; frameborder=&quot;0&quot; width=&quot;1662&quot; height=&quot;1246&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1246</height><width>1662</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1246</thumbnail_height><thumbnail_width>1662</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/dfbc2b34f33d46d0827f4b471f6c5183-182660f5771f00b4.gif</thumbnail_url><duration>127.251</duration><title>End to End Obsidian Import Verification</title><description>This Loom demonstrates an end-to-end test of a newly published page and its node import behavior in Obsidian. The presenter imports the same node into a second graph, confirms the page loads with its image asset, refreshes to show nothing changes, and verifies the imported asset map. They then repeat the import in another environment, confirming the Firebase storage link is converted and the attachment appears in the Attachments folder. After recording the token-related values (TF and D8), they refresh again and note the values remain unchanged and nothing new appears.</description></oembed>