Add resume_on_start option to control crawl resumption on restart

[Copilot]

Arachnado currently auto-resumes all jobs with status "shutdown" or "running" on server restart. This adds a configuration option to control that behavior.

Changes

• Config option: Added resume_on_start (default: 1) in defaults.conf
• CLI flags: Added --resume-on-start and --no-resume-on-start for runtime override
• Logic: Conditionally calls domain_crawlers.resume(job_storage) in main() based on option value

Usage

Config file:

[arachnado]
resume_on_start = 0  # Disable auto-resume

Command line:

arachnado --no-resume-on-start  # Override config, disable resume

Default behavior unchanged (auto-resume enabled) for backward compatibility.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Add an option to continue crawls after restart</issue_title>
<issue_description></issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes Add an option to continue crawls after restart #5

---

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

[github-actions]

This PR has been marked stale and will be closed in 7 days unless updated.