Corrupt holder share in personalized bundle fails silently

[vnykmshr]

When loadPersonalizationData runs and parseShare throws, the error is swallowed:

// app.ts:283-285
} catch {
  // Silently ignore invalid holder share
}

User sees zero shares loaded with no indication their pre-loaded piece was bad. They have no way to know whether to add it manually or why it's missing.

handleHTMLUnified (line 614) already handles the same failure path by surfacing an error when a dropped HTML file has a bad share. The initial-load path should do the same: show something like "Your pre-loaded piece could not be read. You can still add pieces manually."

[eljojo]

this was introduced recently after a refactor, thanks for reporting this