📋 CC 2.1.186 Release-Integration — Plan Playground

The CC-release pipeline already exists and fired. The gap is triage precision, not plumbing. · interactive plan-viz · generated by /ork:visualize-plan
sort:
low risk med high

🔴 NOW — over-fires (11 issues, 8 false "breaking")

CHANGELOG.md (upstream)
  ▼ cc-release-watch.mjs   snapshot + gaps
  ▼ cc-triage.mjs          LLM extract
  validateAndScore (:403)  breaking → 20 ALL
    ✗ NO plugin-relevance gate   ◀── THE GAP
  ▼
cc-adoption-gaps.json (:690)
  ▼
cc-file-adoption-issues.sh  (≥10 floor)
  ▼
11 issues  ·  8 mislabeled breaking/20

🟢 WITH verify gate (#3) + ceiling linter (#4)

CHANGELOG.md (upstream)
  ▼ cc-release-watch.mjs   snapshot + gaps
  ▼ cc-triage.mjs          LLM extract
  validateAndScore (:403)
  ▼ [+] plugin-relevance prefilter
      DOWNGRADE (not drop): cap < 10
  ▼
cc-adoption-gaps.json   real items only
  ▼
cc-file-adoption-issues.sh  (≥10 floor)
  ▼
~2 issues  ·  real adoption only
[~] CC body ceiling-linter guards 147 prose strings
A drop would be invisible (no issue, no signal) — strictly worse than the over-fire it cures. The gate therefore downgrades score below the filer's floor (cc-file-adoption-issues.sh:78-80), keeping every item greppable in cc-adoption-gaps.json.
#1 CLOSING PR ───────────────▶ clears 6 live false-positives        (independent · do now)
     │  traps: comma-list close · playground-gate · stray-ref closes #2619

#3 VERIFY GATE ──────┬───────▶ #5 SOP   (SOP = "process theater" WITHOUT #3)
   root cause · H val│
                     └───────▶ stops the next release over-firing

#4 LINTER + SCHEMA ──┬───────▶ #2 ADOPT #2619   (else silent body-drift; no linter sees it)
                     └───────▶ #5 SOP "subtract" step  (needs a backstop before mass-edit)

#2 ADOPT #2619 ──────────────▶ the ONE genuine feature: claude mcp login/logout

recommended:   1️⃣  →  3️⃣  →  4️⃣  →  2️⃣  →  5️⃣
              clear   fix   guard  adopt  document