Option B is correct because plugin dependencies and releases must be versioned deliberately if the team wants reproducible behavior and a reliable rollback path. Claude Code’s plugin documentation supports explicit semantic versions in plugin manifests and marketplace entries, and the plugin system uses the resolved version as part of update detection and caching. Version constraints can also keep dependent plugins on a tested compatible range until the team intentionally upgrades.

The incident happened because the team could not determine which plugin version had previously worked. Explicit tracking solves that directly: record the version in project configuration, pin known-good releases where stability matters, test upgrades, and change versions through reviewed configuration updates. This creates traceability and makes regression isolation much faster.

Option A removes useful extension functionality instead of managing it. Option C treats third-party change as uncontrollable even though the platform provides version-management mechanisms. Option D automatically moving everything to the latest release increases change frequency and can reproduce the same regression problem.

Therefore, B is the correct configuration-management response. Relevant Study Guide topics: Claude Code plugins, semantic versioning, dependency constraints, reproducible configuration, controlled upgrades, rollback, and configuration management.