Add organization-scoped slash-rate and capital-at-risk analytics endpoint in src/routes/orgAnalytics.ts

[1nonlypiece]

📌 Description

src/routes/orgAnalytics.ts exposes basic org analytics but has no endpoint
that reports slash rate (fraction of vaults that ended in slash_on_miss)
and capital-at-risk (USDC currently locked in active vaults) for an
organization. These are the two numbers an operator needs to gauge protocol
health for their org.

This issue adds a dedicated analytics endpoint computing both metrics with
date-range filtering.

Goal: give org operators a slash-rate and capital-at-risk view filtered by
a date range, derived from persisted analytics storage.

🎯 Requirements and Context

• Must be org-scoped and tenant-isolated.
• Date-range boundaries must be handled in UTC (reuse src/utils/timestamps.ts).
• Slash rate must exclude in-flight vaults from the denominator correctly.
• Capital-at-risk must reflect net staked amounts, not gross.

🛠️ Suggested Execution

1. Fork the repo and create a branch

git checkout -b feature/org-slash-rate-analytics

2. Implement changes

• Add GET /api/orgs/:orgId/analytics/risk to src/routes/orgAnalytics.ts.
• Add aggregation to src/services/analytics.service.ts.
• Document the metric definitions in docs/analytics-metrics.md.

3. Test and commit

• Add src/tests/orgAnalytics.risk.test.ts run with bun test.
• Cover edge cases: zero vaults, all-active (denominator), date boundary
  inclusivity, and cross-org isolation.

Example commit message

feat: org slash-rate and capital-at-risk analytics endpoint

✅ Guidelines

• Minimum 95% test coverage on the new/changed lines.
• Clear, reviewer-friendly documentation.
• No regressions on existing analytics endpoints.
• Timeframe: 96 hours.

🏷️ Labels

type-feature · area-backend · type-testing · MAYBE REWARDED · GRANTFOX OSS · OFFICIAL CAMPAIGN

💬 Community & Support

• Join the Disciplr contributor Discord to coordinate, ask questions, and get
  unblocked fast: https://discord.gg/xvNAvMJf
• Please introduce yourself in the channel before you start so we can avoid
  duplicate work, pair you with a reviewer, and get your PR merged quickly.
• Maintainers actively triage this channel and aim for fast, clear, respectful
  reviews — reach out any time you're blocked.

[wonderfulmarv01]

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

i will like to work on this please

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

[grantfox-oss]

🦊 GrantFox — @wonderfulmarv01 has been assigned to this issue as part of the Official Campaign campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #713)
2. Your PR will be reviewed by the Disciplr-Org maintainers

Good luck! Track your progress on GrantFox.

[drips-wave]

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

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