FA-74264 / Feature flag rollout bucketing / Member archive

Bootstrapped flag payload merge: An equal payload version is treated as stale · case 04

A second payload with the same version but newer per-flag versions is discarded.

Member previewVariant 4 · 3 implementations · 8 checks per implementation

Case contract

Payloads are {version, flags: {key: {value, version, deleted?}}}. An incoming payload with a lower payload version than local is ignored entirely. Otherwise each incoming flag replaces the local entry only when the key is new or its flag version is strictly higher; deleted tombstones follow the same rule. Return sorted [key, value] pairs for merged flags that are not deleted.

Why this case matters

Clients bootstrap from HTML-embedded flags and then stream updates; stale data must not win.

One recorded failure

Sample boundary fixture

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

Boundary fixture	Actual	Expected	Outcome
equal payload version still merges	`[["a", 1]]`	`[["a", 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.