Send OpenRouter's zero-retention flags with Jev requests once Rig supports them #69

What

Jev requests go to OpenRouter's /systemone without provider: {zdr: true, data_collection: "deny"}, because Rig 0.45's JevConfig can't send that object. This is a temporary exception to "Choose the first source input and outbound consent contract" (#3). It's recorded on "Choose how to depend on Rig until Jev works in a release" (#8) and in ADR 0001.

Generator requests are unaffected. They carry the flags through Rig's OpenRouter provider.

Why it's acceptable for now

• TypeSafe is the only provider serving Jev on OpenRouter.
• Both Jev endpoints, typesafe/jev-1.13-20260917 and typesafe/jev-1.14-20261014, are on OpenRouter's zero-retention list. Their data policy is no training and no prompt retention (jev-1.14 endpoints, checked 20 October 2026).
• The outbound review's statement "OpenRouter routes only to endpoints it lists as not keeping prompts" therefore stays true for Jev. It just isn't enforced.

What's lost until this lands: refusal on change. If TypeSafe began keeping prompts, or OpenRouter added a provider that does, Jev requests would still be sent.

When

When a Rig release includes JevConfig::provider, requested in 0xPlaygrounds/rig#2871. Wait for a release. Don't pin a Rig git revision or a fork commit to get it sooner.

Done when

• Rig is upgraded on purpose (it's pinned exactly) to the release with JevConfig::provider.
• Every Jev request sets ProviderPreferences::new().zdr(true).data_collection(DataCollection::Deny).
• The offline recorded-reply tests check that the provider object is in every Jev request. The keyed e2e job sends it live.
• The exception is removed from ADR 0001.