Ronne AI Marketplace 0.4.0

What it added

• A workspace is a level above scopes, with its own members and roles: user, moderator, and a new admin who runs the workspace without being root. It is public or private; a private workspace and everything in it is seen only by its members and root. Every instance has the global workspace, and everyone but root is a member of it.
• Everyone gets a personal workspace, seen only by them and root, to build and try items before moving them to a team. People ask to join a workspace from the Workspaces page, with a message, and its moderators and admins answer. Admins can rename their workspace, and a scope can move from one workspace to another.
• Scope names are unique per workspace, so an item's full name is @workspace/scope/name, and @scope/name still means an item in global. When a workspace is renamed or a scope moves, the old names stay as aliases, so lockfiles, dependencies and links keep working. An rmk older than 0.4.0 installs only global's items and asks you to update.
• rmk workspaces lists the workspaces you can see and your role in each, rmk search --workspace narrows a search to one, and rmk export groups the scopes you can use by workspace. The MCP server has list_workspaces, and the API has GET /api/v1/workspaces.
• The header's links move to a left sidebar in three groups, which folds into a rail of icons. Its workspace switcher sets the workspace you are working in: the Catalogue, Reviews and My submissions show only that one, and New item starts in it, until you choose All workspaces.
• An item and the drafts of yours that it needs go through review together. Submit sends them in one step, and Release releases an item with the dependencies that aren't released yet, all or none. Items that need each other, such as an agent and the skill it runs, are allowed and are installed together.
• rmk-server backup makes one archive of the database, the stored items and the settings file while Ronne runs, and rmk-server restore brings it back, on the same machine or another, into SQLite, PostgreSQL, MySQL or MariaDB. An archive can be checked with --verify and encrypted with a passphrase.
• The server writes one JSON line per event, with a level and the request it belongs to, and never a secret. Point it at an OpenTelemetry collector and it sends metrics and traces; with no collector, nothing is sent. The health endpoint now also reports the database and storage.
• A threat model and an incident runbook sit in the repository. rmk-server revoke-access ends sessions and revokes access tokens for everyone or one person, and rotate-secret replaces the secret that signs sessions. Both ask first and are recorded in the audit log.
• The server runs on Linux and macOS. On Windows, run it in WSL 2 or a Linux virtual machine: the Windows service, the Windows archives and install.ps1 are gone. rmk and the MCP server still run on Windows.
• An item falls back to older versions when the newest ones conflict, each dependency version shows what it writes and accepts, Submit shows what it would refuse after each save, and table columns stay readable on phones.