[0.42-r2 M5] network-failure catch reloads the page and loses in-flight form input without an event

[SisyphusZheng]

Severity: medium · Category: framework design issue

Evidence. entry-generators.ts: the submit chain's catch does window.location.reload() unconditionally — a transient network failure discards the user's unsaved input elsewhere on the page and gives the app no hook.

Fix. Dispatch a cancelable open:action-error CustomEvent on the form (detail { error, form }) before the reload; preventDefault() suppresses the reload so apps can show their own retry UI. Default behavior (reload) is unchanged. Document in MORPH_CONTRACT.

---

Filed from the 0.42 round-2 review (docs/audit/2026-07-28-alpha5-round2-review.md). Target line: 0.42.0-alpha.6.

[SisyphusZheng]

Fixed and shipped in v0.42.0-alpha.6 (npm dist-tags latest/alpha at 0.42.0-alpha.6, tag ccc9407). The fix and its regression test landed via PR #594 (fixture suite 49 tests × 3 engines = 147 green, including the new round-2 specs; unit + parity suites green).