Repository navigation
🚀 3.0.1 - Tests on your terms, hash checks without Git Bash
This release stops the agent from writing or running tests unless you ask for them. The checks that compare a plan with its research and with its last test run now work in any shell on Windows.
✨ Tests only when you ask
/unikit-execute and /unikit-fix no longer write or run tests by themselves. They ask first and say which tests would run. With no answer, nothing is written and nothing runs.
What's included
/unikit-executeasks once after a logic change: no tests (the first option), tests written after you accept the result, or a run of the existing tests.- Tests you ask for in the task wait until you accept the result. The closing question then offers Accept and write the tests first.
/unikit-fixasks once before its test run. Your answer also covers one repeat after a red result.- Unsaved changes in an open scene are never saved or thrown away without asking. You choose: save them yourself (recommended), let the agent save them, or discard them.
- The
testing.runsettings now also decide how wide a/unikit-executerun goes.
🧩 Hash checks work in any shell
The research drift check and the test-run record now use two small Node scripts installed into .unikit/system/. They give the same result in PowerShell and in Git Bash, and Git Bash is no longer required. The test-run record now depends only on file content, so a commit no longer makes it stale, whoever made it.
Details
research-hash.mjsneeds only Node. If it cannot run, you get one info line and the drift check is skipped. Verification does not fail because of it.tree-hash.mjsneeds Node and git. If it cannot run, you get a warning saying the test record was not checked.- A project in a subfolder of a repository counts only its own files. If you change a file next to it, run the tests yourself.
⚠️ After you update
Test-run records written by an older version will show as stale until all tests run once again. A plan in progress runs the full suite one extra time at its final checkpoint. A finished plan keeps the warning until /unikit-verify --strict runs the suite.
📇 Shorter research indexes
researches/INDEX.md is now a compact table with one row per research. Each row's description comes from the research's Topic: line, up to 250 characters, and older longer topics are shortened in the table. The research files themselves are not changed.
Details
- Archived research gets its own
archive/researches/INDEX.md. Archiving or restoring rebuilds both indexes once. - Restoring a research will not overwrite an active one with the same name.
- If an index is missing, the agent searches the research folders instead, without changing anything.
- Planning offers only active research. Reading the archive never restores anything.
Full Changelog: 3.0.0...development