774716ce2cdee28133d463ae865f4c67bef68fb4 ships 11 plugins and 61 skills.
The new catalog ships five plugins and 28 skills.
The reductions equal 55% of plugins and 54% of marketplace skills after rounding.
Plugin replacements
Software Engineering, Kotlin Engineering, IntelliJ Plugin Development, Developer Tooling, and Repository Knowledge keep their identifiers.
Each changed bundle receives a major version increase.
Developer Tooling contains no hooks. The consolidation adds no automatic source, Pkl, API-context, or skill-read behavior.
Skill replacements
Merged skills keep their distinct contracts as task-routed references, scripts, fixtures, or focused procedures.
Compiler proof, negative cases, OpenAPI examples, CLI contracts, diagnostics, and OKF helpers remain under their new owners.
Removed distribution
The catalog removesagents-sdk, frontend-design, grill-me-with-docs, migrate-to-codex, react-best-practices, refactor, stripe-best-practices, and workflow.
These surfaces duplicate general procedures or target work outside the Kotlin-first scope.
Git history preserves their source and provenance.
The previous uv foundation already retired shell authoring and shell data-pipeline skills.
Automation remains Python with uv, PEP 723, locks, strict Pyright, Ruff, and pytest.
The parent-shell adapter stays only for history that its child process cannot read.
Consumer changes
Profiles now select the surviving bundles. Thepkl-checked-repository profile keeps its identifier for callers but selects guidance only.
Custom automatic Pkl checks need an explicit hook composition.
The default Kotlin selection remains software-engineering plus kotlin-engineering.
After authorized publication, install the replacement bundles through the host.
Disable retired bundles before a fresh session.
Reapply selected profiles and examine hook trust.
Older installed caches and unrelated configuration layers do not change through this source edit.
Golden fixtures name the new routes. They do not prove model behavior.
Historical records keep their original identities and evidence.
Two historical routes receive NEEDS_REPLAY_CASE status because their replacement skills lack a fresh replay.