Summary
v0.2.2 ships the completed Phase 1–3 work: a five-tier model abstraction
that removes hard-coded model IDs from agent definitions, a leaner core
roster with a single primary orchestrator, and a set of acceptance fixes
that tighten the installer and documentation.
Highlights
Model tier abstraction (Phase 1)
- Five canonical tier tokens — TIER_ROUTER, TIER_REASONING, TIER_CODE,
TIER_FAST, TIER_REVIEW — replace hard-coded model IDs in agent frontmatter. - The three legacy tiers remain required for backward compatibility;
TIER_ROUTER and TIER_REVIEW fall back one hop (to TIER_REASONING and
TIER_CODE) when omitted. - Ships templates/models.config.json with a ready-to-use default profile and
an editable generic profile, plus a pre-flight validator
(scripts/validate-models.sh) and installer wiring (--symlink,
--with-extras, --with-examples, --skip-validation). - New docs: docs/CONFIGURATION.md (tier resolution, fallbacks, placeholder
policy) and docs/SETUP-NATIVE.md (manual install path).
Lean core roster (Phase 2)
- agents/orchestrator.md is now the sole mode: primary agent; security was
demoted to mode: subagent. - The roster is partitioned into four tiers: core routing, core delivery,
conditional operations, and explicit opt-in extras. - Three new universal skills: build-debug, dev-cleanup, npm-debug.
Acceptance fixes (Phase 3)
- OS allowlist gate added to the installer.
- README updated with a single responsibility map and oracle now listed in
the core-routing tier table; QUICKSTART and SETUP-NATIVE expanded. - Prompt-assembly stable-prefix contract documented in AGENTS.md, with a
committed boundary baseline and guard tests.
Notes
- Full test suite: 384 pass / 0 fail; git diff --check clean.
- .opencode/models.config.json remains user-local and is excluded from this
release; the default profile references provider IDs that are not yours,
so switch to the generic preset and edit the file before running agents. - The ten-minute usability criterion is documented and reproducible but was
not empirically timed in this release. - The pre-existing v0.2.0 / v0.2.1 tags were not moved; this release ships
as a new tag ahead of them. - Next step: the external feedback window (Phase 4) opens after this release.