As a registry operator, I want burnup charts and per-node tracking in status reports to monitor data loading progress over time

[jordanpadams]

Summary

Add burnup chart visualizations and per-node product tracking to the registry status reporting pipeline so operators can monitor data loading progress trends over time and identify which nodes are contributing products.

Motivation

The existing status reports provide point-in-time counts of missing, staged, and loaded products but offer no trend visibility. A burnup chart showing loaded products over time, broken down by registry node, would help operators identify loading rate, progress toward completeness, and per-node contributions.

Acceptance Criteria

• generate_registry_status_reports.py generates burnup history CSVs (burnup_history.csv, burnup_by_node.csv) tracking loaded product counts over time
• Interactive HTML burnup chart (burnup_chart.html) is generated and committed to docs/status/
• Per-node loaded product CSVs (loaded_bundles_in_registry.csv, loaded_collections_in_registry.csv) are generated
• OpenSearch DSL query configs for per-node loaded products exist in conf/status/
• docs/status/README.md documents the new outputs

🤖 Generated with Claude Code