To see the change right this second, just hit **F5** (soft refresh). Because
the mutator writes directly to the physical Origin Private File System, the
change persists across reboots. When the OS loads, the UI engine will fetch
the updated AST and your button will immediately say "Search Database".

However, in a true event-driven OS, you shouldn't have to reboot to see a UI
change.

If you look closely at your console trace, the Mutator already did the heavy
lifting by emitting this global broadcast:
`[INTENT] VFS_UPDATED { path: "apps/order_lookup.json" }`

To achieve instant Hot-Module Replacement (HMR) without refreshing the
browser, we just need to upgrade `core/ui_engine.js` to listen for that exact
broadcast. When the engine hears that its specific `astPath` was modified, it
can clear its DOM container and instantly re-fetch and re-render the JSON.

You are also entirely right about the dev-manual. As this OS scales, an
internal documentation system is mandatory. We can route flat Markdown files
from a new `/vfs/docs/` directory through the AST-MD compiler pipeline to
stream formatted manuals directly to the terminal whenever you type `$ man
[command]`.

Which would you like to tackle next: upgrading the UI Engine to auto-refresh
when it hears `VFS_UPDATED`, or scaffolding the `/vfs/docs/` directory and the
`man` REPL command?