CollaborativeMarkdownView hard-fails loading a document whose node was deleted (stale Hardware/SamuelGlauserMacBookAir) #6076

What is failing

A portal client session whose collaborative document was opened on the node Hardware/SamuelGlauserMacBookAir — since deleted — fails when MeshWeaver.Blazor.Components.CollaborativeMarkdownView loads that document: message delivery to the dead path raises a DeliveryFailureException: No node found, and the component logs it as a hard failure instead of degrading to a not-found/empty state.

Probable cause — high confidence

The node was deleted (likely merged into Hardware/MacBookAir16GB) while the session's view areas still addressed it. Evidence: the Hardware partition now contains only Hardware/MacBookAir16GB (edited at 2026-10-04 08:52:46 by sglauser — the user the missing node was named after), three minutes before the failure burst; the missing path has no version history. The document-loading path in the view layer has no not-found handling for a deleted target. This is the CollaborativeMarkdownView log site of a single event that also surfaced as sibling incidents in five other view components; the sibling HtmlView triage (#6074) already enumerates all six incidents of this burst, including this one. Treat this ticket as a duplicate of #6074; a human can close it in seconds once the sibling is confirmed.

Impact

Nuisance-level: one occurrence, one pod, one user's stale page against a deleted node, cleared by navigating away or recreating the node. The underlying defect class — deleting a node that saved view areas still reference — will keep reproducing across every view component until the delete flow cleans up/re-targets references or the view layer degrades gracefully on a not-found address.

Where to look

• MeshWeaver.Blazor.Components.CollaborativeMarkdownView — the document-loading code behind the Loading document {path} in Area {path} log site: catch the activation DeliveryFailureException and render a not-found/redirect control instead of failing the view.
• The delete/merge flow that leaves saved view areas addressing the removed path — the shared root cause across all six sibling incidents of this burst (see Saved view areas keep referencing deleted nodes and HtmlView hard-fails on delivery (deleted Hardware/SamuelGlauserMacBookAir) #6074).
• Concrete case: deleted Hardware/SamuelGlauserMacBookAir vs. Hardware/MacBookAir16GB (same workspace, edited minutes before the failure).

Evidence

2026-10-04 08:55:40Z memex-portal-deployment-64796f4f56-dfp92 fail: MeshWeaver.Blazor.Components.CollaborativeMarkdownView[0]
      Loading document Hardware/SamuelGlauserMacBookAir in Area Overview/2/1/2
      MeshWeaver.Messaging.DeliveryFailureException: No node found at 'Hardware/SamuelGlauserMacBookAir'. Closest ancestor is 'Hardware' (remainder='SamuelGlauserMacBookAir').

_{Opened automatically from Admin/_LogIncident/13f627adfb488584. Recurrences are folded into this issue rather than opening new ones.
It also stands for the whole log site df09b286b001ae5d: other fingerprints of this site fold in here as comments rather than opening tickets of their own.}