Claude Code adoption: where OrchestKit stands

Live data, 2026-08-24 (npm registry, GitHub, shared/cc-support.json, shared/cc-adoption-gaps.json). The support floor is deliberately frozen; latest_known is how far our triage has verified; upstream is what npm ships today.

2.1.220support floor (frozen by owner override until 2026-11-20)

2.1.238latest_known: highest version triaged

2.1.241upstream latest (2026-08-22); 239, 240, 241 unsnapshotted

29open feature issues across 11 versions

8without auto-filed key: 4 pipeline failures + 4 hand-filed epics

508total gap_score outstanding

313/346"CC adoption" milestone closed/total

Pipeline health: how a CC release becomes an issue here

1. Watchclaude-release-watch.yml snapshots the upstream CHANGELOG. Cron removed 2026-07-28 (weekly quota); workflow_dispatch only, so 2.1.239-241 were never fetched.

2. ExtractLLM step turns bullets into features. Fails on expired CLAUDE_CODE_OAUTH_TOKEN; then a generic "manual triage" issue is filed instead (the 8 pipeline issues).

3. FileOne issue per feature with key, category, gap_score, affected skills. Working when step 2 works: 2.1.238 produced 5 features from 39 bullets.

4. TriageHuman/agent batch: verify each against ork's real surfaces, close no-ops with proof, PR the real ones. Last audit doc: 2.1.231 (2026-08-13). Historical no-op rate about 60%.

5. Bumplatest_known advances per triage (2.1.238). Floor stays 2.1.220 until the override expires; then cc-support-window-bump.yml resumes latest+3.

Open feature issues by version

2.1.221

2.1.222

2.1.225

2.1.227

2.1.229

2.1.232

2.1.233

2.1.234

2.1.235

2.1.236

2.1.238

By category (gap_score weight in brackets)

breaking

new_field

new_perm

new_command

breaking 40 or 20 each, new_perm/new_field/new_command 10 or less. gap_score by version: 2.1.221: 22, 2.1.222: 80, 2.1.225: 40, 2.1.227: 20, 2.1.229: 45, 2.1.232: 99, 2.1.233: 45, 2.1.234: 65, 2.1.235: 20, 2.1.236: 32, 2.1.238: 40

Every open feature issue

category version min gap_score skill contains

issue	version	category	gap	feature key	affected skills
#3642	2.1.238	breaking	40	`mcp_json_headers_helper_trust_gate`	configure, doctor, security-patterns
#3620	2.1.222	breaking	20	`remote_control_autostart_user_scope`	configure, setup, doctor
#3619	2.1.222	breaking	20	`disable_model_invocation_refusal`	help, auto
#3618	2.1.222	breaking	20	`sendmessage_permission_classifier`	agent-orchestration, chain-patterns, security-patterns
#3617	2.1.222	breaking	20	`pretooluse_autoallow_bg_task_bypass`	agent-orchestration, security-patterns, configure
#3614	2.1.225	breaking	20	`sendmessage_recipient_no_swap`	agent-orchestration, chain-patterns
#3613	2.1.225	breaking	20	`mcp_oauth_keychain_401_burst`	mcp-patterns, security-patterns
#3602	2.1.227	breaking	20	`action_allowed_non_write_users_bash`	github-operations, ci-debug
#3603	2.1.229	breaking	20	`commit_push_pr_dangerous_flags`	commit, create-pr, github-operations
#3586	2.1.232	breaking	20	`gateway_desktop_overlay_schema`	configure
#3585	2.1.232	breaking	20	`sendmessage_bare_name_delivery`	agent-orchestration
#3584	2.1.232	breaking	20	`subagent_fork_default_background`	agent-orchestration, chain-patterns, task-dependency-patterns
#3591	2.1.233	breaking	20	`todo_task_tools_removed_new_models`	task-dependency-patterns, agent-orchestration, chain-patterns, implement, auto
#3595	2.1.234	breaking	20	`bg_task_notify_system_reminder`	agent-orchestration, task-dependency-patterns
#3594	2.1.234	breaking	20	`fullscreen_restart_preserves_perms`	security-patterns, configure
#3598	2.1.235	breaking	20	`send_message_oversize_refusal`	agent-orchestration, chain-patterns
#3599	2.1.236	breaking	20	`send_message_burst_refusal`	agent-orchestration, chain-patterns
#3604	2.1.229	new_command	15	`remote_control_continue_flag`	(none detected)
#3588	2.1.232	new_command	15	`at_mention_other_session`	agent-orchestration
#3592	2.1.233	new_command	15	`worktree_gitlab_mr_url`	github-operations, create-pr, chain-patterns
#3596	2.1.234	new_command	15	`add_dir_midturn`	configure
#3615	2.1.221	new_perm	12	`sandbox_credential_mask_mode`	security-patterns, configure, devops-deployment
#3590	2.1.232	new_perm	12	`managed_sandbox_binary_approval`	configure, security-patterns
#3589	2.1.232	new_perm	12	`gitlab_token_redaction_glab_sandbox`	security-patterns, github-operations
#3600	2.1.236	new_perm	12	`sandbox_wildcard_read_deny_precedence`	security-patterns, configure, mcp-patterns
#3616	2.1.221	new_field	10	`plugin_skills_root_path`	configure, doctor
#3605	2.1.229	new_field	10	`marketplace_command_source`	configure, doctor
#3593	2.1.233	new_field	10	`webfetch_cache_ttl_env`	web-research-workflow, browser-tools, configure
#3597	2.1.234	new_field	10	`session_list_truncation_notice`	agent-orchestration

Without an auto-filed key: 4 pipeline failures (manual-triage / staleness) and 4 hand-filed adoption epics (#3541 double-register, #3326 dependencies array, #3322 sandbox.enabled, #3309 EPIC D)

#3643 CC adoption: manual triage needed for 2.1.238, 2.1.219
#3641 platform-watch: new Claude Platform release notes need triage (2026-08-01,2026-08-03,2026-08-05,2026-08-07,2026-08-10,2026-08-11,2026-08-18,2026-08-19)
#3622 cc-watch: adoption lag — upstream 2.1.237 is 6 releases past latest_known 2.1.231
#3621 CC adoption: manual triage needed for 2.1.232, 2.1.233, 2.1.234, 2.1.235, 2.1.236, 2.1.237, 2.1.231, 2.1.227, 2.1.228, 2.1.229, 2.1.223, 2.1.224, 2.1.225, 2.1.226, 2.1.221, 2.1.222, 2.1.219
#3541 Invocable skills double-register: skill + generated command both surface as /ork:<name>
#3326 Adopt the plugin dependencies array
#3322 Adopt sandbox.enabled to retire the bypassable regex egress guard
#3309 EPIC D — ADOPT 5 CC capabilities

What the sweep would do, in order

Dispatch the watcher for 2.1.239-241 first (3 versions, 2 days old) so the sweep covers a closed range; otherwise it is stale on completion.
Batch by version, highest gap_score first: #3642 (2.1.238, trust gate on inline MCP servers, touches the shipped mcp-enabled.json template) is the one most likely to be real; the 2.1.232 cluster (6 issues) is the largest batch.
Verify each against ork's actual surfaces (hook events, settings keys, .mcp.json, agent frontmatter), not against the changelog prose; close no-ops with the proof line in the comment. Expect roughly 60% no-ops.
Close the 8 pipeline issues once their versions are covered by per-feature triage, and record the range in a docs/audits/cc-adoption-2.1.221-241 triage doc.
Advance latest_known to 2.1.241 in cc-support.json (floor untouched), with the synthetic release-watch fixture bumped per the .latest coupling.