fix(providers): correct g4f.space gateway claims

[diegosouzapw]

Summary

• Corrects the public onboarding copy for all five g4f.space gateway entries. Anonymous access is conditional on proof-of-work cake credits from g4f.dev/chat; a g4f.dev member API key is the alternative, and limits are dynamic.
• Discloses that these are remote third-party gateways: prompts and request metadata leave OmniRoute. The service's Terms and Privacy links were unavailable at the 2026-08-27 UTC verification point.
• Updates all 43 shipped locale catalogs, the generated provider reference, registry comments, and the existing issue test. Adds a static regression test that locks the access paths, variable-limit wording, and remote data boundary.
• Keeps the integration itself unchanged: all five remain optional-auth OpenAI-compatible DefaultExecutor client configurations. This PR contains no copied/derived gpt4free implementation code.

Provider	Remote route	Corrected public contract
g4f-groq	https://g4f.space/api/groq/v1	Anonymous cake credits or member API key; limits vary; remote prompt boundary disclosed
g4f-gemini	https://g4f.space/api/gemini/v1	Anonymous cake credits or member API key; limits vary; remote prompt boundary disclosed
g4f-pollinations	https://g4f.space/api/pollinations/v1	Anonymous cake credits or member API key; limits vary; remote prompt boundary disclosed
g4f-ollama	https://g4f.space/api/ollama/v1	Anonymous cake credits or member API key; limits vary; remote prompt boundary disclosed
g4f-nvidia	https://g4f.space/api/nvidia/v1	Anonymous cake credits or member API key; limits vary; remote prompt boundary disclosed

Related Issues

• Related to feat(providers): add g4f.space no-key gateway (Groq/Ollama/Pollinations/NVIDIA/Gemini via gpt4free) #6650

Validation

Change type: provider metadata / i18n / docs.

• Focused TDD: real RED before implementation (2 tests, 0 passed, 2 failed), then GREEN after formatting (27 tests, 27 passed, 0 failed).
• node --import tsx/esm --test tests/unit/g4f-space-gateway-truthful-copy.test.ts tests/unit/g4f-space-gateway-6650.test.ts
• node --import tsx scripts/check/check-provider-consistency.ts — 270 registry entries, 352 canonical providers, 0 exceptions.
• npm run i18n:sync-ui:dry — 42 mirrors, no missing keys added.
• npm run i18n:check-ui-coverage — all 42 translated mirrors at 100%; English plus mirrors = 43 shipped catalogs.
• BASE_REF=091589089cd134a94df9f6cdab9ba562b2cefd18 npm run i18n:check-value-drift
• npm run i18n:check-glossary
• npm run check:docs-all
• npm run typecheck:core
• Targeted ESLint over all eight changed TypeScript files (--no-cache).
• Targeted markdownlint over the two changed Markdown files.
• npm run check:changelog-integrity
• node scripts/release/aggregate-changelog.mjs --dry-run — no files written.
• Global npm run lint:md is base-red: 2,013 pre-existing findings across 141 files; both Markdown files changed here pass targeted markdownlint.
• Global ESLint was held under extreme shared-host load after the exact changed TypeScript scope passed targeted ESLint. CI remains authoritative for the repository-wide lane.

The npm wrappers for provider consistency and provider-reference generation could not start because the shared base install is missing Bun's postinstall artifact. Their direct TypeScript entry points ran successfully; the reference regenerated with 352 providers.

Tests Added Or Updated

• Added tests/unit/g4f-space-gateway-truthful-copy.test.ts: checks all five metadata entries and every shipped locale.
• Updated tests/unit/g4f-space-gateway-6650.test.ts: removes stale no-key/free-tier language while retaining the existing registry, executor, aggregator, optional-auth, and metadata assertions.

Coverage Notes

The new test imports the real public provider catalog and reads the physical locale JSON files. It proves the user-facing contract changed without coupling to executor internals. No model seeds, provider removal, executor behavior, or request dispatch changed.

Reviewer Notes

• Branch was created independently from exact release SHA 091589089cd134a94df9f6cdab9ba562b2cefd18.
• No inference/generation POST was sent, no credentials were used, and no live user content was transmitted.
• Deliberately out of scope: model/seed refresh, provider retirement, THIRD_PARTY_NOTICES, upstream license disposition, merge, tag, or deployment.