FA-8547 / Form submission / Member archive

Submission state transitions: Server failure details never replace old error messages · case 02

Server failure details never replace old error messages.

Member previewVariant 2 · 3 implementations · 9 checks per implementation

Case contract

A duplicate pending submit preserves pending; invalid submit retains errors; success clears errors; failure installs result errors; editing resets status and stale errors.

Why this case matters

A deterministic model of submission state transitions; this isolates one interface invariant without requiring a browser.

One recorded failure

Sample boundary fixture

This sample comes from the broken implementation of a controlled reproducer.

Boundary fixture	Actual	Expected	Outcome
failure	`["failed", {"old": "stale"}]`	`["failed", {"a": "conflict"}]`	Failed

MEMBER ARCHIVE

The complete case is available to members.

This record includes three runnable implementations, regression fixtures, execution results, and source hashes.

Member access is invitation-based. Sign in with your invited account to inspect the sources.