FA-9980 / Packaging / Member archive

Reproducible archive metadata: Archive entry order follows filesystem enumeration · case 05

Archive entry order follows filesystem enumeration.

Member previewVariant 5 · 3 implementations · 4 checks per implementation

Case contract

Return sorted entries with normalized owner/group, fixed timestamp, preserved executable distinction, and file payload. Ignore input owner, group, and timestamp.

Why this case matters

An offline model of reproducible archive metadata, 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 2	`[["b", 0, 0, 100, 493, "b"], ["a", 0, 0, 100, 420, "a"]]`	`[["a", 0, 0, 100, 420, "a"], ["b", 0, 0, 100, 493, "b"]]`	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.