✅ No new issues found.

Reviewed changes — adds a deployBilling feature flag (default off, gating the Unkey Deploy billing UI until GA) plus a local dev escape hatch that resolves all flags on without a Vercel Flags setup.

• Add deployBilling flag — new flag<boolean, Entities> in lib/flags/index.ts keyed deploy-billing, defaultValue: false; mirrors the existing helloWorld shape exactly.
• Local always-on adapter — adapter<T>() in lib/flags/plumbing.ts short-circuits to decide: () => true as T when FLAGS_LOCAL_ALL_ON === "true", checked before the vercel-adapter try/catch.
• Register in resolveAll — lib/flags/resolve.ts adds deployBilling to the resolved set so the Flags type and FlagsProvider expose it to client components.
• Document env var — .env.example documents FLAGS_LOCAL_ALL_ON as a dev-only convenience.

The change is consistent with the established flag-registry pattern, the defaultValue: false is correct for a GA-gated flag, and the true as T shortcut is sound while all flags remain booleans (the comment documents that assumption). Reading FLAGS_LOCAL_ALL_ON via process.env directly rather than the env.ts zod schema matches the existing flags-plumbing convention.

  ^{｜ View workflow run ｜ Using Claude Opus ｜ 𝕏}

✅ No new issues found.

Reviewed changes — since the prior pullfrog review the all-on local escape hatch was replaced with an explicit per-flag override list, directly addressing @chronark's predictability concern on plumbing.ts.

• Replaced FLAGS_LOCAL_ALL_ON with FLAGS_LOCAL_OVERRIDES — plumbing.ts now parses a comma-separated list of flag keys into a Set and forces only those keys on, instead of resolving every flag to true. The override layer wraps the base adapter ({ ...base, decide }) and falls through to base.decide for non-listed keys, so per-flag prod defaults stay honest.
• Override applied after adapter construction — the override no longer short-circuits before the vercel-adapter try/catch; it composes over whichever base adapter (vercel or noop fallback) was built, and a console.warn was added on the fallback path.
• Updated .env.example — documents FLAGS_LOCAL_OVERRIDES with a worked example, replacing the old FLAGS_LOCAL_ALL_ON block.

The new shape is sound: localOverrides is read once at module load (acceptable for a dev-only hatch, matching the prior convention), the true as T cast remains valid while all flags are boolean (documented), and delegating to base.decide for unlisted keys keeps non-overridden flags evaluating normally. This is strictly more predictable than the previous all-on behavior. The deployBilling flag definition and resolveAll registration are unchanged from the prior review.

  ^{｜ View workflow run ｜ Using Claude Opus ｜ 𝕏}

you go figure it out with oz :D