Set up source-grounded frontend research workflows with infospace-bench
Assistant: codex Assistant-Model: gpt-6-astra Assistant-Session: 01a0cffe-206f-7323-89d3-b20ca4cf4bf9
This commit is contained in:
parent
debf9e0aa0
commit
fc8a7dbb49
40 changed files with 1947 additions and 8 deletions
21
research/bench/fixtures/source.md
Normal file
21
research/bench/fixtures/source.md
Normal file
|
|
@ -0,0 +1,21 @@
|
|||
---
|
||||
title: Synthetic interrupted form scenario
|
||||
author: frontend-patterns test fixture
|
||||
locator: repository:research/bench/fixtures/source.md
|
||||
version: '2026-09-24'
|
||||
accessed: '2026-09-24'
|
||||
evidence_kind: synthetic
|
||||
---
|
||||
# Synthetic interrupted form scenario
|
||||
|
||||
## Scenario
|
||||
|
||||
A user types into a form while the server is unreachable. The draft remains
|
||||
visible in the current session. On reconnect, the server can reject submission.
|
||||
The interface shows pending and rejected states separately from committed data.
|
||||
|
||||
## Trade-off
|
||||
|
||||
Keeping drafts near the interaction improves continuity but requires explicit
|
||||
handling of divergence from accepted server data. This fictional example does
|
||||
not establish recurrence, persistence after restart or accessibility compliance.
|
||||
Loading…
Add table
Add a link
Reference in a new issue