Frontend: Add Real-Time Collaborative Editing for Shared Project Configuration

[Smartdevs17]

Context

Enterprise merchants often have multiple team members managing payment configurations. Concurrent edits can lead to conflicts and data loss.

Current Limitation/Problem

Project configuration is single-user. When two team members edit settings simultaneously, last-write-wins causes silent data loss. There is no awareness of other users actions.

Expected Outcome

Real-time collaborative editing using Operational Transform (OT) or CRDTs, with presence indicators showing who is viewing/editing, conflict resolution, and edit history.

Acceptance Criteria

• Multiple users can edit project configuration simultaneously
• Edits are synchronized in real-time via WebSocket (<200ms latency)
• Presence indicators show active users with cursor positions
• Conflict resolution with automatic merging (operational transform)
• Edit history with per-user attribution and rollback capability
• Lock critical sections (API keys, webhook URLs) during edits
• Offline edits queued and synced on reconnection
• Visual diff showing pending and applied changes

Technical Scope

• frontend/src/components/collaboration/ - collaborative editing components
• Yjs or ShareDB CRDT library integration
• backend/src/websocket/collaboration.ts - WebSocket handler for OT
• Redis pub/sub for broadcasting edits across instances
• Prisma: ProjectEditHistory model
• Lock Service for critical section mutation prevention
• Edge cases: connection drops, conflicting changes, partial syncs, permissions

[akintewe]

@akintewe has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

I've been creating intricate forms and e-commerce systems for more than four years as a full-stack developer. I have designed inventory management systems for agricultural enterprises and have experience with image processing and large-scale state management. I have also worked on this project in the past.
My ETA is one hour, and I would love to work on this problem.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @akintewe to this issue.

[drips-wave]

Congratulations, @akintewe! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 30, 2026.

🧑‍💻 @akintewe: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊

[drips-wave]

This issue has been completed by @akintewe as part of the Stellar Wave Program's 6th Wave 🥳

😎 @akintewe: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.