Add insurance pool events to `docs/events.md`

[Levi-Ojukwu]

Description:

The docs/events.md file documents all events emitted by the ILN contracts, which off-chain indexers and frontends rely on to track protocol state changes. However, the insurance_pool contract emits three events that are completely undocumented:

1. enrolled(lp) — Emitted when an LP enrolls in the insurance program (either via explicit enroll() call or automatically on first deposit_premium()). Topic: (symbol!("enrolled"), lp). Data: ().

2. premium(lp, amount) — Emitted when an LP deposits a premium payment. The amount is the premium paid in stroops. Topic: (symbol!("premium"), lp). Data: amount: i128.

3. claimed(invoice_id, payout) — Emitted when a claim is processed for a defaulted invoice. The payout is the compensation amount credited to the LP. Topic: (symbol!("claimed"), invoice_id). Data: payout: i128.

These events are defined in contracts/insurance_pool/src/lib.rs:131-211 and are critical for the indexer service to track insurance pool activity.

Why it matters: Without documented events, the indexer service cannot correctly parse insurance pool events, and frontend developers cannot build features that display insurance enrollment, premium payments, or claim history.

Acceptance Criteria:

• Add a new section for Insurance Pool events in docs/events.md
• Document each event with: event name, topic schema, data schema, description, and example
• Follow the existing event documentation format used for invoice events
• Include the contract address topic pattern (if applicable)

Relevant Files: docs/events.md, contracts/insurance_pool/src/lib.rs:131-211

---

[Dayz-tech-co]

Hi, I'd like to work on this issue. I've gone through the description and acceptance criteria and I'm confident I can deliver it. I'll make sure every acceptance criterion is met and submit a clean, tested PR. Please assign it to me.

[miracleokaa]

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

Please assign this issue to me, i've gone through the task description and can deliver quickly.

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

[drips-wave]

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

🧑‍💻 @miracleokaa: 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 🌊

[grantfox-oss]

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

@miracleokaa's PR #624 was approved and merged by @Levi-Ojukwu.

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

👏 Great work, @miracleokaa! Keep contributing to Invoice-Liquidity-Network.

[drips-wave]

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

😎 @miracleokaa: You earned 100 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.