EVT 2026-02-21 - Stage D Attempt Flow Reliability and Submit Integrity Autocomplete

Session scope

Continue autonomous product completion by closing the largest remaining Stage D gap: attempt execution baseline (currently placeholder-level in UX docs).

Confirmed outcomes (auto-recommended defaults)

1. Attempt mode baseline:

• support both timed and untimed,
• timed is for simulation/full-test style attempts,
• untimed is default for normal practice attempts.

2. Draft safety baseline:

• auto-save answer state continuously while attempting,
• keep local fallback when network is unstable,
• resume from latest valid draft when user returns to unfinished attempt.

3. Submit safety baseline:

• before submit, show lightweight review summary (answered/unanswered),
• keep submit non-blocking (user can still submit with unanswered items),
• apply idempotent submit guard to prevent double-submit race.

4. Network failure handling:

• submit failure keeps attempt state intact,
• user can retry without losing answers,
• status feedback is explicit (saving/submitting/retry).

5. Timed expiration policy:

• timed attempt uses authoritative countdown,
• when time expires, attempt transitions to timeout submit path and then result.

6. Metrics and transition policy:

• only successful submit creates finalized attempt output for result pipeline,
• submission timestamp remains the source of truth for streak/metrics attribution.

Open items carried forward

• None for this attempt-baseline lock batch.