FA-28729 / HTTP redirects / Member archive
Apply a configured redirect query transformation without changing retained value order: addition cardinality · case 04
Apply a configured redirect query transformation without changing retained value order: the addition cardinality branch emits an incorrect decision.
Case contract
Apply a configured redirect query transformation without changing retained value order. 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 fixtureThis sample comes from the broken implementation of a controlled reproducer.
| Boundary fixture | Actual | Expected | Outcome |
|---|---|---|---|
| fixture 5 | {"decision": [[["b", "2"], ["a", "1"]], [["b", "2"], ["a", "1"], ["c", "3"], ["c", "4"]], [["b", "2"], ["a", "1"], ["c", "3"], ["c", "4"]], ["b=2", "a=1"], "##x", ["b", "a"], [["b", "2"], ["a", "1"]], 1, ["absent"], "?"], "request": "/requests/4/4"} | {"decision": [[["b", "2"], ["a", "1"]], [["b", "2"], ["a", "1"], ["c", "3"], ["c", "4"]], [["b", "2"], ["a", "1"], ["c", "3"], ["c", "4"]], ["b=2", "a=1"], "##x", ["b", "a"], [["b", "2"], ["a", "1"]], 2, ["absent"], "?"], "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.
Sign in to the archive ↗