[fabriziodemaria]

Summary

Adds a readOnly option to the JS OpenFeature local server provider (@spotify-confidence/openfeature-server-provider-local) that lets you resolve flag values without sending any data back to Confidence.

Previously there was no unified way to turn off apply/telemetry/logs together — only a per-evaluation _confidence_skip_apply context key that just suppressed apply for a single evaluation.

When readOnly: true, all three outbound side-effects are suppressed:

• Apply — resolve requests are forced to apply=false, and applyFlag() becomes a no-op.
• Telemetry — registerResolve() calls are skipped.
• Resolve/assignment logs — flush() / flushAssigned() still drain the WASM log buffers (to bound memory) but never POST to /v1/clientFlagLogs:write.

Flag values still resolve normally, so this is a true "read-only" preview mode that leaves experiment metrics unaffected.

const provider = createConfidenceServerProvider({
  flagClientSecret: process.env.CONFIDENCE_FLAG_CLIENT_SECRET!,
  readOnly: true, // resolve values only; no apply, logs, or telemetry
});

Changes

• ConfidenceServerProviderLocal.ts: new readOnly?: boolean option; gates apply, telemetry, and log sending.
• ConfidenceServerProviderLocal.read-only.test.ts: new tests asserting zero egress in read-only mode, applyFlag no-op, and a sanity check that logs still send when disabled.
• README.md / CLAUDE.md (AGENTS.md): documented the option.

Test plan

• make test (WASM build + install + proto:gen + format:check + typecheck + vitest): 164/164 non-e2e tests pass.
• New read-only suite passes (3/3).
• Note: flaglogs.test.ts requires a live CONFIDENCE_CLIENT_SECRET + network and is unaffected by this change.

Made with Cursor