Wrap fetch() in try/catch to handle network failures gracefully

[Copilot]

The fetchCompanyJobs function lacked error handling around the fetch() call. With the expanded slug pool, a single DNS timeout, connection reset, or network error would abort the entire Step 1 run instead of continuing to the next company.

Changes:

• Wrapped fetch() and response.json() in try/catch block
• Network failures now log error and return [], allowing iteration to continue
• Error message includes slug and exception details for debugging

try {
  const response = await fetch(url.toString(), { ... });
  if (!response.ok) {
    log('fetch', 'warn', `  Ashby API returned ${response.status} for ${slug}`);
    return [];
  }
  const result: AshbyPublicResponse = await response.json();
  return result.jobs?.map(...) ?? [];
} catch (error) {
  log('fetch', 'error', `  Network error fetching ${slug}: ${error instanceof Error ? error.message : String(error)}`);
  return [];
}

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.