Implement event-sourced strategy lifecycle audit from recommendation to execution to snapshot

[edehvictor]

Summary

Track strategy lifecycle changes end to end so maintainers can trace why a recommendation was produced, queued, executed, or blocked.

Scope

• Define strategy lifecycle event types
• Link recommendation, risk checks, queue events, execution results, and snapshots
• Add query support for historical inspection

Acceptance Criteria

• A strategy path can be reconstructed from stored events
• Blocked and successful executions are both traceable

[github-actions]

🏷️ Issue Needs Triage

This issue has been marked as needs-triage and will be reviewed by maintainers.

What happens next:

• A maintainer will assess the issue and add appropriate labels
• The issue may be assigned to someone or marked as good-first-issue
• If it's a duplicate, it will be closed with a reference

Thank you for opening this issue! 🎯

[udeachudivine-spec]

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

hi maintainer i would like to work on this issue

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

[pre-cious-Igwealor]

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

Hi, my name is Precious Igwealor, and I am a fullstack and smart contract developer skilled in React, Next.js, JavaScript, TypeScript, Tailwind CSS, and Soroban. For this task, I will:

1. Define a typed event schema covering all strategy lifecycle stages: recommendation produced, risk check passed/blocked, queue entry, execution result, and snapshot capture, with each event linked by a shared strategy_id for full path reconstruction.
2. Implement the event sourcing pipeline to emit and persist lifecycle events at each stage, ensuring both blocked and successful execution paths are captured with sufficient context (reason, timestamp, actor) for root cause tracing.
3. Expose query APIs for historical inspection, supporting filtering by strategy_id, event type, and time range so maintainers can reconstruct the full lifecycle of any recommendation end to end.
4. Write tests verifying complete path reconstruction for a happy-path execution, a risk-check-blocked scenario, and a partially executed strategy, confirming no lifecycle gaps in stored events.

ETA: 10 hours

ℹ️ Repo Maintainers: To accept this application, review their application or assign @pre-cious-Igwealor to this issue.

[drips-wave]

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

🧑‍💻 @pre-cious-Igwealor: 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 @pre-cious-Igwealor as part of the Stellar Wave Program's 6th Wave 🥳

😎 @pre-cious-Igwealor: 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.