FA-28113 / HTTP redirects / Member archive

Commit redirect history only after target admission: failed hop retention · case 03

Commit redirect history only after target admission: the failed hop retention branch emits an incorrect decision.

Member previewVariant 3 · 3 implementations · 6 checks per implementation

Case contract

Commit redirect history only after target admission. 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": [["/z", "/a"], ["/z", "/a"], "/a", false, {"completed": ["/z", "/a", "/b"], "rejected": null}], "request": "/requests/3/0"}`	`{"decision": [["/z", "/a"], ["/z", "/a"], "/a", false, {"completed": ["/z", "/a"], "rejected": "/b"}], "request": "/requests/3/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.