fix: restore backward-compatible fields in last-generation.json

[Copilot]

The realtime-monitor run restructured news/metadata/last-generation.json, silently dropping generated_at, workflow, run_id, and mcp_data_source — fields that existing workflows and scripts depend on.

Changes

• news/metadata/last-generation.json — added backward-compatible aliases alongside the new schema fields:
  • generated_at mirrors timestamp
  • workflow: "news-realtime-monitor"
  • run_id: null (not captured at generation time)
  • mcp_data_source object restored (status, sources, accessed_at)

{
  "timestamp": "2026-02-26T12:05:00.000Z",
  "generated_at": "2026-02-26T12:05:00.000Z",
  "workflow": "news-realtime-monitor",
  "run_id": null,
  "type": "realtime-monitor",
  ...
  "mcp_data_source": {
    "status": "live",
    "sources": ["riksdag-regering-mcp"],
    "accessed_at": "2026-02-26T12:05:00.000Z"
  }
}

New fields (timestamp, type, data_sources, events_detected) are preserved unchanged. Both old and new consumers read valid values.

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.