Skip to content

2.1.0

Choose a tag to compare

@NintendaDev NintendaDev released this 13 Sep 14:37
· 388 commits to main since this release
adde8c9

🚀 2.1.0 - Test run placement and rule capture

Where tests run in a plan, and what becomes a project rule, are no longer left implicit - both are now explicit, visible decisions. /unikit can also bring an already-configured project's config file up to date with the current template.

✨ Test runs become their own tasks, placed by policy

A test run is now its own checklist task, carrying a Test checkpoint: <scope> line instead of a command hidden inside another task - and where it lands comes from the new testing section of .unikit/config.yaml rather than a question on every plan. /unikit-verify now skips re-running a full suite when nothing has changed since the last one, and says so instead of repeating it.

What's included
  • testing.plan.checkpoints.{ultra,full,fast} sets where runs land (defaults phase/phase/plan); testing.implement.merge_checkpoints.<mode> can collapse every run in scope into one
  • A run's width follows its scope on its own - one task's fixtures, a touched module's tests plus whatever depends on them, or everything at the end of a plan
  • Writing tests is unchanged - still done inside the task that introduces them, in any phase
  • The plan logs every run plus a Full run: marker that /unikit-verify checks before deciding to reuse it
  • Plans written before this update have no run-placement line and are left exactly as they were

♻️ Project rules are proposed, never written behind your back

Patterns worth keeping are now collected while you work and offered to you as a single question at the end of the run - no skill writes to .unikit/RULES.md on its own any more. The file itself is now a flat list, one rule per line with no sections, and /unikit-rules compact can tidy an older file into that shape without deleting anything.

Details
  • Candidates come from /unikit-implement, /unikit-verify, and the implement worker/coordinator; only /unikit-rules, called with the rules you picked, writes the file
  • Up to three candidates are offered per run alongside an explicit "Add nothing"; a declined candidate is not offered again
  • The background-agent alias used for rule capture was removed - the choice needs a person, so it is asked in the same session instead
  • RULES.md has no length limit and flags nothing - a rule that cannot be shortened is kept exactly as written

⚙️ /unikit can actualize an existing config

Asking /unikit to "update the config", "add missing settings", or "fix my config" on an already-configured project now run the full setup - it compares .unikit/config.yaml against the current template, fills in safe defaults silently, and asksonly about placeholders or out-of-range values. Keys it does not recognize are reported, never deleted, and the two language-selection keys are never written or asked about by this mode.

🛠 Internal Improvements

Technical changes
  • New test-suite guard families cover run placement, rule-candidate capture, and the config actualization branch
  • The ultra plan-bundle integrity check grew from 9 to 11 checks, plus 4 template assertions for the new run-placement secti
  • Documentation updated across configuration.md, subagents.md, skills.md, and workflow.md

Full Changelog: 2.0.1...2.1.0