FA-29320 / HTTP redirects / Member archive

Report redirect failures with the failing phase and completed request context: failure from code · case 05

Report redirect failures with the failing phase and completed request context: the failure from code branch emits an incorrect decision.

Member previewVariant 5 · 3 implementations · 7 checks per implementation

Case contract

Report redirect failures with the failing phase and completed request context. 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 3	`{"decision": ["dispatch", "/a", "/b", ["/a"], "closed", false, "/a", false, ["/a"], false], "request": "/requests/5/2"}`	`{"decision": ["dispatch", "/a", "/b", ["/a"], "closed", true, "/a", false, ["/a"], false], "request": "/requests/5/2"}`	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.