Analytics summary CSV concatenates three heterogeneous sections with comment lines: no RFC 4180-compliant output exists

[usmanimamu17-create]

Problem

export_analytics_summary (app/utils/analytics_exporter.py) builds a single CSV by concatenating three differently-shaped sections:

buffer.write("# KPI Metrics\n")
kpi_writer = csv.DictWriter(buffer, fieldnames=summary["kpi"].keys())
...
buffer.write("# Trends Data\n")
trend_writer = csv.DictWriter(buffer, fieldnames=trend_data[0].keys())

Consequences:

• No standard parser can consume the file: RFC 4180 CSVs have one header row and uniform columns; this file has #-prefixed section headers, blank separator lines, and three different column sets, so csv.reader, Excel, and analytics importers either fail or misalign rows.
• The JSON form of the same function is clean and structured ({"kpi": ..., "trends": [...], "trend_count": N}), so the CSV path provides a strictly worse contract for the same data.
• Empty trends fall back to a hardcoded header ("date,total_outages,violations,rewards,penalties") that only matches SLATrendPoint by luck; any future field addition silently produces a malformed file.

Root cause

The CSV branch was written as "dump each section" rather than a defined CSV schema.

Why this is architecturally hard

1. A compliant CSV needs a single unified schema (e.g. one row per trend point with KPI values repeated, or a documented multi-table layout like table:column prefixing) — a format decision that consumers (dashboard exports, BI tooling) must agree on.
2. export_dashboard_kpi and export_trends each already produce valid single-table CSVs; the summary function could reuse them or return JSON only, which is a product decision about what "export" means.
3. The OpenAPI snapshot documents format=csv as an option; changing the output shape or removing CSV is a contract change for the frontend export UI.

Proposed design

Either produce one RFC 4180-compliant CSV with a unified schema (documented), or make format=csv return the KPI CSV (and document trends/aggregation as JSON-only); add tests that parse the CSV with csv.reader and assert uniform columns.

Acceptance criteria

Service

• CSV output parses with a standard CSV reader into uniform rows.
• Empty datasets produce the same schema as non-empty ones.

Tests

• A parser test asserts uniform columns for populated and empty data.
• Existing analytics export tests pass.

Out of scope

The trend-empty hardcoded header mismatch (resolved by the same fix) and streaming.

Getting started

pytest tests/test_sla_typing.py -q
make typecheck

Good first files to read: app/utils/analytics_exporter.py, app/api/v1/endpoints/sla.py.

[Duyicoda]

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

Hi! I’m a full-stack developer with a strong blockchain background. I’d love to handle this issue and can deliver a clean, reliable solution. Kindly assign it to me.

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

[WALEY-OPS]

@WALEY-OPS has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hi Maintainer.
Let me work on this.

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

[classicjoshua1-creator]

@classicjoshua1-creator has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hello! I’m interested in contributing to this issue and can dedicate time to implementing the required changes properly.

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

[Teejay2696]

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

I’ve thoroughly reviewed the requirements and can work on fixing the issue while ensuring the implementation meets the acceptance criteria.

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

[Halo-chains]

@Halo-chains has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Can I please work on this

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

[MRTEEworld02]

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

Please could you assign me this issue

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

[drips-wave]

Congratulations, @Halo-chains! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.

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