[ORESoftware]

Executes follow-up hardening tracked in zed-pkg-test/zed-pkg-e2e#190 and #191 against the exact zed-cli#388 candidate f3123ebebadaede30da97a31a586288c3b15609d.

The workflow:

• runs the focused GitHub REST degradation, smart-HTTP recovery, and GitHub-before-R2 source-order contracts;
• starts four clean-home five-ecosystem installs concurrently with the Zed control plane and R2 unavailable, then requires deterministic identical lockfiles and successful materialization in every process;
• exercises an actually missing package with registry/R2 unavailable and requires a deterministic product failure before a 60-second outer bound;
• clears ambient GitHub credentials and retains only sanitized logs/locks.

This does not claim full request-count deduplication yet; #191 remains open for the single-process repeated-node harness once the typed transport cache from zed-clients#83 is wired into live fallback.

[linear-code]

DEN-388