v0.6.1 — Standard installation path fixes

Fixes

• Fix bundled catalog loading from installation paths containing spaces, Japanese text, percent signs, or hash signs. This fixes startup in the default Documents/Max 9/Packages/maxforge directory without a symlink workaround.
• Print native error messages as literal text instead of interpreting percent characters as printf format directives.
• Add five installed-path regressions and a native error-format guard; all 417 automated tests pass.

Installation

Download maxforge-v0.6.1.zip and its matching .sha256 asset, verify the checksum, save your work, and close Max. Replace the complete Max package, not only the external binary. The package includes macOS Universal and Windows x64 externals with their bundled service; it uses Max's own Node runtime and does not ship Node.

If v0.6.0 was installed through a symlink workaround, replace that link with the complete extracted package in Documents/Max 9/Packages/maxforge. Do not overwrite or delete a development checkout through a symlink. No MCP server or helper object is required: create one maxforge object.

Skills remain available through:

npx skills add bbb-max-externals/maxforge --skill maxforge-live --global

Requires Max 9 with bundled Node 20 or newer. macOS signing and notarization are checked by CI. Before publication, the signed CI package is tested in the real standard Packages directory, including catalog discovery, patch editing, save/reopen, and revision retention. Windows is build/CTest-verified in CI, not real-host tested.

The release workflow attaches the versioned ZIP and checksum after its clean signed/notarized rebuild. The optional npm CLI is a separate distribution; npm publication is not included in this release.