FA-28459 / HTTP redirects / Member archive

Resolve stored redirect chains with per-entry freshness and provenance: entry age clock rollback · case 04

Resolve stored redirect chains with per-entry freshness and provenance: the entry age clock rollback branch emits an incorrect decision.

Member previewVariant 4 · 3 implementations · 6 checks per implementation

Case contract

Resolve stored redirect chains with per-entry freshness and provenance. 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 5	`{"decision": [["/a", "/a"], 0, false, -1, "cache", false, "/a", 2, false, []], "request": "/requests/4/4"}`	`{"decision": [["/a", "/a"], 0, false, 0, "cache", false, "/a", 2, false, []], "request": "/requests/4/4"}`	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.