acu-update

/acu-update — Pipeline Update Tool

Brings existing pipelines up to the current template standard by applying structural patches defined in _templates/CHANGELOG.md. Never modifies domain-specific content. Always confirms before making any change.

Invocation

/acu-update                   # run against all pipelines in pipelines/
/acu-update ContentReview     # target a single pipeline by name

---

Protocol

Step 1: LOAD — Read current state

1. Read _templates/VERSION → store as CURRENT_VERSION
2. Read _templates/CHANGELOG.md → parse all patches: blocks from every version entry
3. Determine target set:
   • If a pipeline name was given (e.g., /acu-update ContentReview): target that pipeline only
   • If no pipeline given: read pipelines/CLAUDE.md to identify all pipeline directories and target all of them
4. Verify each target directory exists. If a named pipeline directory is not found, report: [ERROR] pipelines/{Name}/ not found — cannot update

---

Step 2: ASSESS — Determine what needs updating

For each target pipeline:

1. Check for pipelines/{Name}/.acu-meta.yaml:

   • Exists: read template_version field → store as PIPELINE_VERSION
   • Does not exist: set PIPELINE_VERSION = "none" (PRE-VERSIONING)

2. Compare PIPELINE_VERSION to CURRENT_VERSION:

   • Match: report {Name}: already at {CURRENT_VERSION} — nothing to do and skip
   • Mismatch or PRE-VERSIONING: proceed to planning

3. Determine which patches apply:

   • PRE-VERSIONING (version = "none"): all patches from ALL changelog entries apply
   • Outdated (version exists but doesn't match): only patches from changelog entries whose version is strictly AFTER PIPELINE_VERSION apply (compare version strings as YYYY.MM.DD.N — higher date or higher N is newer)

4. Read .acu-meta.yaml's known_deviations list (empty list if file doesn't exist). Any patch whose id maps to a known deviation will be suppressed before planning.