CC Milestone Consolidation — Sprawl → Rolling Umbrella

OrchestKit's cc-watch cron filed one GitHub milestone per upstream CC version. This explorer shows why that sprawls, and how a single rolling CC adoption umbrella (plus an idempotent self-heal sweep) fixes it — without losing per-version traceability.

Upstream CC versions filed

8 versions

OLD model one milestone / version

Each version → a new CC X.Y.Z adoption milestone, most with 1–2 issues.

milestones: 8

NEW model one rolling umbrella

All versions file into one permanent CC adoption; real bundles graduate to M###.

milestones: 1

Traceability is preserved. Collapsing milestones loses nothing — dedup & per-version history live outside the milestone:
• Key: <slug>+<version> body marker (the filer dedups on this, not the milestone)
• shared/cc-snapshots/<version>.md (raw per-version changelog bullets)
• latest_new_version in gh-issue-args.json (keeps snapshot-PR titles unique)

The change, in one diff + one sweep

copied ✓

Legend: ■ rolling umbrella · ■ graduated M### human bundle · ■ per-version sprawl milestone (swept & closed). Sweep is idempotent: a steady state is a no-op.