pj c63a2e4897 fix(campaign): record both clocks a run was measured on ...

Duration came from the monotonic clock, which does not advance while a host
sleeps: one calibration run under-reported by about 15 minutes. A run now
carries monotonic_millis for how long it worked and wall_clock_millis for how
much time passed, which is what makes a sleep visible at all.

Claude-Session: https://claude.ai/code/session_01A5KmftdEJ49A9z5mF5ESrX

2026-08-14 17:43:12 +05:30

..

campaign_test.go

fix(campaign): record both clocks a run was measured on

2026-08-14 17:43:12 +05:30

campaign.go

fix(campaign): record both clocks a run was measured on

2026-08-14 17:43:12 +05:30

end_to_end_test.go

fix(campaign): signal a timed-out run so it reaps its sidecar

2026-08-14 17:27:13 +05:30

main_test.go

experiment instrumentation: step budgets, arm labels, campaign runner (#72)

2026-08-12 22:20:31 +05:30

main.go

experiment instrumentation: step budgets, arm labels, campaign runner (#72)

2026-08-12 22:20:31 +05:30

manifest_test.go

experiment instrumentation: step budgets, arm labels, campaign runner (#72)

2026-08-12 22:20:31 +05:30

manifest.go

experiment instrumentation: step budgets, arm labels, campaign runner (#72)

2026-08-12 22:20:31 +05:30

seeds_test.go

experiment instrumentation: step budgets, arm labels, campaign runner (#72)

2026-08-12 22:20:31 +05:30

seeds.go

experiment instrumentation: step budgets, arm labels, campaign runner (#72)

2026-08-12 22:20:31 +05:30

summary_test.go

feat(campaign): count dispatched actions, not steps

2026-08-12 23:43:19 +05:30

summary.go

feat(campaign): count dispatched actions, not steps

2026-08-12 23:43:19 +05:30