Guard JSON parsing in Ashby fetcher against non-JSON responses

[Copilot]

Ashby API can return non-JSON responses (HTML error pages) even with 200 OK, causing response.json() to throw and halt the entire ingestion pipeline.

Changes

• Wrapped JSON parsing in try/catch to isolate parse failures
• Log slug and status code on parse errors for debugging
• Return empty array on failure to allow processing remaining companies

try {
  const result: AshbyPublicResponse = await response.json();
  const postings = result.jobs ?? [];
  return postings.map((posting) => ({ company: companyName, slug, posting }));
} catch (error) {
  log('fetch', 'error', `  Failed to parse JSON for ${slug} (status ${response.status}): ${error}`);
  return [];
}

One malformed response no longer stops Step 1 execution.

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.