Workbench Submit-State + API Error Contract QA

No active submit attempt is running. Operator can inspect payload and edit fields.

Operator changes form data. Result panel must clear so stale success is not trusted.

Operator can see exactly what will be submitted or prepared before pressing the button.

Preview-only action can prepare a safe packet but must not call a backend mutation.

Guarded action is ready to call an approved FAEDA API with auth and backend permissions.

Licensed partner payment draft can be created, but payout execution is still blocked.

Button is disabled, spinner is visible, and duplicate submit must be blocked.

API accepted a draft/profile/offer/RFQ/quote/evidence record only.

Payment instruction draft was accepted for licensed partner processing review only.

Packet is prepared locally and returned to the operator as evidence for the next gate.

Submit failed safely and must expose a safe error code without raw backend details.

AUTH_REQUIRED

No signed-in token exists for a backend guarded action.

Sign in required. No anonymous mutation was submitted.

PERMISSION_DENIED

Backend rejects the current actor, role, tenant, or permission.

You do not have permission for this action.

VALIDATION_ERROR

Backend rejects required fields, format, quantity, price, or scope.

Fix the highlighted data and submit again.

CONFLICT

Duplicate record, stale approval, same-user maker-checker conflict, or already processed item.

This item conflicts with an existing record or state.

NETWORK_UNAVAILABLE

API connection fails or backend is unavailable.

Connection failed. The action was not completed.

UNMAPPED_ACTION

The UI action has no approved backend mutation.

This action is not wired for backend submission yet.

API_ERROR

Unexpected safe backend error after sanitization.

Something went wrong. Review the safe error and retry later.