Tags: sergezuber/FABULA-LLM-5
Tags
fix(setup): repo engine always wins over a PATH mimo — foreign-engine… … hijack of the app (v0.1.3) setup.sh resolved the engine for the fabula command as 'command -v mimo' FIRST and only fell back to the repo-local bin/fabula it had just built. On a machine with a pre-existing MiMoCode install the fabula shim therefore exec'd the foreign engine, and the app served that engine's UI and config inside the FABULA window. The repo-local engine now always takes precedence; a PATH mimo is only the fallback when the repo binary is absent (a --deps run). Re-running setup.sh also repairs an existing fabula exec-shim by repointing it to the preferred engine (detected via its two-line shim shape); a real fabula binary on PATH is never touched. Version 0.1.3.
fix(app): generate the complete .app bundle — fresh-clone launch cras… …hed in UNUserNotificationCenter (v0.1.2) app/build.sh only emitted Contents/MacOS/<binary>; since *.app/ is gitignored, a fresh clone produced a bundle with no Info.plist. Without CFBundleIdentifier, LaunchServices cannot resolve the bundle proxy and UNUserNotificationCenter aborts the process at launch (SIGABRT in applicationDidFinishLaunching, seen on macOS 15). Dev machines only worked off a stale untracked Info.plist from an earlier build. build.sh now writes the full bundle every time — Info.plist (identifier com.sistemma.fabula-llm-5, version read from the engine changelog), PkgInfo, and the icon (app/icon.icns added as the tracked source) — and codesigns after all resources land, then refreshes LaunchServices. FabulaApp.swift additionally gates every notification-framework touch on a resolvable bundle identifier, so a broken or naked bundle degrades to no system notifications instead of crashing. Version 0.1.2.
fix(deps): stop executing manual install guidance as shell commands (… …v0.1.1) The dependency installer ran every manifest install string through /bin/bash -c — including human guidance like 'Install LM Studio (https://lmstudio.ai)…', which crashed with a bash syntax error on the parentheses during setup.sh. Dep entries now carry an explicit manual flag: all three install paths (scripts/install-deps.ts, scripts/manage-cli.ts, the in-chat install_plugin_deps tool) print manual steps as guidance and execute only real commands; installDep refuses to run a manual dep. A new test bash -n-parses every runnable install string and locks the routing. Version bumped to 0.1.1 with a changelog entry.