FA-9693 / Configuration / Member archive

Configuration change plan: All common keys are reported changed · case 03

All common keys are reported changed.

Member previewVariant 3 · 3 implementations · 7 checks per implementation

Case contract

Produce sorted added, removed, changed, restart-required, and unchanged key lists. Restart applies only to added/removed/changed keys in the restart set.

Why this case matters

An offline model of configuration change plan, suitable for testing build and release tooling without external services.

One recorded failure

Sample boundary fixture

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

Boundary fixture	Actual	Expected	Outcome
fixture 5	`{"added": [], "changed": ["a"], "removed": [], "restart": ["a"], "unchanged": []}`	`{"added": [], "changed": [], "removed": [], "restart": [], "unchanged": ["a"]}`	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.