Skip to content

v1.0.2 — 📖 The documentation catches up with the product

Choose a tag to compare

@bagidea bagidea released this 02 Sep 00:00
· 5 commits to main since this release

📖 The documentation catches up with the product

v1.0.0 shipped five real capabilities. v1.0.1 made the office speak fourteen
languages properly. Neither of them reached the surfaces most people actually
read — the landing page's feature grid, the docs site, and the guide set had no
idea any of it existed.

A capability nobody can find is a capability nobody has.

Nothing here changes behaviour. The office runs exactly as v1.0.1 did. What
changes is what it tells you, and in how many languages it tells you.


The website now describes what v1.0 added

Four new cards on the landing page:

📦 Run it somewhere else a throwaway Docker container, or another machine over SSH
🔎 Recall by meaning words and meaning both get a say in what a session remembers
🎨 Media Studio make a picture, change one, make it move — an edit never overwrites its input
📚 Skills that correct themselves reflection can fix a skill it wrote, and runs after failures

…and six new sections on the docs page: where agents run, ghosts that
don't overwrite each other
, recall by meaning, self-correcting skills,
the Tools Hub, and the Media Studio.

Each one cites the ALL-CAPS English setting name the app itself shows —
📦 RUN LOCATION, 👻 GHOST ISOLATION, 🔎 SEMANTIC RECALL — so the page and the
office agree on what a thing is called.

All of it in all fourteen languages, on the same commit

24 new site strings × 14 languages, written rather than left to fall back:
English, ไทย, 中文, Español, हिन्दी, العربية, Português, Русский, 日本語, Deutsch,
Français, 한국어, Indonesia, Tiếng Việt.

"Falls back to English" is still not the same as "supported".

A guide for the 🧰 Tools Hub

docs/guide/tools-hub.md
— the 43 entries and what separates the 15 built-in abilities from the 28 MCP
servers, the creative shelf (Blender, Godot, Unity, Unreal Engine, Roblox
Studio), why a key should be named rather than pasted into a command, how to
read the risk line, and how to submit an entry — including why every one is
checked against the registry before it merges. The v1.0.0 rebuild found seven
dead buttons — six deprecated reference servers and one package that had never
existed at all. A one-click catalog is a supply chain.

The Plugins Hub read English in 12 of the 14 languages

The last known gap of this kind. web/plugins.json carried English and Thai,
and the page collapsed every other language to one of those two before
rendering — so a reader in Korean got a fully translated page wrapped around
English plugin cards. Same shape as the tool catalog before v1.0.1.

The catalog now has per-language overlays fetched on demand, and the page reads
the real document language.

Tests, so the fourteen languages stay checkable

daemon/tests/site-i18n.test.js — eight tests. CI now fails if a language has
no table at all, if any English key is untranslated anywhere, if a language
carries a key English has dropped, if a paragraph is the English left in
place, if a data-i18n key has no English source, if a v1.0 capability vanishes
from a language, or if the app renames an ALL-CAPS setting the docs cite. The
plugins-catalog.test.js adds eight more, including one that fails if the Hub
page stops fetching its overlays at all — twelve translated files no page loads
is twelve files of dead weight while the bug still ships. The suite goes from 242
to 258 tests.

Also

The README documents 📦 run location and 🔎 semantic recall as their own
features, adds eight HTTP API rows that were missing (/registry/backend,
/registry/ghostworktrees, /registry/semantic, /registry/skill/revert,
/gen/image/edit, /gen/video, /studio, /tools/catalog), and the ghost,
skills and tools entries now say what v1.0.0 actually did to them.


Full detail: CHANGELOG.md