fix(hooks): follow-up exhaustive-deps fixes + useSipConnection duplicate body

[adm01-debug]

Descrição

Follow-up to merged PR #584. Resolves 9 remaining react-hooks/exhaustive-deps violations that were missed in the original batches, plus removes a build-breaking duplicate function body in useSipConnection.ts left by the merge conflict resolution.

Tipo de mudança

• fix: Correção de bug

Alterações

useSipConnection.ts — build-breaking duplicate body

The merge conflict resolution for PR #584 left the connect useCallback with its try/catch body duplicated: HEAD's complete try/catch remained, then main's try body was appended as dead code followed by an orphaned catch with no matching try. esbuild failed with Expected ")" but found "catch". Removed the 58 dead-code lines.

useAudioRecorder.ts — 3 fixes

• useEffect (unmount cleanup): added cleanupRecordingResources to deps array (it is a useCallback with [] deps — stable, but ESLint requires it declared)
• cancelRecording: added setBlobUrl to deps (called at line 351; setBlobUrl is a useCallback with [] deps)
• restoreRecording: added setBlobUrl to deps (called at line 359)

useAudioManagement.ts — 3 fixes

• startRecording: added setBlobUrl to [maxDuration, onRecordingComplete] (called at line 854)
• cancelRecording: added setBlobUrl to [isRecording, isPaused, transcription] (called at line 1072)
• restoreRecording: added setBlobUrl to [onRecordingComplete] (called at line 1081)

useChatMediaSending.ts — 3 fixes

• handleSendSticker, handleSendCustomEmoji, handleSendAudioMeme: removed contactPhone from all three dep arrays. contactPhone is not referenced directly in these callbacks — it is captured by getSafePhone (already in the dep array), which closes over contactPhone via its own [contactPhone] dep.

Checklist de qualidade

Para todo PR

• Título segue Conventional Commits (tipo: descrição em minúsculas)
• PR aborda um único tema
• Build local passando (bun run build → ✓ built in 1m 57s)
• TypeScript sem novos erros (tsc --noEmit --skipLibCheck → 0 erros)

Para PRs com fix:

• OBRIGATÓRIO: Inclui ao menos um teste de regressão que falha sem a correção

Testes relacionados

None added. The changes are dep-array corrections — adding stable useCallback refs that ESLint requires declared. Adding them does not change runtime behavior (stable identity means no extra re-registrations). The build + typecheck serve as the primary validation gate.

Notas para o revisor

• setBlobUrl in both audio hooks is a useCallback(() => {...}, []) — its identity never changes, so adding it to dep arrays is semantically a no-op at runtime but required by ESLint for correctness.
• Removing contactPhone from the three media-sending callbacks is safe: the rule flags it as unnecessary because none of those callbacks reference contactPhone directly in their bodies; getSafePhone (already in deps) handles the capture.

---

Generated by Claude Code

---

Summary by cubic

Fixes a build failure in useSipConnection, completes the react-hooks/exhaustive-deps audit across the app, restores CI workflows so required checks run reliably, and reconciles with main while keeping our hook fixes; also bumps a few dependencies and restores a corrupted audio player component.

• Bug Fixes

  • useSipConnection: removed duplicated connect try/catch body and centralized reconnect limits; teardown no longer triggers auto-reconnect.
  • Completed remaining react-hooks/exhaustive-deps fixes across hooks/components; resolved merge with main without losing these corrections.
  • CI workflows: fixed invalid YAML/quoting and updated actions in .github/workflows/ci-gate.yml, pr-size-gate.yml, fix-schema-refs.yml, and ts-nocheck-ratchet.yml to restore the “ci” status gate and other checks.
  • AudioMessagePlayer: restored the file from corrupted content and added unsubscribe-before-remove cleanup to prevent Realtime leaks.

• Refactors

  • Dependencies: bumped @sentry/react to 10.68.0, web-vitals to 6.0.1, and @commitlint/* to 21.x; synced bun.lock; restructured src/components/ui/registry.json (no functional changes).
  • Merge alignment: adopted main’s canonical updates in several areas (e.g., explicit filter args, SpeechRecognition lang, userAgent browser field) while retaining this branch’s type-safety and lint cleanup.

^{Written for commit a13acb7. Summary will update on new commits.}

Summary by CodeRabbit

• Novos recursos

  • O modo de movimento reduzido agora é respeitado em animações e partículas.
  • Reconexões de chamadas SIP passam a ser limitadas e interrompidas corretamente ao desconectar manualmente.
  • Rascunhos de mensagens são restaurados com maior precisão, sem sobrescrever texto digitado.

• Correções

  • Melhorias na atualização de conversas, buscas, notificações, integrações, relatórios e dados do catálogo.
  • Verificações de autenticação multifator e carregamentos assíncronos ficaram mais consistentes.
  • O CI agora valida tipos, testes, cobertura, build e tamanho das alterações sem bloquear por tamanho de PR.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
zapp-web-v3	Error		Jul 27, 2026 7:42pm

[coderabbitai]

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 32 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 957d0933-52c8-441d-aae7-0f0e544d65a3

📥 Commits

Reviewing files that changed from the base of the PR and between cf6dd32 and a13acb7.

📒 Files selected for processing (3)

• src/features/inbox/components/AudioMessagePlayer.tsx
• src/features/inbox/hooks/useChatMediaSending.ts
• src/hooks/useAudioManagement.ts

Walkthrough

A PR reconstrói workflows de CI, ajusta dependências de hooks React, reduz usos de any, tipa integrações Supabase e corrige referências potencialmente obsoletas em fluxos de catálogo, inbox, áudio, autenticação e administração.

Changes

Governança e validação

Layer / File(s)	Summary
Workflows e gates .github/workflows/*, .gitignore	Workflows de CI, tamanho de PR, schema e @ts-nocheck foram normalizados, com verificações de lockfile, TypeScript, Supabase, testes, build, labels e comentários rastreados.
Ciclos de vida dos componentes src/components/*, src/features/admin/*, src/features/auth/*	Callbacks, refs e dependências de efeitos foram ajustados em componentes de catálogo, conexões, relatórios, segurança, temas, chat e administração.
Inbox, áudio e realtime src/features/inbox/*, src/hooks/*	Fluxos de busca, filas, uploads, mensagens, gravação, SIP, presença e sincronização passaram a usar referências atuais, callbacks memoizadas e cleanups explícitos.
Contratos e acesso a dados src/integrations/*, src/services/*, src/shared/*, src/lib/*, src/pages/*	Tipos genéricos e estruturas Supabase foram refinados, RPCs dinâmicos receberam shapes internos e contratos públicos trocaram any por unknown ou tipos específicos.

Estimated code review effort: 5 (Critical) | ~120 minutes

Possibly related PRs

• adm01-debug/zapp-web-v3#548: Atualiza o mesmo workflow .github/workflows/ci-gate.yml.
• adm01-debug/zapp-web-v3#550: Implementa mudanças relacionadas ao workflow de tamanho de PR.
• adm01-debug/zapp-web-v3#584: Sobrepõe refatorações de hooks e remoção de supressões de dependências.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	Docstring coverage is 84.21% which is sufficient. The required threshold is 80.00%.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	O título resume bem os fixes de exhaustive-deps e a remoção do corpo duplicado em useSipConnection, que são mudanças centrais do PR.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch claude/zapp-web-v3-audit-74uxvx

---

_{Comment @coderabbitai help to get the list of available commands.}

[ecc-tools]

ECC bundle files are already tracked in this repository. Skipping generation of another bundle PR.

[ecc-tools]

ECC bundle files are already tracked in this repository. Skipping generation of another bundle PR.

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

[ecc-tools]

ECC bundle files are already tracked in this repository. Skipping generation of another bundle PR.

[coderabbitai]

Actionable comments posted: 20

Note

Due to the large number of review comments, Critical, Major severity comments were prioritized as inline comments.

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (16)

src/components/monitoring/MonitoringWebhookPanel.tsx (1)

48-63: 🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win

Valide o retorno antes de chamar setSecretStatus(...). data as SecretStatus não faz validação em runtime; se a Edge Function devolver um payload fora do contrato, a UI pode ficar inconsistente ou quebrar ao ler checkedAt, length ou hashPrefix.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@src/components/monitoring/MonitoringWebhookPanel.tsx` around lines 48 - 63,
Validate the payload returned by supabase.functions.invoke in loadSecretStatus
before calling setSecretStatus, ensuring it matches the SecretStatus shape and
safely includes checkedAt, length, and hashPrefix. Treat invalid data as an
error through the existing catch/toast flow, and remove the unchecked cast.

Source: Path instructions

src/components/effects/EasterEggs.tsx (1)

228-255: 🩺 Stability & Availability | 🟠 Major | ⚡ Quick win

Cancele a instalação assíncrona do listener. Se navigator.permissions.query resolver depois que o efeito desmontar, o cleanup já passou e devicemotion pode ficar registrado sem remoção. Adicione um flag de descarte antes de chamar addEventListener.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@src/components/effects/EasterEggs.tsx` around lines 228 - 255, Update the
effect containing setupListener and its cleanup to track a disposed/cancelled
flag, set it during cleanup, and check it after the asynchronous permission
query resolves before calling addEventListener. Ensure listenerAdded is only set
when the listener is actually registered, preventing late registration after
unmount.

src/features/admin/hooks/useAdminManagement.ts (1)

817-840: 🚀 Performance & Scalability | 🟠 Major | ⚡ Quick win

Evite a recarga em loop no diálogo de roles. roleUsers ?? [] cria um array novo enquanto roleUsers ainda está indefinido; com showAddRoleDialog aberto, isso troca a identidade de fetchAvailableRoleUsers a cada render e o useEffect dispara novas consultas até a query preencher. Use um fallback estável (EMPTY_ROLE_USERS/useMemo) e remova roleUsersList das dependências do efeito se ele só serve para o filtro interno.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@src/features/admin/hooks/useAdminManagement.ts` around lines 817 - 840,
Estabilize o fallback usado por roleUsersList quando roleUsers estiver
indefinido, usando EMPTY_ROLE_USERS ou useMemo, para que fetchAvailableRoleUsers
não seja recriada a cada render. Como roleUsersList é utilizado apenas no filtro
interno de fetchAvailableRoleUsers, remova-o das dependências de useEffect e
mantenha o efeito dependente somente de showAddRoleDialog e da callback estável.

src/hooks/useAutomationSuggestions.ts (1)

144-148: 🗄️ Data Integrity & Integration | 🟠 Major | ⚡ Quick win

Só grave applied_tags depois de checar o retorno da RPC. rpc_upsert_contact pode falhar sem interromper esse fluxo; hoje a função ainda persiste a tag local e mostra sucesso mesmo com erro externo ou sem externalClient, deixando a auditoria inconsistente com o contato.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@src/hooks/useAutomationSuggestions.ts` around lines 144 - 148, In the
automation suggestion flow around rpc_upsert_contact, only persist applied_tags
and show success after confirming externalClient exists and the RPC returns
successfully. Handle RPC errors or a missing client by stopping the local update
and success notification, keeping the audit consistent with the external
contact.

src/components/connections/IntegrationsPanel.tsx (1)

50-92: 🩺 Stability & Availability | 🟠 Major | ⚡ Quick win

O cleanup não aborta as requisições em andamento.

Ao fechar o diálogo, apenas cancelled muda. O AbortController só é abortado no finally, que roda depois de Promise.allSettled; logo, as seis requisições continuam consumindo rede. Crie o controller no efeito e aborte-o diretamente no cleanup.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@src/components/connections/IntegrationsPanel.tsx` around lines 50 - 92, Move
AbortController ownership from loadAll into the useEffect: create the controller
there, pass its signal through loadAll to each getter, and call abort() in the
effect cleanup alongside setting cancelled. Remove the delayed finally-based
abort so closing the dialog immediately cancels all in-flight requests.

src/components/dashboard/FloatingParticles.tsx (1)

19-30: 🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win

A redução de movimento ainda mantém animações infinitas ativas.

Quando prefersReducedMotion é verdadeiro, apenas as partículas são removidas; os quatro orbes abaixo continuam animando com repeat: Infinity. Condicione também esses animate/transition à preferência reduzida.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@src/components/dashboard/FloatingParticles.tsx` around lines 19 - 30,
Atualize as animações dos quatro orbes no componente FloatingParticles para
respeitarem prefersReducedMotion, desativando os valores animate e as transições
com repeat: Infinity quando essa preferência estiver ativa. Preserve as
animações atuais quando prefersReducedMotion for falso.

src/components/reports/AbandonmentRate.tsx (1)

20-48: 🩺 Stability & Availability | 🟠 Major | ⚡ Quick win

Tratem rejeições e sempre encerrem o loading.

Esses loaders disparam Promises sem recuperação. Uma falha de rede ou exceção deixa o componente em skeleton/loading e pode gerar rejeição não tratada. Adicionem try/catch/finally dentro de cada loader; no catch, preservem um estado consistente e exibam/registram a falha.

• src/components/reports/AbandonmentRate.tsx#L20-L48: envolver fetchAbandonmentRateMessages com try/catch/finally.
• src/components/reports/ConversationHeatmap.tsx#L28-L56: envolver fetchContactMessagesForHeatmap com try/catch/finally.
• src/components/reports/DemandForecast.tsx#L29-L82: garantir setLoading(false) no finally.
• src/components/reports/PeriodComparison.tsx#L31-L82: tratar falhas de ambas as consultas e finalizar o loading.
• src/features/inbox/components/LeadRiskScorePanel.tsx#L42-L63: tratar falhas da consulta e marcar o painel como carregado no finally.

As per path instructions, “Promises sem await ou .catch()” devem ser verificadas.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@src/components/reports/AbandonmentRate.tsx` around lines 20 - 48, Ensure all
listed loaders handle rejected requests and always clear loading state: in
src/components/reports/AbandonmentRate.tsx lines 20-48, wrap loadData’s
fetchAbandonmentRateMessages flow in try/catch/finally, preserving consistent
state and logging or displaying errors; apply the same to
fetchContactMessagesForHeatmap in src/components/reports/ConversationHeatmap.tsx
lines 28-56; guarantee setLoading(false) in finally for DemandForecast.tsx lines
29-82; handle both queries and finalize loading in PeriodComparison.tsx lines
31-82; and handle the query failure while marking the panel loaded in finally in
LeadRiskScorePanel.tsx lines 42-63. Verify each effect invocation does not leave
an unhandled promise rejection.

Source: Path instructions

src/hooks/useEmail.ts (1)

55-62: 🎯 Functional Correctness | 🟠 Major | ⚡ Quick win

Normalize message_count antes do Math.max
row está tipado como Record<string, unknown>, então row.message_count ?? 1 continua sem narrowing e não entra em Math.max. Converta esse campo para número antes de calcular unread_count (como já feito em useEmailManagement.ts).

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@src/hooks/useEmail.ts` around lines 55 - 62, Normalize row.message_count to a
numeric value before passing it to Math.max in mapBaseThreadRow, matching the
existing conversion used in useEmailManagement.ts. Preserve the current fallback
to 1 and unread_count behavior for read threads.

Source: Path instructions

src/features/inbox/components/ConversationHistory.tsx (1)

82-172: 🔒 Security & Privacy | 🟠 Major | ⚡ Quick win

Evite sobrescrita por respostas antigas

• Uma requisição anterior pode concluir depois da atual e sobrescrever conversations/isLoading com dados do contexto errado. Use requestId, AbortController ou uma flag de cancelamento antes de chamar setConversations/setIsLoading.
• contactPhone não é usado na query; tire-o das dependências para evitar refetch desnecessário.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@src/features/inbox/components/ConversationHistory.tsx` around lines 82 - 172,
The fetchConversationHistory callback must ignore stale requests before updating
conversations or isLoading; add request cancellation or a request ID/active flag
and guard every relevant state update, including early returns and finally, so
only the latest invocation affects state. Remove unused contactPhone from the
callback dependency array since it is not used by the query.

src/hooks/useAutomations.ts (1)

99-116: 🎯 Functional Correctness | 🟠 Major | 🏗️ Heavy lift

Use a RPC tipada aqui, não SupabaseClient<any>

Hoje o código só garante que msgs é um array, mas ainda assume message_timestamp, from_me e content sem validação. Se a RPC devolver uma linha fora do contrato, a ordenação pode virar NaN e as automações tomar decisões erradas. Use o helper tipado da RPC ou valide cada item antes de processar.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@src/hooks/useAutomations.ts` around lines 99 - 116, Update the RPC call in
the automation flow around typedClient and rpc('rpc_list_messages') to use the
project’s typed RPC helper and its declared message-row contract instead of
SupabaseClient<any>. Ensure returned rows are validated for message_timestamp,
from_me, and content before sorting or selecting last, rejecting or excluding
invalid rows so sorting never receives invalid timestamps.

Source: Path instructions

src/features/inbox/components/ConversationSummary.tsx (1)

115-120: 🎯 Functional Correctness | 🟠 Major | ⚡ Quick win

Não use hasGenerated como gatilho direto desse reset.

Após gerar o resumo, setHasGenerated(true) executa este efeito, que imediatamente limpa summary e volta o estado para false. O resumo recém-gerado desaparece. Detecte a mudança dos filtros com um useRef ou outra comparação anterior, mantendo hasGenerated apenas como condição.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@src/features/inbox/components/ConversationSummary.tsx` around lines 115 -
120, Atualize o useEffect associado a analysisPeriod, customDateFrom e
customDateTo para detectar mudanças reais nos filtros usando useRef ou
comparação com os valores anteriores, sem usar hasGenerated como gatilho.
Mantenha hasGenerated apenas como condição antes de limpar summary e
redefini-lo, garantindo que setHasGenerated(true) após a geração não apague o
resumo recém-criado.

src/hooks/useVoiceManagement.ts (1)

39-46: 🔒 Security & Privacy | 🟠 Major | ⚡ Quick win

Interrompa o SpeechRecognition no unmount.
O cleanup só marca mountedRef como falso; a instância pode continuar ativa após o componente desmontar, mantendo o microfone e recursos do navegador ocupados. Chame stop() no cleanup e limpe recognitionRef.current.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@src/hooks/useVoiceManagement.ts` around lines 39 - 46, Atualize o cleanup do
useEffect em useVoiceManagement para interromper a instância ativa de
SpeechRecognition antes de desmontar. Chame stop() quando recognitionRef.current
existir e, em seguida, defina recognitionRef.current como null, preservando
também a atualização de mountedRef.current para false.

src/hooks/connections/useHubTabNavigation.ts (1)

9-42: 📐 Maintainability & Code Quality | 🟠 Major | ⚡ Quick win

Lógica de validação/sincronização de aba duplicada entre dois hooks. useHubTabNavigation e useHubTabNavigationManagement implementam exatamente a mesma validação de HubTab e os mesmos dois efeitos de sincronização com searchParams — esta própria PR precisou aplicar o mesmo fix de useCallback/deps duas vezes.

• src/hooks/connections/useHubTabNavigation.ts#L9-L42: manter como implementação canônica desta lógica.
• src/hooks/connections/useConnectionsManagement.ts#L39-L80: substituir useHubTabNavigationManagement por uma chamada a useHubTabNavigation(isDev) (ou extrair ambos para um hook compartilhado), eliminando a duplicação de validateTab e dos dois useEffect.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@src/hooks/connections/useHubTabNavigation.ts` around lines 9 - 42, The tab
validation and URL synchronization logic is duplicated across two hooks. Keep
useHubTabNavigation in src/hooks/connections/useHubTabNavigation.ts:9-42 as the
canonical implementation; in
src/hooks/connections/useConnectionsManagement.ts:39-80, replace
useHubTabNavigationManagement with a call to useHubTabNavigation(isDev),
removing its duplicate validateTab and synchronization effects.

src/hooks/useAudioRecorder.ts (2)

24-43: 📐 Maintainability & Code Quality | 🟠 Major | 🏗️ Heavy lift

Duas implementações completas de useAudioRecorder mantidas em paralelo. src/hooks/useAudioRecorder.ts e src/hooks/useAudioManagement.ts exportam cada um sua própria versão de useAudioRecorder, com a mesma lógica de MediaRecorder/AudioContext/SpeechRecognition/stopRecordingRef. Esta PR precisou replicar o mesmo fix (stopRecordingRef, deps de setBlobUrl) nos dois arquivos, confirmando o risco de divergência futura.

• src/hooks/useAudioRecorder.ts#L24-L43: candidata a implementação canônica (após corrigir o TDZ de cleanupRecordingResources apontado no arquivo).
• src/hooks/useAudioManagement.ts#L781-L781: avaliar remoção do useAudioRecorder local em favor de importar a implementação de src/hooks/useAudioRecorder.ts, confirmando antes quais consumidores usam qual versão.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@src/hooks/useAudioRecorder.ts` around lines 24 - 43, Use
src/hooks/useAudioRecorder.ts:24-43 as the canonical useAudioRecorder
implementation, moving cleanupRecordingResources before the useEffect that
references it to eliminate the temporal dead zone. In
src/hooks/useAudioManagement.ts:781-781, inspect consumers and remove the local
useAudioRecorder implementation where compatible, importing the canonical hook
instead; preserve any version-specific behavior only if consumers require it.

---

24-43: 🩺 Stability & Availability | 🔴 Critical | ⚡ Quick win

TDZ em cleanupRecordingResources quebra a montagem do hook src/hooks/useAudioRecorder.ts:25-43 — o array de dependências de useEffect avalia cleanupRecordingResources antes do const ser inicializado, disparando ReferenceError em runtime. Mova cleanupRecordingResources para antes do efeito.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@src/hooks/useAudioRecorder.ts` around lines 24 - 43, Move the
cleanupRecordingResources useCallback definition before the useEffect that
references it in its dependency array. Preserve its existing cleanup behavior
and keep the mountedRef lifecycle effect unchanged aside from resolving this
initialization order.

src/features/inbox/components/useAudioRecorderUI.ts (1)

159-163: 🩺 Stability & Availability | 🔴 Critical | ⚡ Quick win

Efeito de auto-start reinicia a gravação a cada render.

onRecordingComplete é uma closure inline aqui, então startRecording muda em todo render; cancelRecording também muda quando isRecording/isPaused/transcription atualizam. Com essas deps, o useEffect faz cleanup + setup de novo em cada re-render, cancelando e reiniciando o microfone repetidamente. Mantenha esse efeito estável para rodar só no mount.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@src/features/inbox/components/useAudioRecorderUI.ts` around lines 159 - 163,
Estabilize o efeito de auto-start em useAudioRecorderUI para executar apenas na
montagem, evitando que as mudanças de startRecording ou cancelRecording causem
cleanup e reinício da gravação a cada render. Preserve o cancelamento no unmount
e ajuste as dependências conforme necessário para manter esse comportamento.

🟡 Minor comments (16)

src/pages/admin/email/useEmailHealthStatus.ts-66-83 (1)

66-83: 🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win

Valide o payload da Edge Function antes de consumi-lo.

Response.json() entra como dado não confiável e os campos aninhados são acessados sem narrowing. Uma resposta 2xx malformada pode gravar failuresData inválido e quebrar consumidores posteriores. Valide o shape antes de atualizar o estado.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@src/pages/admin/email/useEmailHealthStatus.ts` around lines 66 - 83, Validate
the parsed payload from fetchResponse.json() before using it in the health and
failures state updates. Add a type/shape guard for the expected status, source,
validation timestamp, failure count, and failuresResult.items/total fields, and
reject malformed 2xx responses before setHealth or setFailuresData; preserve the
existing error handling for non-OK responses.

Source: Path instructions

src/pages/admin/AdminDevDiagnosticsPage.tsx-28-40 (1)

28-40: 🔒 Security & Privacy | 🟡 Minor | ⚡ Quick win

Trate o { error } do insert da auditoria. O await já existe; o problema é ignorar o retorno de safeClient.from(...), então a falha pode passar em silêncio e o acesso ficar sem registro.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@src/pages/admin/AdminDevDiagnosticsPage.tsx` around lines 28 - 40, Atualize a
função logAccess para capturar o retorno de safeClient.from(...) no insert de
dev_diagnostic_logs e verificar sua propriedade error. Quando houver falha,
trate-a explicitamente conforme o padrão de tratamento de erros já usado no
módulo, sem ignorar o resultado da auditoria.

.github/workflows/pr-size-gate.yml-137-143 (1)

137-143: 🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win

Busca de comentário existente não pagina — pode duplicar em PRs com muitos comentários.

listComments retorna só a primeira página (padrão 30 itens). Em PRs bem discutidos, o comentário com o marcador <!-- pr-size-gate --> pode estar fora dessa página, e o bot cria um comentário duplicado em vez de atualizar o existente.

♻️ Fix sugerido (usar paginate)

-              const { data: comments } = await github.rest.issues.listComments({
-                owner: context.repo.owner,
-                repo: context.repo.repo,
-                issue_number: context.issue.number
-              });
+              const comments = await github.paginate(github.rest.issues.listComments, {
+                owner: context.repo.owner,
+                repo: context.repo.repo,
+                issue_number: context.issue.number
+              });

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In @.github/workflows/pr-size-gate.yml around lines 137 - 143, Atualize a busca
em torno de `github.rest.issues.listComments` e `comments.find` para usar a API
paginada (`github.paginate` ou equivalente), garantindo que todos os comentários
da issue sejam carregados antes de procurar pelo `MARKER`; preserve a lógica
existente de localizar o comentário e atualizar ou criar conforme o resultado.

src/services/api/genericService.ts-63-65 (1)

63-65: 🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win

Faça narrowing real de min e max antes de montar a faixa.

as Record<string, unknown> e 'min' in rangeVal só garantem a chave; gte/lte ainda pode receber objeto/array e gerar filtro inválido em runtime. Valide min/max como escalares antes de aplicar o range.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@src/services/api/genericService.ts` around lines 63 - 65, Update the range
handling around rangeVal so min and max are narrowed to valid scalar values
before calling query.gte and query.lte. Do not rely solely on the Record cast or
key existence checks; reject objects and arrays, and apply each bound only when
its value passes scalar validation.

Source: Path instructions

src/components/monitoring/MonitoringWebhookPanel.tsx-278-279 (1)

278-279: 🩺 Stability & Availability | 🟡 Minor | ⚡ Quick win

Trate as rejeições dessas Promises

• src/components/monitoring/MonitoringWebhookPanel.tsx#L69-L70 e #L278-L279: navigator.clipboard.writeText() pode rejeitar; o handler hoje ignora essa falha.
• src/components/monitoring/RetryMetricsPanel.tsx#L206-L207, #L284-L290 e #L417-L418: mesmo problema em copy() e refetch().

Use async/await com try/catch ou void ...catch(...) nesses handlers.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@src/components/monitoring/MonitoringWebhookPanel.tsx` around lines 278 - 279,
Trate explicitamente as rejeições das Promises nos handlers de cópia e
atualização: em src/components/monitoring/MonitoringWebhookPanel.tsx, nos
trechos 69-70 e 278-279, capture a rejeição de navigator.clipboard.writeText();
em src/components/monitoring/RetryMetricsPanel.tsx, nos trechos 206-207 e
417-418, trate a Promise de copy(), e no trecho 284-290, trate a Promise de
refetch(). Use async/await com try/catch ou void com catch() em cada handler,
sem deixar essas rejeições serem ignoradas.

Source: Path instructions

src/components/ai/AutoTicketClassifier.tsx-127-134 (1)

127-134: 🩺 Stability & Availability | 🟡 Minor | ⚡ Quick win

Restaurar isMountedRef antes de carregar os tickets. No cleanup, isMountedRef.current vira false; na segunda execução do efeito em Strict Mode, loadClassifiedTickets() roda com o ref desativado e loading/estado não atualizam, deixando a tela presa no carregamento. Defina isMountedRef.current = true no início do efeito.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@src/components/ai/AutoTicketClassifier.tsx` around lines 127 - 134, Atualize
o efeito que chama loadClassifiedTickets para definir isMountedRef.current como
true antes do carregamento. Preserve o cleanup que o redefine para false,
garantindo que execuções subsequentes do efeito em Strict Mode possam atualizar
loading e os demais estados.

src/components/effects/EasterEggs.tsx-64-69 (1)

64-69: 🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win

Remova rainbow-mode e disco-mode no unmount.
O cleanup atual só cancela os timers; se o provider desmontar antes do timeout, as classes ficam em document.body e o efeito vaza para o resto da app.

Correção sugerida

     useEffect(
       () => () => {
         effectTimers.current.forEach(clearTimeout);
+        document.body.classList.remove('rainbow-mode', 'disco-mode');
       },
       []
     );

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@src/components/effects/EasterEggs.tsx` around lines 64 - 69, Atualize o
cleanup de desmontagem do componente em EasterEggs para remover explicitamente
as classes `rainbow-mode` e `disco-mode` de `document.body`, além de cancelar os
timers existentes. Garanta que ambos os efeitos sejam limpos mesmo quando o
provider desmontar antes dos timeouts.

src/features/admin/components/GmailWebhookMonitor.tsx-35-37 (1)

35-37: 🗄️ Data Integrity & Integration | 🟡 Minor | ⚡ Quick win

Valide cada conta antes do cast para EmailAccount.

Array.isArray não valida os elementos. O cast final aceita itens nulos, primitivos ou objetos sem id/email_address, produzindo dados inválidos na lista. Filtre com um type guard/schema que confirme os campos obrigatórios antes do map.

As per path instructions, “any/unknown sem narrowing posterior” deve ser verificado.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@src/features/admin/components/GmailWebhookMonitor.tsx` around lines 35 - 37,
Valide cada elemento de emailAccounts antes do cast final em EmailAccount:
filtre apenas objetos não nulos que contenham os campos obrigatórios id e
email_address, usando um type guard ou schema com narrowing explícito de
unknown. Aplique o map que define history_id como null somente após essa
filtragem e remova a dependência de um cast que aceite dados inválidos.

Source: Path instructions

src/components/settings/theme/useThemePreset.ts-181-205 (1)

181-205: 🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win

Valide o payload antes de aplicar o tema. JSON.parse(text) deixa config sem forma garantida; um borderRadius não numérico pode virar NaNrem em applyBorderRadius, e preset/theme fora do tipo esperado ainda chegam aos callbacks. Faça o parse como unknown e aplique narrowing antes de chamar applyPresetById, applyBorderRadius e onThemeChange.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@src/components/settings/theme/useThemePreset.ts` around lines 181 - 205,
Validate the imported payload in importTheme before applying any values: parse
it as unknown, narrow it to an object, require preset and theme to be strings,
and ensure borderRadius is a finite number before invoking applyPresetById,
applyBorderRadius, setBorderRadius, or onThemeChange. Keep invalid payloads
routed to the existing error toast.

Source: Path instructions

src/features/auth/components/mfa/MFAEnroll.tsx-64-71 (1)

64-71: 🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win

Não atualize a ref durante o render. Em React concorrente, handleVerifyRef.current = handleVerify pode expor a closure de um render descartado; mova essa sincronização para um useEffect dependente de handleVerify, antes do efeito que reage a code.

Correção sugerida

 const handleVerifyRef = useRef(handleVerify);
- handleVerifyRef.current = handleVerify;
+ useEffect(() => {
+   handleVerifyRef.current = handleVerify;
+ }, [handleVerify]);

 useEffect(() => {

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@src/features/auth/components/mfa/MFAEnroll.tsx` around lines 64 - 71, In
MFAEnroll, stop assigning handleVerifyRef.current during render; synchronize the
ref in a useEffect dependent on handleVerify, declared before the existing
code-length verification effect. Keep the handleVerifyRef.current invocation in
the code effect unchanged.

Source: Linters/SAST tools

src/hooks/useRetryAndErrorPrevention.ts-260-274 (1)

260-274: 🩺 Stability & Availability | 🟡 Minor | ⚡ Quick win

O cancelamento não impede onReject.

A expressão da linha 266 é avaliada ao iniciar a Promise; se o componente desmontar depois, o callback já foi capturado e ainda será executado. Passe um wrapper que teste cancelled no momento da rejeição.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@src/hooks/useRetryAndErrorPrevention.ts` around lines 260 - 274, Corrija o
callback onReject no useEffect de useRetryAndErrorPrevention para avaliar
cancelled no momento da rejeição, não durante a criação da Promise. Passe um
wrapper que verifique cancelled antes de invocar onRejectRef.current, mantendo o
cancelamento efetivo após a desmontagem.

src/components/settings/sla/SLARuleFormDialog.tsx-54-59 (1)

54-59: 🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win

Evite escrever em ref.current durante o render — isso deixa o componente impuro e pode expor valores de uma renderização abortada em React concorrente. Mova essa sincronização para um useEffect/useLayoutEffect (ou um helper useLatest).

• src/components/settings/sla/SLARuleFormDialog.tsx#L54-L59
• src/hooks/useRetryAndErrorPrevention.ts#L152-L153
• src/hooks/useRetryAndErrorPrevention.ts#L187-L188
• src/hooks/useRetryAndErrorPrevention.ts#L233-L234
• src/hooks/useRetryAndErrorPrevention.ts#L260-L261
• src/hooks/useRetryAndErrorPrevention.ts#L302-L307
• src/hooks/useRetryAndErrorPrevention.ts#L394-L397
• src/hooks/useTeamChatDraft.ts#L29-L32

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@src/components/settings/sla/SLARuleFormDialog.tsx` around lines 54 - 59, Stop
assigning to ref.current during render; synchronize each latest-value ref
through useEffect/useLayoutEffect or the existing useLatest helper. Update
SLARuleFormDialog.tsx lines 54-59, all listed ref assignments in
useRetryAndErrorPrevention.ts at lines 152-153, 187-188, 233-234, 260-261,
302-307, and 394-397, and useTeamChatDraft.tsx lines 29-32, preserving the
existing consumers and dependency behavior.

Source: Linters/SAST tools

src/components/ui/registry.json-91-99 (1)

91-99: 🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win

Remova as variantes duplicadas do registry.

toggle.variant, badge.variant, input.variant e card.variant repetem "hover" ou "visible". Como src/pages/DesignSystem.tsx renderiza cada entrada diretamente, essas duplicatas aparecem como opções repetidas e poluem o catálogo visual. Mantenha cada variante uma única vez ou corrija o gerador do registry.

Also applies to: 131-150, 204-221, 230-246

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@src/components/ui/registry.json` around lines 91 - 99, Remova as entradas
duplicadas nas listas de variantes de toggle, badge, input e card no registry,
mantendo cada variante como "hover" ou "visible" apenas uma vez. Preserve a
ordem e todas as variantes únicas para que DesignSystem.tsx continue
renderizando o catálogo completo sem opções repetidas.

src/hooks/useGmailOAuthFlow.ts-334-337 (1)

334-337: 🩺 Stability & Availability | 🟡 Minor | ⚡ Quick win

Trate a Promise retornada por ensureWatch.

O efeito chama uma função async sem await nem .catch(). Uma rejeição inesperada pode gerar unhandled rejection; use void ensureWatch(acc.id).catch(...) ou agregue as chamadas com Promise.allSettled.

As per path instructions: Promises sem await ou .catch().

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@src/hooks/useGmailOAuthFlow.ts` around lines 334 - 337, Atualize o efeito que
percorre accountsRef.current para tratar a Promise retornada por ensureWatch:
encadeie um catch com tratamento apropriado para cada chamada ou agregue as
chamadas usando Promise.allSettled, evitando rejeições não tratadas.

Source: Path instructions

src/features/inbox/components/RealtimeInboxView.tsx-129-160 (1)

129-160: 🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win

Exponha useExternalDb no retorno do hook. RealtimeInboxView lê (inbox as any).useExternalDb, mas useRealtimeInbox não retorna esse campo; o valor fica undefined e a decisão de markAsRead passa a depender de uma condição acidental. Passe o booleano tipado pelo hook ou mova essa lógica para dentro dele.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@src/features/inbox/components/RealtimeInboxView.tsx` around lines 129 - 160,
Expose the typed useExternalDb boolean from useRealtimeInbox and include it in
the hook’s returned value, then consume that returned field directly in
RealtimeInboxView instead of casting inbox to any. Preserve the existing
markAsRead condition and dependency tracking using the exposed value.

Source: Path instructions

src/features/inbox/hooks/realtime/useAutomationFailureAlerts.ts-78-81 (1)

78-81: 🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win

Falta narrowing em row.rule_snapshot?.name.

Com rule_snapshot agora tipado como Record<string, unknown> | null, row.rule_snapshot?.name resolve para unknown e não recebe cast, ao contrário de payload.rule_name (linha 80) e de ctx.stage (linhas 81/99), que já usam cast explícito. Se name não for string, o toast pode exibir [object Object] sem aviso do compilador.

🔧 Sugestão de correção

-      const ruleName =
-        row.rule_snapshot?.name ?? (payload.rule_name as string | undefined) ?? 'Regra sem nome';
+      const ruleName =
+        (row.rule_snapshot?.name as string | undefined) ??
+        (payload.rule_name as string | undefined) ??
+        'Regra sem nome';

As per path instructions, "any/unknown sem narrowing posterior" deve ser verificado em código TypeScript/JavaScript.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@src/features/inbox/hooks/realtime/useAutomationFailureAlerts.ts` around lines
78 - 81, Faça o narrowing de row.rule_snapshot?.name no cálculo de ruleName,
validando ou convertendo explicitamente o valor unknown para string antes de
usá-lo como nome. Preserve o fallback existente para payload.rule_name e “Regra
sem nome”, garantindo que valores não-string não cheguem ao toast como [object
Object].

Source: Path instructions

🧹 Nitpick comments (7)

.github/workflows/ts-nocheck-ratchet.yml (1)

19-19: 🔒 Security & Privacy | 🔵 Trivial | ⚡ Quick win

Checkout sem persist-credentials: false — job é somente leitura.

Esse job só faz grep/wc em src/, não precisa de push nem chamadas gh. Ao contrário do workflow fix-schema-refs.yml (que precisa do token para push), aqui não há justificativa para manter credenciais persistidas no runner.

🔒 Fix sugerido

       - uses: actions/checkout@v4
+        with:
+          persist-credentials: false

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In @.github/workflows/ts-nocheck-ratchet.yml at line 19, Update the
actions/checkout@v4 step in the ts-nocheck-ratchet workflow to disable persisted
credentials with persist-credentials: false, keeping the rest of the read-only
job unchanged.

Source: Linters/SAST tools

.github/workflows/ci-gate.yml (1)

61-63: 🔒 Security & Privacy | 🔵 Trivial | ⚡ Quick win

Template injection: interpolar github.base_ref direto no shell.

O zizmor sinalizou linhas 62-63: ${{ github.base_ref }} é expandido textualmente antes do shell rodar. Hoje o trigger restringe a main/develop, então o risco prático é baixo, mas é um padrão frágil — se o gatilho mudar no futuro (ou herdar de pull_request_target), vira injeção de comando real. Passe o valor via env em vez de interpolar direto.

🛡️ Fix sugerido

       - name: Verify bun.lock is in sync with package.json
+        env:
+          BASE_REF: ${{ github.base_ref }}
         run: |
           if [ "${{ github.event_name }}" = "pull_request" ]; then
-            git fetch origin ${{ github.base_ref }}
-            BASE="origin/${{ github.base_ref }}"
+            git fetch origin "$BASE_REF"
+            BASE="origin/$BASE_REF"

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In @.github/workflows/ci-gate.yml around lines 61 - 63, Atualize o bloco
condicional do workflow que usa `github.event_name` para receber
`github.base_ref` por meio de uma variável `env`, removendo as interpolações
diretas `${{ github.base_ref }}` nos comandos `git fetch` e na atribuição de
`BASE`; preserve o comportamento de buscar e referenciar a branch base da pull
request.

Source: Linters/SAST tools

src/utils/emailMappers.ts (1)

16-16: 🎯 Functional Correctness | 🔵 Trivial | ⚡ Quick win

Valide o payload antes dos casts.

Trocar any por unknown não torna o mapper seguro enquanto todos os campos continuam usando as string, as boolean etc. Payloads inválidos ainda entram nos modelos tipados e podem quebrar consumidores depois. Use um schema Zod ou type guard antes do mapeamento.

As per path instructions: verificar any/unknown sem narrowing posterior.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@src/utils/emailMappers.ts` at line 16, Valide o payload Raw antes do
mapeamento, substituindo os casts diretos para string, boolean e demais tipos
por um schema Zod ou type guard que faça o narrowing dos campos. Faça o mapper
prosseguir apenas com dados validados e rejeite ou trate payloads inválidos
antes de construir os modelos tipados.

Source: Path instructions

src/components/monitoring/RetryMetricsPanel.tsx (1)

116-124: 🚀 Performance & Scalability | 🔵 Trivial | ⚡ Quick win

Estabilize filters antes de passá-lo ao hook.

Esse objeto é recriado em cada render e é enviado diretamente a useRetryMetrics. Caso o hook use o objeto em queryKey ou dependências de efeitos, isso pode causar churn ou refetches desnecessários.

As per coding guidelines: valores derivados usados em queryKey ou dependências de hooks devem ser estabilizados com useMemo ou estado apropriado.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@src/components/monitoring/RetryMetricsPanel.tsx` around lines 116 - 124,
Estabilize o objeto filters antes de passá-lo a useRetryMetrics, usando useMemo
com hours, actionFilter e statusFilter como dependências. Preserve os valores
atuais de action e status, mantendo null para o filtro all, e continue usando o
objeto memoizado na chamada do hook.

Source: Coding guidelines

src/features/inbox/components/ConversationHistory.tsx (1)

172-176: 🚀 Performance & Scalability | 🔵 Trivial | ⚡ Quick win

Remova contactPhone das dependências.

fetchConversationHistory não lê contactPhone; mantê-lo no callback e no efeito provoca refetches desnecessários quando o telefone é formatado ou atualizado.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@src/features/inbox/components/ConversationHistory.tsx` around lines 172 -
176, Remove contactPhone from the dependency array of the useEffect that invokes
fetchConversationHistory in ConversationHistory. Keep contactId, periodFilter,
and fetchConversationHistory as dependencies, and leave the callback
dependencies unchanged unless required by this removal.

src/features/auth/components/mfa/MFAVerify.tsx (1)

56-59: 🩺 Stability & Availability | 🔵 Trivial | ⚡ Quick win

Refs são mutadas durante o render em dois hooks.

Sincronize ambas após o commit para evitar que renders concorrentes descartados contaminem efeitos posteriores.

• src/features/auth/components/mfa/MFAVerify.tsx#L56-L59: mover as atribuições para um efeito pós-commit.
• src/features/inbox/components/chat/useChatInputLogic.ts#L46-L47: sincronizar inputValueRef em efeito ou usar o valor comprometido do textarea.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@src/features/auth/components/mfa/MFAVerify.tsx` around lines 56 - 59, Move
the current-value assignments for handleVerifyRef and verifyingRef in
MFAVerify.tsx into a post-commit effect, preserving their latest committed
values for subsequent effects. Also update inputValueRef synchronization in
useChatInputLogic.ts at lines 46-47 to occur in an effect or otherwise use the
textarea’s committed value; both sites require changes.

src/features/inbox/hooks/useRealtimeInbox.ts (1)

201-201: 🚀 Performance & Scalability | 🔵 Trivial | ⚡ Quick win

Não dependa do objeto inteiro messageQueue sem estabilizá-lo.

useMessageQueue retorna um novo objeto a cada renderização, então esta dependência faz o efeito executar novamente em toda renderização. Dependa diretamente do callback estável reconcileWithDelivery ou memorize o controller retornado pelo hook.

As per coding guidelines, valores derivados usados em dependências de hooks devem ser estabilizados com useMemo/estado apropriado.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@src/features/inbox/hooks/useRealtimeInbox.ts` at line 201, Atualize as
dependências do efeito associado a `selectedMessages`, `selectedContactId` e
`messageQueue` para não depender do objeto instável `messageQueue`; use
diretamente o callback estável `reconcileWithDelivery` ou memorize o controller
retornado por `useMessageQueue`, garantindo que o efeito só seja reexecutado
quando seus valores relevantes mudarem.

Source: Coding guidelines

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 7265195f-a918-4138-93f8-962fc678e3be

📥 Commits

Reviewing files that changed from the base of the PR and between 91bb6ec and cf6dd32.

⛔ Files ignored due to path filters (1)

• bun.lock is excluded by !**/*.lock, !**/*.lock

📒 Files selected for processing (149)

• .github/workflows/ci-gate.yml
• .github/workflows/fix-schema-refs.yml
• .github/workflows/pr-size-gate.yml
• .github/workflows/ts-nocheck-ratchet.yml
• .gitignore
• src/components/ai/AutoTicketClassifier.tsx
• src/components/catalog/ExternalProductCatalog.tsx
• src/components/catalog/ExternalProductManagement.tsx
• src/components/catalog/ProductDetailDialog.tsx
• src/components/catalog/SendProductDialog.tsx
• src/components/connections/ConnectionAuditDialog.tsx
• src/components/connections/ConnectionsView.tsx
• src/components/connections/InstanceSettingsDialog.tsx
• src/components/connections/IntegrationsPanel.tsx
• src/components/connections/NumberReputationMonitor.tsx
• src/components/contacts/AuditLogPanel.tsx
• src/components/contacts/ContactRecycleBin.tsx
• src/components/contacts/useContactDuplicateDetector.ts
• src/components/dashboard/ConversationHeatmap.tsx
• src/components/dashboard/FloatingParticles.tsx
• src/components/diagnostics/ConnectionHealthPanel.tsx
• src/components/effects/EasterEggs.tsx
• src/components/gamification/GamificationProvider.tsx
• src/components/layout/SidebarNavGroup.tsx
• src/components/monitoring/MonitoringWebhookPanel.tsx
• src/components/monitoring/RetryMetricsPanel.tsx
• src/components/monitoring/useRetryMetricsPanelState.ts
• src/components/queues/SLADashboard.tsx
• src/components/reports/AbandonmentRate.tsx
• src/components/reports/ConversationHeatmap.tsx
• src/components/reports/DemandForecast.tsx
• src/components/reports/PeriodComparison.tsx
• src/components/security/AuditLogDashboard.tsx
• src/components/security/IPWhitelistPanel.tsx
• src/components/security/RateLimitRealtimeAlerts.tsx
• src/components/security/SecurityOverview.tsx
• src/components/settings/sla/SLARuleFormDialog.tsx
• src/components/settings/theme/useThemePreset.ts
• src/components/team-chat/TeamChatInputArea.tsx
• src/components/team-chat/TeamChatPanel.tsx
• src/components/team-chat/useTeamChatPanel.ts
• src/components/transitions/TransitionProvider.tsx
• src/components/ui/chart.tsx
• src/components/ui/command-palette.tsx
• src/components/ui/registry.json
• src/components/voice/FloatingParticles.tsx
• src/features/admin/components/GmailWebhookMonitor.tsx
• src/features/admin/components/SicoobBridgeDashboard.tsx
• src/features/admin/components/TrainingMode.tsx
• src/features/admin/hooks/useAdminManagement.ts
• src/features/auth/components/AuthProvider.tsx
• src/features/auth/components/mfa/MFAEnroll.tsx
• src/features/auth/components/mfa/MFAVerify.tsx
• src/features/auth/hooks/usePermissions.ts
• src/features/inbox/components/CRMAutoSync.tsx
• src/features/inbox/components/ChatPanel.tsx
• src/features/inbox/components/ContactPurchasesPanel.tsx
• src/features/inbox/components/ConversationHistory.tsx
• src/features/inbox/components/ConversationListSidebar.tsx
• src/features/inbox/components/ConversationMemoryPanel.tsx
• src/features/inbox/components/ConversationSummary.tsx
• src/features/inbox/components/ConversationTasksPanel.tsx
• src/features/inbox/components/LeadRiskScorePanel.tsx
• src/features/inbox/components/NextBestActionEngine.tsx
• src/features/inbox/components/ObjectionDetector.tsx
• src/features/inbox/components/RealtimeInboxView.tsx
• src/features/inbox/components/RemindersPanel.tsx
• src/features/inbox/components/TeamFiles.tsx
• src/features/inbox/components/VoiceChanger.tsx
• src/features/inbox/components/chat/AIEnhanceButton.tsx
• src/features/inbox/components/chat/ChatInputArea.tsx
• src/features/inbox/components/chat/MessageStatusPanel.tsx
• src/features/inbox/components/chat/hooks/useInitialHighlight.ts
• src/features/inbox/components/chat/useChatInputLogic.ts
• src/features/inbox/components/chat/useChatPanelHandlers.ts
• src/features/inbox/components/contact-details/EditContactDialog.tsx
• src/features/inbox/components/conversation-list/ConversationItem.tsx
• src/features/inbox/components/useAudioRecorderUI.ts
• src/features/inbox/components/useFileUploadLogic.ts
• src/features/inbox/components/useGlobalSearchData.ts
• src/features/inbox/hooks/reactions/useBatchReactions.ts
• src/features/inbox/hooks/realtime/useAutomationFailureAlerts.ts
• src/features/inbox/hooks/sip/useSipConnection.ts
• src/features/inbox/hooks/useChatMediaSending.ts
• src/features/inbox/hooks/useChatSearch.ts
• src/features/inbox/hooks/useMediaUrl.ts
• src/features/inbox/hooks/useMessageQueue.ts
• src/features/inbox/hooks/useMessageStatus.ts
• src/features/inbox/hooks/useMessages.ts
• src/features/inbox/hooks/useMessagesCursor.ts
• src/features/inbox/hooks/useNewConversation.ts
• src/features/inbox/hooks/useRealtimeInbox.ts
• src/features/sla/hooks/useSLAAlertPreferences.ts
• src/features/sla/hooks/useSLAAlerts.ts
• src/features/sla/hooks/useSLACalculation.ts
• src/hooks/__tests__/useSpeechToText.test.ts
• src/hooks/connections/useConnectionsManagement.ts
• src/hooks/connections/useHubTabNavigation.ts
• src/hooks/use-toast.ts
• src/hooks/useAudioManagement.ts
• src/hooks/useAudioRecorder.ts
• src/hooks/useAutomationSuggestions.ts
• src/hooks/useAutomations.ts
• src/hooks/useConversationManagement.ts
• src/hooks/useDebounce.ts
• src/hooks/useEmail.ts
• src/hooks/useEmailManagement.ts
• src/hooks/useEvolutionApiManagement.ts
• src/hooks/useEvolutionAutoSync.ts
• src/hooks/useExternalApiManagement.ts
• src/hooks/useExternalEvolution.ts
• src/hooks/useGmailOAuthFlow.ts
• src/hooks/useImportData.ts
• src/hooks/useIndexNavigation.ts
• src/hooks/useIntegrationManagement.ts
• src/hooks/useNotificationManagement.ts
• src/hooks/useOnboarding.ts
• src/hooks/useProviderPanel.ts
• src/hooks/usePushNotifications.ts
• src/hooks/useQueueManagement.ts
• src/hooks/useRetryAndErrorPrevention.ts
• src/hooks/useTeamChatDraft.ts
• src/hooks/useTypingPresence.ts
• src/hooks/useVoiceManagement.ts
• src/integrations/datasource/db.ts
• src/integrations/supabase/safe-queries.ts
• src/integrations/supabase/safeClient.test.ts
• src/integrations/supabase/safeClient.ts
• src/lib/silentErrorPrevention.ts
• src/lib/supabaseHelpers.ts
• src/pages/OAuthConsent.tsx
• src/pages/admin-realtime-monitor/DispatchErrorsBlock.tsx
• src/pages/admin-realtime-monitor/EventsLiveBlock.tsx
• src/pages/admin-webhook-secret-status/useAdminWebhookStatus.ts
• src/pages/admin-webhook-secret-status/useHmacAuditHistory.ts
• src/pages/admin/AdminDevDiagnosticsPage.tsx
• src/pages/admin/AdminEmailAuditPage.tsx
• src/pages/admin/Connections.tsx
• src/pages/admin/email/useEmailHealthStatus.ts
• src/pages/admin/operations/OpsTransfersTab.tsx
• src/services/api/genericService.ts
• src/services/api/mutationFactory.ts
• src/services/api/queryFactory.ts
• src/services/api/types.ts
• src/services/connections/connectionsRepository.ts
• src/services/settings/settingsRepository.ts
• src/shared/criticalPayloadSchemas.ts
• src/test/typing.ts
• src/utils/emailMappers.ts

💤 Files with no reviewable changes (11)

• src/features/admin/components/SicoobBridgeDashboard.tsx
• src/pages/admin-webhook-secret-status/useHmacAuditHistory.ts
• src/components/monitoring/useRetryMetricsPanelState.ts
• src/pages/admin-realtime-monitor/DispatchErrorsBlock.tsx
• src/pages/admin-realtime-monitor/EventsLiveBlock.tsx
• src/pages/admin/operations/OpsTransfersTab.tsx
• src/components/dashboard/ConversationHeatmap.tsx
• src/pages/admin-webhook-secret-status/useAdminWebhookStatus.ts
• src/hooks/usePushNotifications.ts
• src/components/transitions/TransitionProvider.tsx
• src/hooks/useExternalApiManagement.ts

[coderabbitai]

🗄️ Data Integrity & Integration | 🟠 Major | ⚡ Quick win

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Verifica se existem refs a schema public associadas a mensagens/conversas
rg -n "schema: 'public'" -g '*.ts' -g '*.tsx' -B3 -A3 src/ | rg -i 'evolution_messages|evolution_conversations'

Repository: adm01-debug/zapp-web-v3

Length of output: 161

---

🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo "== workflow =="
git ls-files .github/workflows/fix-schema-refs.yml
wc -l .github/workflows/fix-schema-refs.yml
sed -n '1,140p' .github/workflows/fix-schema-refs.yml

echo
echo "== search schema refs =="
rg -n "schema: 'public'|schema: \"public\"|schema: 'zapp'|schema: \"zapp\"|evolution_messages|evolution_conversations" .

echo
echo "== candidate files mentioning evo tables =="
rg -n "evolution_messages|evolution_conversations" .

Repository: adm01-debug/zapp-web-v3

Length of output: 50380

---

🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo "== .github/workflows/fix-schema-refs.yml (trechos) =="
sed -n '1,140p' .github/workflows/fix-schema-refs.yml

echo
echo "== migração que cita public -> zapp no realtime =="
sed -n '1,120p' supabase/migrations/20260724000026_fix_missing_realtime_publications.sql

echo
echo "== migração de views zapp para evolution_* =="
sed -n '1,90p' supabase/migrations/20260725000012_create_zapp_views_edge_function_tables.sql

echo
echo "== guia do projeto sobre evo/zapp =="
sed -n '40,60p' CLAUDE.md

Repository: adm01-debug/zapp-web-v3

Length of output: 10091

---

🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo "== ocorrências de schema: 'public' no src =="
rg -n -C 3 "schema: 'public'|schema: \"public\"" src/

echo
echo "== ocorrências de schema: 'public' no supabase/functions =="
rg -n -C 3 "schema: 'public'|schema: \"public\"" supabase/functions

echo
echo "== trechos do arquivo citado com public =="
sed -n '80,110p' src/features/inbox/components/useAudioMessagePlayer.ts

Repository: adm01-debug/zapp-web-v3

Length of output: 2167

---

🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo "== useAudioMessagePlayer.ts =="
sed -n '80,102p' src/features/inbox/components/useAudioMessagePlayer.ts

echo
echo "== useBridgeStatus.ts =="
sed -n '192,210p' src/pages/admin/useBridgeStatus.ts

echo
echo "== busca por voice_conversion_queue =="
rg -n -C 3 "voice_conversion_queue" .

echo
echo "== busca por system_health_incidents =="
rg -n -C 3 "system_health_incidents" .

Repository: adm01-debug/zapp-web-v3

Length of output: 50379

---

Restringe o replace automático

O sed global vai trocar também public.voice_conversion_queue e public.system_health_incidents, que são tabelas físicas/publicadas de verdade. Isso quebra essas subscriptions ao apontá-las para zapp (onde há view proxy/no-op). Limite a migração aos alvos corretos com uma whitelist explícita.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In @.github/workflows/fix-schema-refs.yml around lines 55 - 58, Restrict the
automatic schema replacement in the workflow’s migration step to an explicit
whitelist of intended Realtime subscription targets, excluding
public.voice_conversion_queue and public.system_health_incidents. Update the
sed/replacement logic while preserving the existing PR creation flow in gh pr
create.

[coderabbitai]

🎯 Functional Correctness | 🟠 Major | ⚡ Quick win

A mudança de página dispara o debounce de filtros e volta para a página 1.

buildFilters depende de page; portanto, ao avançar a paginação, ele muda e reexecuta o efeito de filtros. Após 300 ms, esse efeito executa setPage(0), impedindo permanecer em qualquer página posterior. Separe os filtros-base paginados com useMemo e deixe o debounce depender apenas dos filtros, não de page.

Conforme as coding guidelines, “Estabilizar valores derivados usados em queryKey, dependências de hooks ou paginação com useMemo/estado apropriado”.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@src/components/catalog/ExternalProductManagement.tsx` around lines 89 - 94,
Impeça que a mudança de página reative o debounce de filtros em
ExternalProductManagement. Separe os filtros-base da paginação em um valor
estabilizado com useMemo, faça o efeito de filtros depender apenas desses
filtros e preserve page apenas no fluxo de busca paginada; ajuste buildFilters e
as dependências dos efeitos para que avançar a página não execute setPage(0).

Source: Coding guidelines

[coderabbitai]

🎯 Functional Correctness | 🟠 Major | ⚡ Quick win

Não confirme o aquecimento quando o update falhar.

startReputationWarmup em src/hooks/useNumberReputation.ts ignora o { error } do Supabase e sempre resolve. Assim, esta chamada sempre exibe sucesso, mesmo sem atualizar a reputação. Faça o helper lançar/retornar o erro e mostre um toast destrutivo aqui.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@src/components/connections/NumberReputationMonitor.tsx` around lines 39 - 42,
Update startReputationWarmup in useNumberReputation to propagate the Supabase
update error instead of always resolving, then adjust startWarmup in
NumberReputationMonitor to show the success toast only after a successful update
and display a destructive toast when the helper fails.

[coderabbitai]

🩺 Stability & Availability | 🟠 Major | ⚡ Quick win

Trate falhas do carregamento.

Se fetchIPWhitelist() rejeitar, o efeito gera uma Promise não tratada e o spinner pode permanecer ativo. Capture o erro e mova setLoading(false) para um finally protegido por mountedRef.current; isso também cobre as chamadas dos handlers.

As per path instructions, “Promises sem await ou .catch().”

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@src/components/security/IPWhitelistPanel.tsx` around lines 53 - 63, Handle
rejection in fetchWhitelistedIPs by wrapping fetchIPWhitelist and the state
update in try/finally, ensuring the returned Promise is caught by the useEffect
invocation and handler callers. Move setLoading(false) into a finally block
guarded by mountedRef.current, while preserving the existing mounted check
before updating whitelisted IPs.

Source: Path instructions

[coderabbitai]

🩺 Stability & Availability | 🔴 Critical | ⚡ Quick win

Capture falhas de loadSessions.

A consulta pode rejeitar em falhas de rede, mas loadSessions não captura erros e o efeito a chama sem await nem .catch(). Trate o erro dentro de loadSessions ou use void loadSessions().catch(...); isso também protege a chamada posterior na conclusão do cenário.

Conforme as path instructions, verifique “Promises sem await ou .catch()”.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@src/features/admin/components/TrainingMode.tsx` around lines 80 - 93, Capture
rejected promises from loadSessions by handling the Supabase query error inside
the callback or attaching a catch handler to every effect invocation, including
the later scenario-completion call. Ensure the effect does not leave
loadSessions unhandled while preserving the existing session-loading behavior.

Source: Path instructions

[coderabbitai]

🎯 Functional Correctness | 🟠 Major | ⚡ Quick win

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
rg -n -C 3 --glob '*.{ts,tsx}' \
  'useAsyncEffect\s*\(|dependencies\s*:' src

Repository: adm01-debug/zapp-web-v3

Length of output: 161

---

🏁 Script executed:

#!/bin/bash
set -euo pipefail

# Mapear o arquivo e localizar o hook/assinaturas relacionadas
ast-grep outline src/hooks/useRetryAndErrorPrevention.ts --view expanded || true

echo '---'
rg -n -C 4 --glob 'src/**/*.{ts,tsx}' \
  'dependencies\s*:|useRetryAndErrorPrevention|useAsyncEffect|withErrorRecovery' src

Repository: adm01-debug/zapp-web-v3

Length of output: 9702

---

🏁 Script executed:

#!/bin/bash
set -euo pipefail

sed -n '291,335p' src/hooks/useRetryAndErrorPrevention.ts

Repository: adm01-debug/zapp-web-v3

Length of output: 1338

---

dependencies está sendo ignorado pelo hook. O useEffect só depende de operation, então mudanças passadas por quem usa useAsyncEffect não disparam nova execução; ou conecte dependencies ao efeito, ou remova essa opção da API.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@src/hooks/useRetryAndErrorPrevention.ts` around lines 300 - 329, Conecte a
opção dependencies ao array de dependências do useEffect no fluxo de
useAsyncEffect, preservando operation como dependência existente para que
alterações recebidas pelo consumidor disparem novamente o efeito. Não remova
dependencies da API; use o valor já desestruturado em options.

[coderabbitai]

🗄️ Data Integrity & Integration | 🟠 Major | ⚡ Quick win

Não propague any pelo acesso dinâmico.

dbFrom é um ponto central e seu retorno any remove a validação de colunas, payloads e resultados de todas as consultas downstream. Retorne ReturnType<typeof supabase.from> — como já feito em src/lib/supabaseHelpers.ts — ou um builder explicitamente limitado.

Correção sugerida

-export function dbFrom(entity: LogicalEntity): any {
+export function dbFrom(entity: LogicalEntity): ReturnType<typeof supabase.from> {

As per path instructions: **/*.{ts,tsx,js,jsx}: verificar any/unknown sem narrowing posterior.

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	type DynamicTableClient = { from(t: string): ReturnType<typeof supabase.from> };
	// eslint-disable-next-line @typescript-eslint/no-explicit-any
	export function dbFrom(entity: LogicalEntity): any {
	const mapping = requireMapping(entity);
	validateEntityAccess(mapping.table, mapping.client);
	// eslint-disable-next-line @typescript-eslint/no-explicit-any
	return dbClient(entity).from(mapping.table as any);
	return (dbClient(entity) as unknown as DynamicTableClient).from(mapping.table);
	type DynamicTableClient = { from(t: string): ReturnType<typeof supabase.from> };
	// eslint-disable-next-line `@typescript-eslint/no-explicit-any`
	export function dbFrom(entity: LogicalEntity): ReturnType<typeof supabase.from> {
	const mapping = requireMapping(entity);
	validateEntityAccess(mapping.table, mapping.client);
	return (dbClient(entity) as unknown as DynamicTableClient).from(mapping.table);

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@src/integrations/datasource/db.ts` around lines 63 - 69, Remova o retorno
explícito como any de dbFrom e faça a função retornar ReturnType<typeof
supabase.from>, reutilizando o tipo já empregado em supabaseHelpers.ts. Preserve
o fluxo de requireMapping, validateEntityAccess e dbClient, ajustando apenas a
tipagem do cliente dinâmico e do retorno para evitar propagar any sem narrowing
posterior.

Source: Path instructions

[coderabbitai]

🎯 Functional Correctness | 🟠 Major | ⚡ Quick win

🧩 Analysis chain

🏁 Script executed:

npx tsc --noEmit --pretty false 2>&1 | rg 'src/integrations/supabase/safe-queries.ts|TS2344|SchemaName'

Repository: adm01-debug/zapp-web-v3

Length of output: 161

---

🏁 Script executed:

#!/bin/bash
set -euo pipefail

printf '\n## safe-queries.ts\n'
cat -n src/integrations/supabase/safe-queries.ts | sed -n '1,120p'

printf '\n## supabase package version\n'
node - <<'JS'
const fs = require('fs');
const pkg = JSON.parse(fs.readFileSync('package.json', 'utf8'));
const ver = pkg.dependencies?.['`@supabase/supabase-js`'] || pkg.devDependencies?.['`@supabase/supabase-js`'] || '(not found)';
console.log(ver);
JS

printf '\n## SupabaseClient type signature in installed types (if present)\n'
rg -n "type SchemaName|class SupabaseClient|interface SupabaseClient" node_modules/@supabase -g '*.d.ts' -g '*.ts' | sed -n '1,120p'

Repository: adm01-debug/zapp-web-v3

Length of output: 4957

---

🏁 Script executed:

#!/bin/bash
set -euo pipefail

printf '\n## relevant local type definitions for Database\n'
rg -n "export type Database|type Database" src/integrations/supabase -g '*.ts' -g '*.tsx' | sed -n '1,80p'

printf '\n## usages of AnySupabaseClient and schema()\n'
rg -n "AnySupabaseClient|schema\\('evo'\\)|schema\\('zapp'\\)" src/integrations/supabase src -g '*.ts' -g '*.tsx' | sed -n '1,160p'

Repository: adm01-debug/zapp-web-v3

Length of output: 2106

---

🏁 Script executed:

#!/bin/bash
set -euo pipefail

python3 - <<'PY'
from pathlib import Path
p = Path('src/integrations/supabase/safe-queries.ts')
text = p.read_text()
print(text)
PY

Repository: adm01-debug/zapp-web-v3

Length of output: 7694

---

🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo "## safe-queries.ts"
cat -n src/integrations/supabase/safe-queries.ts | sed -n '1,120p'

echo
echo "## Database type"
rg -n "export type Database|type Database" src/integrations/supabase -g '*.ts' -g '*.tsx' | sed -n '1,80p'

echo
echo "## SupabaseClient declaration"
if [ -d node_modules/@supabase ]; then
  rg -n "class SupabaseClient|type SchemaName" node_modules/@supabase -g '*.d.ts' -g '*.ts' | sed -n '1,120p'
else
  echo "node_modules/@supabase not present"
fi

Repository: adm01-debug/zapp-web-v3

Length of output: 5152

---

🌐 Web query:

SupabaseClient generic schema parameter string keyof Database TS2344 @supabase/supabase-js 2.110.0

💡 Result:

The TS2344 error ("Type '...' does not satisfy the constraint '...'") related to the SupabaseClient generic schema parameter typically occurs when TypeScript fails to infer the correct SchemaName generic or when the provided schema does not match the expected constraints defined in the Database type [1][2]. In versions of @supabase/supabase-js, the SupabaseClient is defined with generic parameters that include SchemaName extends string & keyof Database [1]. This ensures that the schema you pass (or the default 'public') exists within your generated Database interface [1]. Common causes and solutions for this error include: 1. Incomplete or Mismatched Database Types: Ensure your generated Database type actually includes the schema you are trying to use. If your database types were generated without including specific schemas, they will not be present in keyof Database [1][3]. 2. Inference Limitations: When initializing the client with createClient<Database>(...), if you do not explicitly provide the second generic argument (SchemaName), TypeScript may default it to 'public' [4]. If 'public' is not part of your Database type (e.g., you are using a different schema structure), or if the inference is constrained by other options, a TS2344 error may occur [4][2]. 3. Workaround for Initialization: You can often resolve this by explicitly passing the schema name as the second generic parameter during client instantiation [4]: const supabase = createClient<Database, 'your_schema_name'>(URL, KEY); 4. Type Relaxation: If you are encountering this error specifically in the client options.db.schema configuration, recent updates in the library have aimed to relax these constraints [4]. Ensure you are using the latest version of the library (2.110.0 or later) [5][6], as maintainers frequently adjust these type definitions to improve compatibility with complex custom schemas [4]. If you are using @supabase/ssr, ensure your createClient wrappers are correctly passing the generic types through to the underlying SupabaseClient instance [7][2]. If the error persists after explicitly defining the schema, double-check that your generated types file (database.types.ts) includes the target schema and that your Database interface is correctly exported [3].

Citations:

• 1: https://github.com/supabase/supabase-js/blob/b8a5d7137de9985d09fb5820b444b1f7a8a580f3/src/SupabaseClient.ts
• 2: @supabase/supabase-js v2.50.4 breaks types supabase/supabase-js#1483
• 3: https://supabase.com/docs/reference/javascript/typescript-support
• 4: fix(supabase): relax db schema type constraints in createClient options supabase/supabase-js#2476
• 5: https://github.com/supabase/supabase-js/releases/tag/v2.110.0
• 6: https://github.com/supabase/supabase-js/blob/HEAD/CHANGELOG.md
• 7: fix(types): export type utils for ssr use supabase/supabase-js#1491

---

🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo "## schema.ts"
cat -n src/integrations/supabase/schema.ts | sed -n '1,220p'

echo
echo "## top of types.ts around Database"
cat -n src/integrations/supabase/types.ts | sed -n '1,120p'

Repository: adm01-debug/zapp-web-v3

Length of output: 6969

---

🏁 Script executed:

#!/bin/bash
set -euo pipefail

log=/tmp/coderabbit-shell-logs/shell-output-LtG4Cv
echo "## log head"
sed -n '1,220p' "$log"

Repository: adm01-debug/zapp-web-v3

Length of output: 173

---

🌐 Web query:

@supabase/supabase-js v2.110.0 SupabaseClient class signature SchemaName extends string keyof Database source

💡 Result:

In @supabase/supabase-js v2.110.0, the SupabaseClient class is defined with three primary generic type parameters [1][2][3]. Its class signature is structured as follows [3]: export default class SupabaseClient< Database = any, SchemaNameOrClientOptions extends (string & keyof Omit<Database, 'InternalSupabase'>) | { PostgrestVersion: string } =..., SchemaName extends string & keyof Omit<Database, 'InternalSupabase'> =..., Schema extends... =..., ClientOptions extends { PostgrestVersion: string } =... > {... } Key aspects of the SchemaName type parameter: 1. Definition: The SchemaName parameter is constrained as SchemaName extends string & keyof Omit<Database, 'InternalSupabase'> [1][3]. It represents the specific database schema being targeted by the client instance [4][5]. 2. Purpose: It facilitates type-safe database queries by restricting access to tables and views within the specified schema [3][6]. 3. Default Behavior: By default, if not explicitly provided, the type system attempts to resolve the schema to 'public' if it exists within the provided Database definition; otherwise, it defaults to the available keys in the Database type [1][3]. 4. Relationship with SchemaNameOrClientOptions: In modern versions of the library (following changes introduced around v2.50.4), the second generic parameter, SchemaNameOrClientOptions, allows for specifying either the schema name or client configuration options (such as PostgrestVersion) [3][7]. The SchemaName parameter is then derived based on these inputs to ensure compatibility with both legacy patterns and newer requirements for SSR and version-specific PostgREST features [3][7]. For most users, the standard usage involves passing the Database type generated by the Supabase CLI, which then automatically populates these generic parameters correctly [6].

Citations:

• 1: https://jsr.io/@supabase/supabase-js/doc/all_symbols
• 2: https://jsr.io/@supabase/supabase-js/doc
• 3: https://github.com/supabase/supabase-js/blob/21e9d4b7/packages/core/supabase-js/src/SupabaseClient.ts
• 4: https://supabase.com/docs/reference/javascript/initializing
• 5: https://github.com/supabase/supabase-js/blob/21e9d4b7/packages/core/supabase-js/src/lib/types.ts
• 6: https://supabase.com/docs/reference/javascript/typescript-support
• 7: fix(types): export type utils for ssr use supabase/supabase-js#1491

---

Restrinja AnySupabaseClient a schemas válidos.

SupabaseClient<Database, string> viola a constraint do generic de schema. Use uma união explícita dos schemas suportados (public | zapp) — ou derive isso de keyof Omit<Database, '__InternalSupabase'> — para manter o helper tipado sem quebrar o build.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@src/integrations/supabase/safe-queries.ts` at line 14, Atualize o alias
AnySupabaseClient para restringir o parâmetro de schema à união válida "public"
| "zapp" (ou derivá-la de keyof Omit<Database, "__InternalSupabase">),
substituindo o string amplo em SupabaseClient<Database, ...> e preservando a
tipagem compatível com a constraint do generic.

[coderabbitai]

🩺 Stability & Availability | 🔴 Critical | ⚡ Quick win

Capture rejeições das operações disparadas com void.

loadLogs() e logAccess(isDev) podem rejeitar sem .catch(). Em especial, loadLogs não possui try/catch/finally, deixando loading ativo caso a consulta lance. Trate o erro dentro das funções ou capture as promessas nas chamadas.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@src/pages/admin/AdminDevDiagnosticsPage.tsx` around lines 76 - 81, Handle
rejected promises from loadLogs and logAccess in the useEffect for
AdminDevDiagnosticsPage: add appropriate try/catch/finally handling inside those
functions, ensuring loadLogs always clears its loading state when the query
fails, or attach catches at both void call sites. Preserve the existing isDev
guard and dependency array.

Source: Path instructions

[coderabbitai]

🎯 Functional Correctness | 🟠 Major | ⚡ Quick win

🧩 Analysis chain

🏁 Script executed:

#!/usr/bin/env bash
set -euo pipefail

fd -i -e ts -e tsx -e json -e lock . \
  | xargs -r rg -n "UseMutationOptions|MutationFunctionContext|`@tanstack/react-query`"

Repository: adm01-debug/zapp-web-v3

Length of output: 30200

---

🏁 Script executed:

#!/usr/bin/env bash
set -euo pipefail

printf '\n## mutationFactory.ts\n'
sed -n '1,280p' src/services/api/mutationFactory.ts | cat -n

printf '\n## queryFactory.ts\n'
sed -n '1,220p' src/services/api/queryFactory.ts | cat -n

printf '\n## package.json TanStack deps\n'
rg -n '"`@tanstack/react-query`"|`@tanstack/query-core`' package.json bun.lock

Repository: adm01-debug/zapp-web-v3

Length of output: 17597

---

🌐 Web query:

TanStack Query v5 useMutation onSuccess onError signature async promise data variables context official docs

💡 Result:

In TanStack Query v5, the onSuccess and onError callback signatures in useMutation (and when passed to mutate) follow a specific structure involving the mutation result, variables, the optional context returned from onMutate, and the mutation function context [1][2][3]. As of v5.89.0, the signatures for these callbacks are [3]: onSuccess: (data: TData, variables: TVariables, onMutateResult: TOnMutateResult | undefined, context: MutationFunctionContext) => void onError: (err: TError, variables: TVariables, onMutateResult: TOnMutateResult | undefined, context: MutationFunctionContext) => void Key signature details: - data / err: The result (on success) or the error object (on error) [1][2]. - variables: The variables passed to the mutation function [1][2]. - onMutateResult: The value returned by your onMutate callback [4]. This will be undefined if no onMutate is defined or if onMutate does not return a value [3]. - context: The mutation function context [3]. Behavior of async and promises: - When defined within the useMutation hook options, returning a promise from onSuccess or onError will cause the hook to await that promise before proceeding to the next step in the mutation lifecycle (e.g., before executing onSettled) [1][2][5]. - When passed directly to the mutate function, onSuccess and onError are triggered for that specific call [4][6]. - You can use mutateAsync if you need to receive a promise that resolves on success or throws on error, which is useful for composing side effects [6]. Important note on updates: A recent change (introduced in v5.89.0) added a fourth parameter (mutation function context) to these callbacks [3]. If you are migrating code that previously relied on a specific number of positional arguments, ensure your callback signatures are updated to accommodate the new parameter structure [3]. Callbacks defined in useMutation execute for every mutate call, whereas callbacks passed directly to the mutate function run only once and only if the component remains mounted [4][6].

Citations:

• 1: https://tanstack.com/query/v5/docs/framework/react/reference/useMutation.md
• 2: https://tanstack.com/query/latest/docs/framework/react/reference/useMutation
• 3: v5.89.0: onError, onSuccess and onSettled signature change breaks existing code TanStack/query#9660
• 4: https://tanstack.com/query/v5/docs/framework/react/guides/mutations
• 5: https://github.com/tanstack/query/blob/main/docs/framework/react/reference/useMutation.md
• 6: https://tanstack.com/query/latest/docs/framework/react/guides/mutations

---

Não deixe ...options sobrescrever os callbacks internos. onSuccess/onError precisam vir depois do spread das opções; hoje um callback do consumidor substitui invalidações/toasts e o wrapper também perde o 4º argumento do TanStack Query v5. Faça o wrapper repassar data, variables, onMutateResult, context e await/return dos callbacks assíncronos em todas as factories.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@src/services/api/mutationFactory.ts` around lines 59 - 63, Atualize todas as
factories de mutação em torno dos callbacks onSuccess e onError para aplicar
...options antes dos callbacks internos, impedindo que opções do consumidor os
sobrescrevam. Faça os wrappers repassarem os quatro argumentos do TanStack Query
v5 — data, variables, onMutateResult e context — e aguardarem/retornarem
callbacks assíncronos, preservando invalidações e toasts.

Sources: Path instructions, MCP tools

[vercel]

Deployment failed with the following error:

Invalid vercel.json file provided

[ecc-tools]

ECC bundle files are already tracked in this repository. Skipping generation of another bundle PR.

[github-actions]

⚠️ PR muito grande — 922 linhas (+754/−168)

Este PR excede o teto de 800 linhas definido no Plano 50 Etapas (Etapa 16).

Ação necessária antes do merge:

1. Dividir em PRs menores com um tema cada, OU
2. Adicionar uma justificativa escrita no corpo do PR explicando por que a divisão não é possível

"Um PR = um tema. PR ideal ≤300 linhas, teto de 800."
— CONTRIBUTING.md

Por que esse limite?

PRs grandes aumentam o tempo de review, elevam o risco de conflito e
tornam o histórico ilegível. O PR #545 do histórico recente tinha 911 linhas
cobrindo 7 temas independentes e zero testes — exatamente esse padrão
que este gate identifica para o reviewer.