FA-9477 / Dependency resolution / Member archive

Peer dependency diagnostics: Diagnostics lose the failing package identity · case 02

Diagnostics lose the failing package identity.

Member previewVariant 2 · 3 implementations · 8 checks per implementation

Case contract

For each peer in declaration order, ignore missing optional peers, report missing required peers, report too-old installed peers, report too-new peers, and accept inclusive lower/exclusive upper versions.

Why this case matters

An offline model of peer dependency diagnostics, 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 4	`[["peer", "low"]]`	`[["a", "low"]]`	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.