Document `fuseraft eval` in docs/cli-reference.md

`docs/cli-reference.md` documents every top-level CLI command as its own `##` section — `run`, `repl`, `sessions`, `plugins`, `validate`, `config`, `init`, `graph`, `arch`, `knowledge`, `memory`, `objective`, `context`, `schedule`, `skills`, `log`, `models`, `update`, `settings` — except `fuseraft eval`, which is registered as a top-level branch in `src/Program.cs` (`cfg.AddBranch("eval", ...)`) right alongside those others.

`eval` *is* documented, but only in [`docs/evals.md`](https://github.com/fuseraft/fuseraft-cli/blob/main/docs/evals.md), which `cli-reference.md` never links to. A newcomer scanning `cli-reference.md` — the natural place to look for "what commands does this CLI have" — has no way to discover `fuseraft eval` exists.

**Task**

Add a `## \`fuseraft eval\`` section to `docs/cli-reference.md` (near the other command sections, e.g. after `## \`fuseraft models\``) that briefly summarizes `eval init` and `eval run` and links to `docs/evals.md` for the full reference, matching how other multi-page topics are cross-linked elsewhere in this file (e.g. the `## \`fuseraft repl\`` section links out to `docs/skills.md`).

**Acceptance criteria**

- `fuseraft eval` has a discoverable entry in `docs/cli-reference.md`.
- The new section links to `docs/evals.md` rather than duplicating its full content.
- No behavior changes — docs only.

Good first issue — no code changes required, just closing a documentation gap.