feat: make agreement chat production-ready (schema + participants)

[Kalchaqui]

Context

Nest already exposes JWT-protected chat endpoints:

• GET /v1/agreements/:agreementId/messages
• POST /v1/agreements/:agreementId/messages

Frontend will be wired to these in a companion FE issue. Before that can work in production, the backend schema and create-agreement path must support real A↔B chat.

Problem

1. AgreementChatService inserts sender_id, but the FE SQL schema for agreement_messages (004-contacts-and-chat.sql) has no sender_id column → Nest insert will fail against current DB.
2. On agreement create, if agreement_participants insert fails, we only console.error and continue → counterparty cannot access the agreement or chat (Not a participant).

Scope (keep tight)

• Add SQL migration: agreement_messages.sender_id (UUID, preferably FK/auth_users.id; backfill nullable OK for old rows).
• Document / add the migration under BE scripts/ (schema should live with the API that writes it).
• Fail agreement create if participant insert fails (do not leave orphan agreements without participants).
• Prefer mapping chat DB/validation errors to proper HTTP 4xx (not always 200 + { error }).

Out of scope

• Frontend wiring (separate FE issue)
• Realtime / WebSockets
• Rate limiting / MaxLength (nice-to-have later)
• Multi-wallet identity alignment (user_wallets vs auth_users.wallet_public_key)

Acceptance criteria

1. Applying the migration allows Nest to insert a message with sender_id + sender_wallet.
2. Creating an agreement always creates participant rows for both parties, or the create request fails.
3. Only JWT users who are creator/participant can GET/POST messages.
4. Manual check: User A creates agreement with User B’s wallet → B can list messages (empty) and A can send one → B sees it.

Related

• Companion FE issue: wire AgreementChat to Nest + persist UUID (link after creation)
• Existing Nest module: src/agreement-chat/

DoD

• PR on main with migration + create harden
• Short proof in PR (SQL applied + curl/Postman or integration test for messages)
• Closes #NN

[birdcoin0]

hi i want to work in this issue

[nurudeenheroic]

Hello! I understand what's needed and can deliver a solution that meets the project's standards. I'd love the opportunity to work on this issue.

[SudiptaPaul-31]

Hey Maintainer!!! My name is Sudipta Paul a very old contributor of GrantFox and other platform having quite a lot of experience in open source and working with full stack issues as well as very much proficient in writing contracts and would love to work on this issue and contribute to your project, May I be assigned to this task

[grantfox-oss]

🦊 GrantFox — @SudiptaPaul-31 has been assigned to this issue as part of the Official Campaign | FWC26 campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #86)
2. Your PR will be reviewed by the Thalos-Infrastructure maintainers

Good luck! Track your progress on GrantFox.

[ManuelJG1999]

🎉 Congratulations @SudiptaPaul-31 ! This issue has been assigned to you.

Before you start, make sure you understand the requirements. If you have any questions, ask us in our community chat:
https://t.me/ThalosOSSCommunity

Please keep us updated on your progress. If there's no activity or communication within 48 hours, the issue may be reassigned to another contributor.

Happy coding, and thanks for contributing to Thalos! 🐉

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox as part of the Official Campaign | FWC26 campaign!

@SudiptaPaul-31's PR #105 was approved and merged by @Kalchaqui.

🏆 @SudiptaPaul-31: You earned 40 FoxPoints for this contribution! Your current tier: Builder (1,524 total points). Track your full progress on GrantFox.

👏 Great work, @SudiptaPaul-31! Keep contributing to Thalos-Infrastructure.