Three code-quality issues from review thread 3838367404 plus stale generated files from a concurrent article merge.

Code fixes

• mcp-client.ts — performPost().json() non-JSON resilience
  JSON.parse(responseBody) was called unconditionally on non-2xx responses. If the server returns HTML/plain-text (e.g. rate-limit page), callers got an opaque SyntaxError. Now wrapped in try/catch with a structured error including status code and body snippet:

  json: async () => {
    try {
      return JSON.parse(responseBody) as unknown;
    } catch {
      throw new Error(`HTTP ${raw.status} ${raw.statusText}: non-JSON response body: ${responseBody.slice(0, 200)}`);
    }
  },

• monthly-review.ts — fix JSDoc step order
  Header comment described the 5-step pipeline with steps 2 (get_dokument_innehall) and 3 (search_anforanden) swapped relative to the implementation. Updated to match actual execution: Step 2 = typed metadata fetchers, Step 3 = get_dokument_innehall, Step 4 = search_anforanden.

• month-ahead.ts — document search_dokument as conditional in REQUIRED_TOOLS
REQUIRED_TOOLS listed search_dokument unconditionally, but it is only invoked when get_calendar_events returns empty. Added inline comment and JSDoc note to prevent false validation failures on calendar-populated runs.

Generated file sync

Regenerated data/news-articles.json, all 14 news/index*.html files, and sitemap.xml to reflect articles on this branch after a concurrent article merge to the base affected those files.

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