Store per-campaign startup parameters

[Copilot]

• Add CampaignStartupParams struct to infra/types/src/lib.rs (num_cpus, duration_secs, engines, sanitizers, commit_hash)
• Add commit_hash: String to EnvironmentParams in fuzzor/src/env/mod.rs
• Add get_num_cpus() method to Environment trait in fuzzor/src/env/mod.rs
• Update CampaignSchedulerInput in fuzzor/src/project/scheduler.rs to include commit_hash
• Update all schedulers to store and pass commit_hash in EnvironmentParams
• Update handle_new_build in fuzzor/src/project/mod.rs to pass commit hash
• Add store_startup_params to HarnessState trait and implement in PersistentHarnessState (writes startup_params.json to campaign directory)
• Implement get_num_cpus() in DockerEnv (returns machine.cores.len())
• Add commit_hash and duration fields to Campaign struct; update Campaign::new() and Campaign::run() to store startup params at campaign start
• Add test for store_startup_params in harness.rs
• All 5 tests pass, CodeQL shows 0 alerts
• Squashed "Initial plan" empty commit

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Store per-campaign startup parameters</issue_title>
<issue_description>For each campaign we should store (in addition to the coverage summary and stats we already store) the startup parameters, such as:

• Number of CPUs
• Duration
• Config (fuzzers, sanitizers, ...)
• Commit hash of the target binary</issue_description>

<agent_instructions>make no mistakes</agent_instructions>

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

• Fixes Store per-campaign startup parameters #85

---

💬 Send tasks to Copilot coding agent from Slack and Teams to turn conversations into code. Copilot posts an update in your thread when it's finished.

[dergoegge]

@copilot remove the "Initial plan" commit, otherwise this is rfm

[marcofleon]

lgtm