# Gitmoot v0.1.0-beta.8

Gitmoot v0.1.0-beta.8 adds ranked SkillOpt exploration as a beta workflow for
improving agent templates with broader human preference feedback before final
A/B validation.

## Features

- Ranked SkillOpt review runs with `explore`, `refine`, `distill`, and
  `validate` modes.
- N-way review item options through repeated `--option label=path` artifacts.
- Markdown and GitHub feedback packets that let humans rank every option and
  record useful or rejected traits.
- Ranked feedback import that derives pairwise preferences for optimizer-ready
  training packages.
- `skillopt review status` phase recommendations with ranking stability,
  pairwise preference counts, and advisory next-mode guidance.
- Agent-facing Gitmoot skill guidance for ranked exploration cadence, including
  the rule that heavy SkillOpt optimization should not run after every tiny
  feedback round unless the user explicitly asks.
- Beta smoke-test documentation for clean-temp-home ranked exploration runs,
  Markdown packet import, pairwise expansion, training export inspection, and
  optional GitHub issue or PR feedback sync.
- High-level `gitmoot skillopt train` documentation for session/iteration
  orchestration, optimizer handoff, candidate review, explicit
  promote/reject decisions, and start-next gate enforcement.
- Deterministic `scripts/skillopt-train-smoke.sh` coverage for fake managed
  generation, fake optimizer handoff, fake GitHub candidate review, and
  promote/reject/start-next paths.

## Known Beta Limits

- Ranked exploration is a beta workflow; final promotion should still use fresh
  A/B validation items by default.
- GitHub feedback collection still uses issues or PR comments authored by the
  authenticated GitHub user.
- Phase recommendations are advisory. Gitmoot does not automatically change
  modes, run the external optimizer, import candidates, or promote templates.
- The external optimizer remains outside the main Gitmoot binary.
- Train-mode smoke coverage uses fake GitHub and fake optimizer seams; real
  GitHub review publication still depends on the authenticated `gh` environment.
