Skip to content

fix(providers): separate MaxAI and UC credential contracts - #12431

Merged
diegosouzapw merged 3 commits into
release/v3.8.51from
fix/v3851-web-session-credentials-syntax
Sep 3, 2026
Merged

diegosouzapw merged 3 commits into
release/v3.8.51from
fix/v3851-web-session-credentials-syntax

Conversation

@diegosouzapw

@diegosouzapw diegosouzapw commented Sep 2, 2026 •

Copy link
Copy Markdown
Owner

Status

OWN SCOPE: PASS · RECONCILED · CI: PASS

The branch is reconciled with the current release/v3.8.51 tip. The production repair is already present on the live base; this PR now contributes only the regression test that keeps the MaxAI and UC credential contracts independent.

Summary

The malformed MaxAI credential entry originally left maxai.storageKeys open before the uc property. TypeScript then parsed UC inside the preceding array/object and emitted 11 syntax diagnostics.

The release branch now contains the production repair. This PR preserves the missing regression guard: MaxAI and UC must remain separate top-level entries with independent storage keys and credential metadata.

Final candidate delta

Item Result
Current base bf0d902dfc5369bd025f64808d96fe6cb473ea75
Candidate c422dd4fced77fe3869491bddfeb6fc00119cce9
Merge result PASS: clean merge, no conflict
Candidate vs current base PASS: tests/unit/web-session-credentials.test.ts only, +27 lines
Production source PASS: candidate and base use the identical src/shared/providers/webSessionCredentials.ts blob (20548eda56f2c333e11775dd4a8638d257a1e81a)
Material overlap None; only the regression test remains unique to this PR

Validation

Check Result Evidence
Focused web-session credential suite PASS 5/5, 0 failures
Related credential/session suites PASS 306/306, 0 failures on the reconciled candidate
Core TypeScript PASS npm run typecheck:core
API-route typecheck gate PASS 289 pre-existing diagnostics, all inside the frozen baseline; 0 new
Owned-file ESLint PASS npx eslint tests/unit/web-session-credentials.test.ts
Owned-file Prettier PASS npx prettier --check tests/unit/web-session-credentials.test.ts
Patch integrity PASS git diff --check origin/release/v3.8.51..HEAD
Review conversations PASS no review threads are open
GitHub checks PASS 9 successful, 0 failed, 0 pending; 7 skipped and 2 neutral are not reported as passes

Base-red attribution

The release line has a separately verified BASE-RED for the official full-repository lint at exact base 6da2418247d75acd0af3a617c7289b004b5a86f5: orphaned entries in config/quality/eslint-suppressions.json. This PR neither edits production code nor changes the suppression inventory, and the owned test file passes ESLint. The fresh GitHub checks against the current base above are green.

Draft only. No merge, automerge, deploy, or release action requested.

@diegosouzapw
diegosouzapw marked this pull request as ready for review September 3, 2026 23:56
@diegosouzapw
diegosouzapw merged commit 239d8fc into release/v3.8.51 Sep 3, 2026
21 checks passed
muhamadgalihsaputra pushed a commit to niyatna/NiyatnaRoute that referenced this pull request Sep 27, 2026
…apw#12431)

Validado em lote numa worktree combinada com os 14 PRs desta campanha de error-boundary sobre o tip de `release/v3.8.51`: `typecheck:core` limpo e **120/120** nos 23 arquivos de teste que os PRs trazem.

Um ponto que só apareceu no tree combinado: **diegosouzapw#12465 e diegosouzapw#12466 criam o mesmo arquivo novo** `open-sse/utils/streamReadiness.ts` (que não existe no tip) com desenhos divergentes de cancelamento — `cancelled` + `releaseLock` imediato num, `readInFlight`/`cancelRequested` com `cancelReader` fire-and-forget no outro. Adotei a versão do diegosouzapw#12466, que difere e defere o release do lock para quando a leitura em voo termina, e validei a escolha rodando as suítes dos **dois** PRs contra ela: 21/21 no readiness compartilhado e 22/22 incluindo o boundary do Perplexity.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant