chore: move skills and evals to plugins/bin, remove legacy root configs

Skills and evals migrated from .agents/ to plugins/bin/ plugin directory.
Remove .mcp.json, provider-manifest.sh, and skills-lock.json legacy artifacts.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

AGENTS.md

@@ -4,9 +4,6 @@ This repo is the global AI development configuration repository — the authorit
 
 ## Structure
 
-- `core/` — provider-agnostic source of truth (plain language, no tool-specific references)
-- `.agents/skills/` — directly-deployed skills (Agent Skills standard); deployed to `~/.agents/skills/` via `install.sh`; marketplace and factory skills live in `plugins/kyberforge/` instead
-- `.agents/evals/` — eval.yaml files for skills not bundled into a plugin
 - `.claude-plugin/` — marketplace manifest (`marketplace.json`); read by both Claude Code and Copilot CLI
 - `plugins/` — installable plugin units; each is self-contained (skills, agents, hooks, MCP servers, bundled assets); install separately via `claude plugin install <name>@holocron`
 - `providers/claude-code/` — Claude Code adapter (deployed to `~/.claude/` via `install.sh`)
@@ -33,7 +30,6 @@ Read these on demand:
 
 ## Key rules
 
-- `core/` content must use plain imperative language — no tool names, provider APIs, or format assumptions
 - Never edit files deployed by `sync.sh` directly in a project; put customizations in override files
 - `providers/claude-code/CLAUDE.md` is the deployed global config — edit it there, not here
 - Governance constraints from `core/instructions/governance.md` apply when building content in this repo — hard prohibitions on secrets and data, HITL requirements before irreversible actions, sycophancy resistance, and deterministic execution preference are always in effect