Purge deprecated ACE/CRG/CIX/ROX development dependencies and self-validate with Opcore

[tomdps]

Goal

Remove the deprecated ACE, CRG, CIX, and ROX development/bootstrap/guardrail stack from Opcore and make Opcore validate its own repository. This is a blocking prerequisite for the remaining Python parity sequence because fresh Zeroshot worktrees must not acquire or depend on deprecated external tools.

Scope

• Delete checked-in deprecated configuration and wrapper entrypoints, including ace.json, rox.json, current-tool setup/dev-env scripts, ROX gates, and their tests.
• Remove root scripts, environment variables, sibling-repo discovery, generated-state assumptions, and Zeroshot setup steps that acquire or invoke those tools.
• Replace local CI and Zeroshot command proof with a checked-in Opcore-on-Opcore validation command built from the repository's own public CLI/package surface.
• Give self-validation an explicit repository policy/scope so intentional failing fixtures and unavailable optional fixture authorities do not make the gate meaningless.
• Remove deprecated guardrail fields and commands from release, cutover, ASP dogfood, provenance, workspace, schema, contract, fixture, summary, and test evidence. Replacement evidence must record Opcore self-validation, not reuse historical guardrail hashes.
• Remove stale architectural/planning/release guidance that instructs agents or maintainers to use the deprecated stack.
• Update AGENTS.md and CLAUDE.md together to describe the new convention.
• Remove deprecated generated/cache paths from active source-discovery policy where they exist solely for this development stack; retain only product-generic exclusions with an independently valid reason.

Required self-validation behavior

• npm run setup installs repository dependencies only and leaves a clean worktree.
• npm run opcore:self-check uses the built Opcore CLI against this checkout, consumes .opcore/config, and checks the intended implementation surface without scanning intentional failure fixtures as production source.
• The self-check fails closed on malformed router output, infrastructure failure, unsupported request, or error diagnostics and emits concise actionable output.
• scripts/ci/run-local-ci-equivalent.sh runs normal CI plus opcore:self-check; the docs/guidance fast path runs repository-native checks only.
• .zeroshot/settings.json uses the non-deprecated setup and the same CI-equivalent proof.

Acceptance criteria

• A repository search finds no active acquisition, wrapper, command, receipt, or documentation path for ACE, CRG, CIX, or ROX.
• The removed configs/scripts cannot be required by workspace/provenance/package/release checks.
• npm run setup:check-clean, npm run lint, focused tests, npm run opcore:self-check, and the local CI-equivalent gate pass from a clean worktree based on origin/dev.
• Opcore Zero changed and staged verification passes before commit.
• The PR targets dev and must merge before Python parity issue P1: Add Python file-length and function-metrics parity #292 starts.

Dependency

Insert before #292 in epic #243's strict sequential graph. It supersedes stale setup/current-tool blockers #225 and #227; close those only after this PR is merged and verified on dev.