Standardized event schema & indexing docs

[DevMuhdishaq]

Description
Off-chain consumers (dashboards, the market-data-streaming component) need a consistent, documented event schema across swaps, liquidity, staking, orders, and governance.

Direction

• Audit events.rs and each module's emissions; normalize topic naming and payload structs.
• Ensure every state-mutating public function emits a typed event with a versioned schema tag.
• Document the full event catalog in counter/EVENTS.md (topic, fields, emitting function).

Acceptance criteria

• Every mutating entry point emits at least one event (verified by test assertions).
• Event topics follow a single documented naming convention.
• EVENTS.md lists all events with fields and source functions.
• A test subscribes to and asserts event payloads for swap, add/remove liquidity, stake, and order placement.

---

[Okorie2000-code]

Hi maintainer, would love to work on this issue, i have already reviewed the description and will submit a clean PR. kindly assign.

[Okorie2000-code]

Hi maintainer, would love to work on this issue, i have already reviewed the description and will submit a clean PR. kindly assign.

[Tinna23]

can i please be assigned to this?

[grantfox-oss]

🦊 GrantFox — @Tinna23 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 #222)
2. Your PR will be reviewed by the StelTade maintainers

Good luck! Track your progress on GrantFox.

[grantfox-oss]

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

@Tinna23's PR #234 was approved and merged by @DevMuhdishaq.

🏆 @Tinna23: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (484 total points). Track your full progress on GrantFox.

👏 Great work, @Tinna23! Keep contributing to StelTade.