FA-24568 / Client state / Member archive

Incremental client response projection: Unconsumed tail after frame · case 03

Unconsumed tail after frame.

Member previewVariant 3 · 3 implementations · 70 checks per implementation

Case contract

The client stream view tracks a chunk cursor independently from rendered text. Per-frame budgets consume chunks including empty chunks. Completion waits for drain, and cancellation preserves committed text but discards pending output. Operation unconsumed-tail-after-frame has the six explicit input/output oracles below.

Why this case matters

An offline client lifecycle model that isolates a state-management defect without DOM rendering or network services.

One recorded failure

Sample boundary fixture

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

Boundary fixture	Actual	Expected	Outcome
unconsumed-tail-after-frame scenario 1	`["c"]`	`[]`	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.