fix(release): repair build and quality gate drift

[backryun]

Summary

• Rebased emergency-fix onto release/v3.8.49 tip 91fd5f946, keeping current upstream behavior as the source of truth while resolving conflicts.
• Resolve the sql.js WASM asset through its public package entrypoint so Turbopack no longer tries the unexported sql.js/package.json subpath.
• Preserve boundary whitespace in streamed text deltas while suppressing the internal reasoning replay placeholder.
• Sanitize Muse Spark fetch failures without leaking paths, stack traces, or the redundant Error: prefix expected to be absent by the latest release regression contract.
• Reconcile inherited release-tip gate drift across complexity baselines, ESLint suppressions, environment docs, compression metadata, mutation coverage, dashboard typing, quota-reset expectations, and platform-independent fixtures.
• Derive credentialed Antigravity auto-combo expectations from the current registry and align provider-family tests with the upstream no-auth allowlist.
• Keep catalog and sidebar regression fixtures aligned with the current Qianfan URL and compression-exclusions navigation.

Root cause

This is the release emergency-fix branch: the latest upstream release tip is accepted first, then build and quality-gate failures that still reproduce on that clean tip are repaired around it.

The SQL.js warning came from resolving a package metadata subpath that the package export map does not expose. Resolving the public sql.js entrypoint is sufficient to locate the adjacent WASM asset and avoids the missing-private-subpath diagnostic.

The latest release tip also introduced additional inherited gate drift. A clean 91fd5f946 probe and this PR both measure 2159 cyclomatic/max-lines violations and 948 cognitive-complexity violations, so this PR contributes zero complexity growth. The baseline now records those exact measurements. The PR also removes two no-explicit-any occurrences from combo-routing-engine.test.ts, so its frozen suppression count is tightened from 271 to 269. GROK_AUTH_PATH, newly used by the release tip, is now represented in both .env.example and the environment reference.

Validation on 8c73aed19

• npm run build — passed; the private sql.js/package.json missing-subpath warning is absent.
• npm run lint:json -- --max-warnings 0 — passed.
• npm run typecheck:core — passed.
• npm run check:dashboard-typecheck — passed against the frozen dashboard baseline.
• npm run check:docs-all — passed.
• npm run check:complexity-ratchets — passed at 2159 / 948.
• Changed Node-runner regression set — 204/205 passed on the first run; the sole Muse Spark message-contract mismatch was fixed, then the affected file passed 7/7.
• npm run test:vitest -- tests/unit/autoCombo/provider-family-combos.test.ts — 11/11 passed.
• git diff --check — passed.

[gemini-code-assist]

Caution

The consumer version of Gemini Code Assist on GitHub has been sunset. All code review activity has officially ceased.

[gemini-code-assist]

Caution

The consumer version of Gemini Code Assist on GitHub has been sunset. All code review activity has officially ceased.

[backryun]

@diegosouzapw Errors are being logged so frequently that it’s practically flooding the logs. Since this is a patch to resolve the issue quickly, we request that you apply it as soon as possible.

[gemini-code-assist]

Caution

The consumer version of Gemini Code Assist on GitHub has been sunset. All code review activity has officially ceased.

[diegosouzapw]

Thanks, @backryun! 🙏 Closing this one — it overlaps an active base-red reconciliation campaign that's repairing the same build/quality-gate drift on release/v3.8.49 (e.g. the codex-responses ladder ranking is handled by #8256, plus the PROVIDER_BREAKER export / stryker / eslint-suppression drift by #8254-8259), and it also modifies complexity-baseline.json (which is release-captain territory — baselines get reconciled at release time, not per-PR). If any of your fixes here are unique and not covered by that campaign (e.g. the muse-spark-web error-helper or reasoningPlaceholder tweaks), a focused branch against the current tip would be very welcome and I'll fast-track it.