Skip to content

docs(sdlc): bump CC baseline v2.1.150 → v2.1.159 (closes #367, refs #368)#370

Merged
BaseInfinity merged 1 commit into
mainfrom
feat/367-cc-baseline-v2.1.159
Jun 1, 2026
Merged

docs(sdlc): bump CC baseline v2.1.150 → v2.1.159 (closes #367, refs #368)#370
BaseInfinity merged 1 commit into
mainfrom
feat/367-cc-baseline-v2.1.159

Conversation

@BaseInfinity
Copy link
Copy Markdown
Owner

Summary

cc-version-drift.yml (PR #354) opened #367 when our <!-- Claude Code Baseline --> marker fell 9 versions behind npm latest. Review of v2.1.151–v2.1.159 changelog and selective adoption of wizard-relevant features.

Per-release classification

Version Wizard-relevant? Decision
v2.1.151 n/a (skipped — not in changelog) none
v2.1.152 Maybe (hook event additions, unspecified) note in baseline row
v2.1.153 No (plugin marketplace internal) none
v2.1.154 YES — Opus 4.8 here, defaults to high effort, dynamic workflows, 4.8 fast mode cost reductions note availability; hold model recommendation per #365 A/B
v2.1.155 n/a (skipped) none
v2.1.156 No (bug fix for 4.8 thinking blocks) none
v2.1.157 YES.claude/skills plugin auto-load (no marketplace), claude plugin init scaffold, agent field in settings.json honored, tool_decision telemetry includes tool_parameters with OTEL_LOG_TOOL_DETAILS=1, EnterWorktree mid-session switching, worktrees unlocked when agent finishes note in baseline row; no code change (our skills already live in .claude/skills/, telemetry is opt-in)
v2.1.158 No (Bedrock/Vertex/Foundry auto mode via CLAUDE_CODE_ENABLE_AUTO_MODE=1) none
v2.1.159 No (internal infra only) none

Why minimal-adoption is the right call here

  • .claude/skills auto-load (v2.1.157): our skills already live there via cli/init.js. CC's runtime behavior change doesn't require any wizard code change — users get the auto-load for free.
  • Opus 4.8 (v2.1.154): per Hold Opus 4.7 → 4.8 model-pin bump 48-72h for sentiment, then A/B via local-shepherd #365's gate-2 deferral. Sentiment is converging positive but the system-card-flagged prompt-injection regression (Gray Swan +60% vs 4.7) hits wizard hook-heavy use. Model recommendation stays at 4.7 until A/B parity proven.
  • tool_decision telemetry (v2.1.157): opt-in observability via env var, not a wizard mandate. Noted for users who want it.
  • Everything else is bug fixes, deployment-channel additions, or internal CC infra — out of wizard scope.

Companion #368 triage

12 entries total: 10 duplicates from #359 (already closed last week with the same triage outcome) + 2 new:

Deprecation re-verification (zero usage in repo):

  • context-1m-2025-08-07 — 0 hits
  • claude-3-haiku-20240307 — 0 hits
  • managed-agents-2026-04-01 header — 0 hits

#368 will be closed with the triage comment after merge.

Verification

  • Drift workflow goes silent: scripts/cc-drift-check.sh --baseline v2.1.159 --latest 2.1.159 returns alert:false threshold_exceeded:false. Post-merge cc-version-drift.yml cron will skip the issue-update step.
  • Test plan:
    • tests/test-cc-drift-check.sh — 18/18
    • tests/test-cc-version-drift.sh — 22/22
    • tests/test-doc-consistency.sh — 41/41
    • tests/test-self-update.sh — 153/153
    • tests/test-hooks.sh — 160/160
    • tests/test-docs-usability.sh — 29/29
    • CI green on validate
    • Squash-merge
    • Manual gh workflow run cc-version-drift.yml post-merge to verify silent

Closes

)

cc-version-drift.yml workflow opened #367 when our baseline fell 9 versions
behind npm latest. Review of v2.1.151–v2.1.159 changelog:

| Version | Wizard-relevant? | Decision |
|---------|------------------|----------|
| v2.1.151 | (skipped — not in changelog) | n/a |
| v2.1.152 | Maybe (hook event additions, unspecified) | note in baseline row |
| v2.1.153 | No (plugin marketplace internal) | none |
| v2.1.154 | YES — Opus 4.8 here, defaults to high effort | note availability; hold model recommendation per #365 A/B |
| v2.1.155 | (skipped) | n/a |
| v2.1.156 | No (bug fix for 4.8 thinking blocks) | none |
| v2.1.157 | YES — `.claude/skills` plugin auto-load, `claude plugin init`, agent field honored, tool_decision telemetry tool_parameters | note in baseline row; no code change (our skills already live in .claude/skills/) |
| v2.1.158 | No (Bedrock/Vertex auto mode) | none |
| v2.1.159 | No (internal infra) | none |

Minimal-adoption call: bump the baseline marker + recommended row to reflect
what the new version unlocks. No code changes needed — the wizard-relevant
features in v2.1.157 either work for us already (`.claude/skills` location)
or are opt-in observability (`OTEL_LOG_TOOL_DETAILS=1`). Opus 4.8 is gated
on #365 A/B, so model recommendation stays at 4.7.

Companion #368 triage (will close with comment after merge): 12 entries
total, 10 are duplicates from #359 (already closed); 2 new (Managed Agents
multi-agent + Opus 4.8) are both no-op for the wizard (managed-agents API
path / model bump gated on #365).

Verified locally:
- `scripts/cc-drift-check.sh --baseline v2.1.159 --latest 2.1.159` returns
  `alert:false` → workflow will go silent post-merge.
- test-cc-drift-check 18/18, test-cc-version-drift 22/22, test-doc-consistency
  41/41, test-self-update 153/153, test-hooks 160/160, test-docs-usability 29/29.
@BaseInfinity BaseInfinity merged commit f8d19db into main Jun 1, 2026
3 checks passed
@BaseInfinity BaseInfinity deleted the feat/367-cc-baseline-v2.1.159 branch June 1, 2026 21:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

CC version drift: baseline v2.1.150, latest v2.1.159 (9-release gap)

1 participant