Apex roster scoping, spawn analytics, and on-demand routing

The problem

Six weeks of session data showed generic agents (general-purpose, Explore, fork) beating tonone specialists 233-to-90. Choosing from a roster of 120 costs effort, and roughly 90 of the 100 agents were never spawned once.

New commands

• -`/apex-profile`: scopes the installed agent roster per project via enabledPlugins in .claude/settings.json, installing a curated subset instead of the full 100-agent tonone@tonone-ai bundle.
• -`/apex-stats`: spawn-count analytics pulled from local session transcripts, showing which agents a project actually uses, the tonone-vs-generic split, and zero-spawn prune candidates.
• -`/apex-route`: reaches any of the 100 specialists on demand, even when not installed in the current session. Reads docs/agent-index.json (generated from CLAUDE.md's team tables) to find the right agent, then injects its full persona into a general-purpose dispatch.

Also fixed

• -scripts/bump-version.py now syncs marketplace.json plugin versions too. This had been drifting since inception, with entries as old as 0.6.1 sitting against a root version of 1.9.1.
• -scripts/gen-skill-plugins.py rewritten to be idempotent and additive, backfilling plugin.json for the 22 skills that had none at all.
• -164 marketplace entries (design-team, data-science-team, secops-team, devx-team waves) converted from GitHub tree-URL sources to local ./team/x paths, matching every other wave.