Skip to content

2.0.0

Choose a tag to compare

@NintendaDev NintendaDev released this 05 Sep 16:49
· 410 commits to main since this release
ea00005

🚀 2.0.0 - The engine editor joins the pipeline

This release adds the engine editor as a third pipeline layer next to design and code - editor work is now planned, executed through an MCP server, and verified automatically. MCP server identity is reworked, plans and research each collapse to one file, and an ultra planning mode arrives for both.

⚠️ Breaking Changes

Every change below migrates automatically on the next unikit-ai init or unikit-ai update; rules sync/rules install refuse with exit code 8 until it has run.

  • mcp.servers in .unikit.json changes from an array to a key → code map - a server's settings identity (code) is now tracked separately from its package file name (key), so an engine's alternative servers no longer have to share one name.
  • MCP config files are renamed to a <vendor>-<engine>-mcp.json shape (e.g. unity-mcp-coplay.json → coplay-unity-mcp.json).
  • Context7 now connects over HTTP instead of a local npx process. Projects installed before this change keep their old entry - nothing is migrated.
  • Plan and research folders no longer carry a date prefix - a plan's folder name now matches its branch name; older dated names still resolve.
  • A plan's TASKS.md + PLAN-BRIEF.md merge into one PLAN.md. A finished plan with no open tasks is left alone, so plans/ stays a mix of old and new shapes by design.
  • A research's result and source files rename to RESEARCH.md + SOURCE.md. Its old brief file is left in place, untouched.

🧩 Editor tasks: the Editor: grammar, rules trees, and a findings log

A task that touches the editor's saved state now carries an Editor: [kind] <container> → <target> : <action> line, across six kinds - scene, ui, vfx, anim, asset, settings. A project setting decides how it's carried out: through the configured engine MCP server, by hand with an exact instruction, or as a direct text edit - then /unikit-verify checks the result.

What's included
  • A rules tree copied from the selected MCP server into .unikit/system/engine-mcp/ - exceptions only, no tool names, nothing it grants is ever taken away
  • A per-project findings log, .unikit/MCP-RECHECK-NOTES.md, plus a ## MCP Findings table written into the plan the moment a task finishes
  • Two new skills: /unikit-mcp-trap records a finding, /unikit-mcp-audit re-checks and retires old ones
  • The development principles grow from 23 to 244 lines with a claim/evidence/verdict model and nine named failure classes (false success, eaten parameter, catalog phantom, and six more), plus a six-field diagnosis in /unikit-fix
  • Unity only, for now - Godot and UE5 plans don't yet generate Editor: lines

🔌 MCP: seven configs, six rules trees, settings that hold

The catalog grows from five configs to seven - Unity Biome MCP and Fennara Godot AI are new - and all six engine servers now ship a rules tree. Writing a server into an agent's settings file is now handled on both init and update, not just init, so a dropped server's entry and permissions no longer survive future runs.

Details
  • Unity: Unity Biome and Coplay; Godot: Fennara (free), GDAI (paid), Coding-Solo (free); UE5: ChiR24
  • OpenCode can now connect to a remote MCP server, not only a local command
  • New per-server fields: docs (where it documents itself), rules (its rules tree), order, and per-OS config variants

✨ Ultra mode for plans and research

/unikit-plan ultra writes a bundle - the same PLAN.md plus one deeply detailed file per phase, for a strong model to write and a smaller one to execute. /unikit-explore ultra adds matching research artifacts (architecture views, ADRs, a dependency graph) only when they're warranted; both modes are strictly opt-in, triggered only when asked for by name.

What's included
  • Nine integrity checks gate every ultra plan before it's used
  • A reader contract (.unikit/system/ultra-plan-read.md) gives each pipeline skill its own read depth, from one phase to the whole bundle
  • Phase files are read-only during execution - the manifest is the only thing ever edited
  • A coherence gate checks every saved research, ultra or not, in at most two passes before asking the user
  • Drift detection by hash: /unikit-plan records a Summary SHA256, later steps recompute it to catch an out-of-date plan

♻️ One manifest per plan and per research

The overview, settings, checklist, commit plan and technical notes of a plan now live in one PLAN.md instead of two separate files. Re-running /unikit-explore on an existing topic continues that research instead of starting a second one.

🐛 Fixes

Fixes
  • /unikit-evolve could edit installed skill files through an unused permission; the write boundary is now explicit and enforced
  • /unikit-rules reports one row per rule for a batch, instead of writing the confirmation as if only one rule had been added
  • /unikit's stack-selection summary is now plain markdown instead of <details> tags a terminal rendered literally

🛠 Internal Improvements

Technical changes
  • inquirer now loads lazily, trimming ~240ms off every non-interactive CLI run
  • Tests no longer depend on a live GitHub connection - the registry's "official" level reads a local fixture
  • New test coverage for the migration chain and the ultra plan/research bundle contract
  • Installer tests run against a fixture MCP catalog instead of the shipped configs
  • Six documentation audits found and fixed 59 places where the docs no longer matched the code; the README is rewritten around three layers - design, code, and the editor

Full Changelog: 1.1.0...2.0.0