Skip to content

fix(messages): reject encrypted contents arrays - #203

Merged
ralyodio merged 1 commit into
profullstack:masterfrom
aiirvizionz:clientkit/chat-messages-encrypted-contents-map-guard
Jul 30, 2026
Merged

fix(messages): reject encrypted contents arrays#203
ralyodio merged 1 commit into
profullstack:masterfrom
aiirvizionz:clientkit/chat-messages-encrypted-contents-map-guard

Conversation

@aiirvizionz

Copy link
Copy Markdown
Contributor

Summary

  • reject encrypted_contents arrays in the legacy chat message send endpoint
  • keep the fan-out input constrained to a user-id to encrypted-content object map
  • add regression coverage that blocks array payloads before participant or message creation work

Test

  • node node_modules\vitest\vitest.mjs run --config %TEMP%\qryptchat-vitest-minimal.config.mjs "src/app/api/chat/messages/route.test.js"
  • git diff --check

uGig billing

  • Expected invoice: 0.50 USD if accepted/merged
  • Counted as revenue now: no, pending review/payment

@ralyodio
ralyodio merged commit 7644d7c into profullstack:master Jul 30, 2026
8 checks passed
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.

2 participants