FA-28127 / HTTP redirects / Member archive

Expose redirect events in request order without false completion: redirect count from events · case 02

Expose redirect events in request order without false completion: the redirect count from events branch emits an incorrect decision.

Member previewVariant 2 · 3 implementations · 6 checks per implementation

Case contract

Expose redirect events in request order without false completion. The explicit fixture inputs and outputs define a bounded offline policy; request identity must accompany the decision.

Why this case matters

Models a redirect controller decision before following a target or exposing a redirect result.

One recorded failure

Sample boundary fixture

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

Boundary fixture	Actual	Expected	Outcome
fixture 1	`{"decision": [["/a", "/b", "/a"], false, 2, "/a", "canceled"], "request": "/requests/2/0"}`	`{"decision": [["/a", "/b", "/a"], false, 3, "/a", "canceled"], "request": "/requests/2/0"}`	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.