FA-27472 / HTTP ranges / Member archive

A row-range endpoint builds byte-addressable line record metadata: index entries expose octet counts rather than codepoint counts · case 02

A row-range endpoint builds byte-addressable line record metadata: index entries expose octet counts rather than codepoint counts.

Member previewVariant 2 · 3 implementations · 9 checks per implementation

Case contract

Build a bounded row index over UTF-8 text. A leading UTF-8 BOM is excluded from records but occupies3 representation bytes. LF or CRLF terminates a row; blank rows are ignored. A final unterminated nonempty row is included. Return [entries,selected-hex-bodies], with each entry [absolute-byte-start,content-byte-count,terminator-byte-count]. Enforce a per-record byte cap and nonnegative selected row indices. Selection order and multiplicity are meaningful.

Why this case matters

Range responses combine representation identity, conditional requests, framing, and partial-object state.

One recorded failure

Sample boundary fixture

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

Boundary fixture	Actual	Expected	Outcome
record-byte-length fixture 5	`[[[0, 2, 1]], ["c3a9c3a9"]]`	`[[[0, 4, 1]], ["c3a9c3a9"]]`	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.