🦅 ContentHawk Campaign - Allow completed content campaigns to be re-executed from existing snapshots

[ssw-yakshaver]

Requested by: @Calinator444 via YakShaver.ai 🦬
cc: @Calinator444, @calumjs, @Lewkans

Hi Team!

  🟥  Watch the video (1 min 37 sec)

Pain

Currently, ContentHawk agentic workflows create snapshot files and complete content campaigns with no way to rerun them once finished. Introduce a capability to move a completed snapshot back to an in-progress state, reassess the associated file list, include any newly relevant files, and reprocess the entire list to generate new or updated PBIs as needed.

Acceptance Criteria

1. A completed content campaign snapshot can be moved back to an in-progress state.
2. When rerun, the system reassesses the repository to identify any additional files that should be included.
3. All files in the snapshot are rechecked during the rerun.
4. New PBIs are generated when new issues are identified.
5. Re-running a content campaign does not affect existing runs
6. Re-run workflow is distributed by the installer

[Calinator444]

I'm working on an improved skill for running content hawk campaigns. It includes a form for starting new campaigns, and viewing the status of current campaigns.