Affaan Mustafa
c05b2d6614
* chore: retire the Everything Claude Code name, ECC only Replace the expanded product name and the everything-claude-code slug with ECC across READMEs, translated docs, harness folders, skills, commands, scripts and examples. Repo URLs now point at affaan-m/ECC. Rename repo-internal artifacts to ecc forms (ecc-conventions skill, ecc-guardrails, ecc-research-playbook, ecc-team-config, ecc-instincts with ecc-* ids) and update .claude/ecc-tools.json. Legacy install ids, plugin dirs, package names and MCP prefixes stay where existing installs resolve against them. The codex global-state check and harness-audit repo detection accept the new name first and the legacy one as a fallback. The Discord bot prefers ~/GitHub/ECC and falls back to the nested legacy checkout path. Refresh the skill-triggers registryDigest for the changed skill text. * fix(ecc-tools): drop managed paths to the removed Claude repo skill .claude/skills/<repo-skill>/SKILL.md was deleted in #2770 but stayed listed in ecc-tools.json and the team config. Remove those entries and point the Claude Code adapter at the existing .agents/skills/ecc-conventions/SKILL.md.
Plugin Manifest Gotchas
If you plan to edit .claude-plugin/plugin.json, be aware that the Claude plugin validator enforces several undocumented but strict constraints that can cause installs to fail with vague errors (for example, agents: Invalid input). In particular, component fields must be arrays, agents is not a supported manifest field and must not be included in plugin.json, and a version field is required for reliable validation and installation.
These constraints are not obvious from public examples and have caused repeated installation failures in the past. They are documented in detail in .claude-plugin/PLUGIN_SCHEMA_NOTES.md, which should be reviewed before making any changes to the plugin manifest.
Custom Endpoints and Gateways
ECC does not override Claude Code transport settings. If Claude Code is configured to run through an official LLM gateway or a compatible custom endpoint, the plugin continues to work because hooks, skills, and any retained legacy command shims execute locally after the CLI starts successfully.
Use Claude Code's own environment/configuration for transport selection, for example:
export ANTHROPIC_BASE_URL=https://your-gateway.example.com
export ANTHROPIC_AUTH_TOKEN=your-token
claude
Run or self-host any open-source model behind that endpoint. Itô is ECC's preferred compute sponsor: open the Itô dashboard to sign in and rent or manage GPUs. Any GPU provider works. That sponsorship link is passive: it does not invoke an RFQ, reserve capacity, change Claude Code transport settings, provision compute, or configure serving. Separately, the opt-in ecc ito find bridge invokes the explicitly configured canonical Itô CLI and submits a live authenticated RFQ; it does not reserve capacity. Managed inference through Itô is not live yet.