# CC 2.1.138 floor bump — W4 closeout (M134)

Bumps OrchestKit's CC support floor from `2.1.132` to `2.1.138` — the closeout for milestone M134. Versions 2.1.133, 2.1.136, 2.1.137, 2.1.138 exist upstream; 2.1.134 and 2.1.135 do not. The original 2026-05-07 `manual_override` (latest-only, 12-week window) carries forward unchanged — expires 2026-08-07.

2.1.132 2.1.133 2.1.134 2.1.135 2.1.136 2.1.137 → 2.1.138 · NEW FLOOR

## What changes floor bump only — no new feature entries

File | Change
--- | ---
`shared/cc-support.json` | `latest` & `supported_floor` → `2.1.138`, `drop_after` → `2.1.137`. `manual_override` (expires 2026-08-07) untouched.
`src/hooks/src/lib/cc-version-matrix.ts` | `MIN_CC_VERSION` → `2.1.138` (stamper). No feature entries added — matrix still ends at 2.1.132.
`CLAUDE.md` | Version section CC floor → `2.1.138` (stamper).
`src/skills/doctor/references/version-compatibility.md` | Overview line → `2.1.138` (stamper).
`.github/workflows/plugin-validation.yml` | Plugin-validate CC pin → `2.1.138`.
`src/hooks/src/__tests__/lib/cc-version-matrix.test.ts` | "is 2.1.132" → "is 2.1.138". "no missing features" probe → 2.1.138. Counts unchanged (392).
`src/hooks/src/__tests__/lifecycle/cc-version-check.test.ts` | "matrix latest" probe → 2.1.138.
`tests/fixtures/cc-changelogs/synthetic.md` | Synthetic above-floor heading: 2.1.133 → 2.1.139 (must stay above current latest).
`tests/integration/test-cc-release-watch.sh` | Pre-populates 133/136/137/138 alongside earlier versions; new-version probe → 2.1.139.
`tests/security/test-mcp-deny-case.sh` | "floor at 2.1.132" comment → "floor at 2.1.138".
4 skill `references/*.md` + SKILL.md | Inline "our floor is 2.1.132" load-bearing lines → 2.1.138. Section headers about features added in 2.1.132 (historical) untouched.
`plugins/ork/…` + `docs/site/lib/generated/…` | Auto-regenerated by `npm run build`.

## Source-of-truth diff

    {
      "latest": "2.1.132",            // → "2.1.138"
      "supported_floor": "2.1.132",   // → "2.1.138"
      "drop_after": "2.1.131",        // → "2.1.137"
      "manual_override": {
        "reason": "Bolder bump per 2026-05-07 decision — gates on
           CLAUDE_CODE_SESSION_ID (2.1.132) ...",   // unchanged (historical)
        "expires": "2026-08-07"                     // unchanged (still future)
      }
    }

`cc-support-window-bump.yml` honors the unexpired override and would have opened an info-only PR; this PR is a manual closeout for M134 instead. The original override reasoning (CLAUDE_CODE_SESSION_ID, parallel-shell fanout, sub-agent prompt-cache reduction) still applies — all gated features are now strictly older than the new floor.

## Versions in scope

### 2.1.133

Adoption tracked under M132. Issues filed against the per-version "CC 2.1.133 adoption" milestone via cc-release-watch.

### 2.1.134 / 2.1.135

No upstream release. Skipped — not in `shared/cc-snapshots/`, not in CC GitHub Releases.

### 2.1.136

Adoption tracked under M135.

### 2.1.137

Adoption tracked under M133 (W3 recovery).

### 2.1.138 — new floor

Closeout. Adoption issues continue in their respective milestones; the floor declaration here just unlocks reliance on those features without compat checks.

Risk: who breaks?

Anyone running CC `≤ 2.1.137` sees the doctor warning `Claude Code X.Y.Z is below OrchestKit's supported floor (2.1.138)`. Hooks degrade gracefully via fallback paths. The `manual_override` still expires 2026-08-07 (~3 months). After expiry, `cc-support-window-bump.yml` resumes the standard `latest + 3` policy — whichever version is latest at that point becomes the floor under default arithmetic.

Test status

`npm run build` · `npm run test:skills` · `npm run test:agents` · `npm run test:manifests` · `npm run test:security` · `npm run typecheck` all green pre-push. Hook unit tests (`cc-version-matrix.test.ts`, `cc-version-check.test.ts`) updated to match new floor — matrix entry count assertion unchanged (no new feature entries in this PR).