FA-74140 / Feature flag rollout bucketing / Member archive

Multi-context canonical key: Context kinds follow insertion order · case 05

The same user+org context built in a different order buckets differently.

Member previewVariant 5 · 3 implementations · 8 checks per implementation

Case contract

contexts maps kind -> key. Empty input or any empty key -> None. A context containing only the kind "user" is keyed by the bare user key. Otherwise join, over kinds in sorted order, kind + ":" + escaped key with ":", where escaping replaces "%" by "%25" and then ":" by "%3A".

Why this case matters

Canonical context keys feed bucketing and caches; two spellings of one context split its traffic.

One recorded failure

Sample boundary fixture

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

Boundary fixture	Actual	Expected	Outcome
three kinds	`"device:d1:app:z:user:bob"`	`"app:z:device:d1:user:bob"`	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.