go through metric creation all related subsequent steps

[drifter089]

• api-endpoints are they representative of the metric look and remove unused, add two new
• metric templates make sure they are only source of truth
• ingestion transformer - pipeline to run and create in dev use analysis script and improve prompt in template directly then test again.
• goal are the calculations correct ? how to manage time for metric data and last time it was fetched data , currently most available data from api , goal time left
• are we integrating manual metric properly in the whole pipeline

[linear]

RYO-103

[coderabbitai]

📝 CodeRabbit Plan Mode

Generate an implementation plan and prompts that you can use with your favorite coding agent.

• Create Plan

Examples

• Example 1
• Example 2

---

🔗 Similar Issues

Possible Duplicates

• house keeping tasks #221

Related Issues

• Make metric extraction more robust with better field handling #189
• major clean up and updated claude.md and new agents #168

🔗 Related PRs

#69 - refactor: remove static metric fields in favor of template-based approach [merged]
#113 - feat: optimize dashboard metric creation with prefetch and parallel ops [merged]
#167 - feat: DB ingestion pipeline improvements (RYO-52) [merged]
#185 - feat: Google Sheets dedicated transformer system [merged]
#201 - feat: Enable manual metric data entry with check-in page [merged]

👤 Suggested Assignees

• drifter089

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord or schedule a call!