Event Sourcing and Player Action Audit Log

[Mkalbani]

Description

Introduce an event sourcing pattern for player actions so every significant game event is stored as an immutable log entry. This powers replay, debugging, anti-cheat investigation (extends #18), and verifiable on-chain reputation when integrated with mesh-contract.

Acceptance Criteria

• PlayerEvent entity: id, userId, sessionId, eventType, payload (JSONB), timestamp
• Events emitted for: puzzle.started, puzzle.solved, puzzle.abandoned, hint.used, answer.submitted, achievement.unlocked
• Events published to an internal NestJS EventEmitter2 bus and persisted to DB asynchronously
• GET /players/:id/events — paginated event history (admin only)
• GET /sessions/:id/events — full event replay for a session (admin/owner only)
• Events are append-only — no update or delete on PlayerEvent table
• Aggregates (e.g., total hints used, solve time) computable from event log
• Tests for: event emission on each trigger, append-only enforcement, aggregate calculation

Technical Notes

• Use @nestjs/event-emitter for internal bus
• Persist asynchronously via a queue to avoid blocking the request cycle
• Index on (userId, eventType, timestamp) for efficient querying
• JSONB payload schema validated per eventType at write time

[drips-wave]

This issue has been added to the Stellar Wave Program and is worth 150 Points.

🧑‍💻 Interested in contributing? Apply to work on this issue on Drips Wave, earn points, and receive rewards.

Warning

Only applications submitted via the apply link above will be considered. Please do not apply by commenting on the issue or opening a PR directly.

🤠 Repo maintainers: You can manage this issue's Points and Complexity on your Maintainer Dashboard here. Please keep an eye on applications and respond quickly 💙

ℹ️ Learn more about Drips Wave

[OthmanImam]

@OthmanImam has applied to work on this issue as part of the Stellar Wave Program's 3rd wave.

Hi Maintainer,

I’m Usman Adamu, a full-stack developer, and I’d like to contribute to the task. I’ll implement it carefully and efficiently thoroughly understand requirements and edge cases
Communicate promptly about suggestions or improvements. And I will provide regular progress updates and address blockers
Align with project goals through feedback and clarification.

Thank you,

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

[drips-wave]

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

🧑‍💻 @OthmanImam: 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 @OthmanImam as part of the Stellar Wave Program's 3rd Wave 🥳

😎 @OthmanImam: You earned 150 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.