/**
 * `peaks ecc install|status|ls|show` — the ECC read layer.
 *
 * ECC's agent definitions come from the `ecc-universal` npm dependency of
 * `peaks-loop-mut`. `install` copies `<package>/agents/*.md` into the
 * plugin-free dir the LLM reads (`~/.peaks/agents/ecc/`); `status`, `ls` and
 * `show` read that copy. There is no download anywhere in this file: the
 * previous design fetched a GitHub release tarball on the premise that the
 * project was not on npm, and that premise was false (`ecc-universal`
 * `repository.url` is `git+https://github.com/affaan-m/ECC.git`).
 *
 *   - `peaks ecc install` — land/refresh the copy. Idempotent; prunes agents the
 *   - `peaks ecc status` — package version + what landed and when.
 *   - `peaks ecc ls` — the roster with declared name + description (D-009
 *     fallback to filename + first body line when frontmatter is malformed).
 *   - `peaks ecc show <name> [--section H] [--max-lines N]` — the agent body;
 *     this is the Skill-first path the LLM consumes directly.
 *
 * Per the "Enhancement, not new AI CLI" tenet: read-only access plus a local
 * copy. There is no `peaks ecc run`, and no ECC subprocess is spawned.
 */
import type { Command } from 'commander';
import { type ProgramIO } from '../cli-helpers.js';
export declare function registerEccCommands(program: Command, io: ProgramIO): void;