v0.3.0

RoleWeave 0.3.0

This release brings native phone shells, editable employee profiles, and persistent Agent bindings to the desktop installers, together with conversation refinements, encrypted host-credential settings, semantic color theming, and the bundled WorkBuddy engine host. The workspace grows easier to enter: existing folders can be initialized as RoleWeave workspaces, and the open workspace can be revealed in the system file manager from the top bar.

Changes

• Phones get a native shell instead of a scaled desktop: organization, instructions, desktop, and settings surfaces fit a phone layout, split into iOS, Android, and HarmonyOS variants with user-agent routing and a ?platform= override. Turns still execute on the opened computer desktop, and the organization page shows a read-only preview.
• Employee profiles are editable after creation. An employee's name, execution mode, and permissions — tools, resource rules, skills, and MCP bindings — are changed through the edit drawer, reachable from the position card header and the org-tree row menu. Changes are re-adjudicated by the engine; rejections roll back byte-for-byte, and employees with running turns return a conflict instead of writing.
• An employee's Agent selection persists and locks on first use. Imported employees choose a host once; newly created employees and projects bind at creation. The conversation panel shows the current Agent and disables switching once locked.
• Conversation work is easier to revisit: messages can be copied and re-edited, session history is browsable with read positions and drafts preserved per workspace, employee, and session, and a "new conversation" control rotates the active session into history while keeping the old one readable. Failed turns retry against their original association. Settings drafts use unified JSONC with encrypted credential references, change previews, conflict handling, and a restart prompt.
• Host credentials move in-app: Qoder, Claude, Codex, and WorkBuddy credentials can be saved with operating-system encryption from Settings, with change previews and launch-environment precedence. A bundled WorkBuddy (CodeBuddy Code CLI) turn engine joins the host list with its audited tool manifest.
• Semantic color theming opens up: presets, a picker, and Agent-generated palettes retheme the light and dark surfaces.
• Creating employees is simpler: the drawer leads with Agent and basic information and expands memory, permissions, and budget on demand; the Agent identity is shown consistently, and Qoder model choices sync with the local CLI catalog. Model selection is available before the first task.
• Existing folders can become workspaces: opening a directory without RoleWeave files explains why and offers "Initialize this folder", preserving existing files and adding the workspace skeleton through the engine's apply gate. The workspace path in the top bar is clickable and reveals the folder in Finder or Explorer, including WSL share-path mapping.
• The module rail is frequency-ordered and self-explanatory, with a movable collapse control and a faster collapse animation.
• Groups gain a dismiss action with soft-delete and quota recovery, and long group messages expand to their full text.
• A new GitHub-operations example team (examples/github-ops) ships issue-research, PR-submission, and merge-gatekeeping positions driven by gh commands. An Ontology Runtime R2 contract slice (semantic-runtime.v1alpha1) documents trusted-execution vocabulary with pure-function tests; it is not live execution.
• Turn control is more robust: timeouts are configurable, indeterminate outcomes carry per-code copy, and cancellation kills process groups. Oversized request bodies are drained or read-aborted with a reported reason instead of a bare connection reset.
• Hiring and editing warn clearly about employee-level MCP bindings: every bundled engine currently rejects them on the first turn, so the panel warns instead of silently suggesting a capability that cannot run.
• The employee card keeps per-task and per-day budget declarations visible after turns instead of replacing them with latest-turn usage.

This packet is reviewed against main revision d5e028472a64a39465ebcc2f0b3c8c262988cbe1. The post-v0.2.0 commits are enumerated in the release record. Server refactors (#254/#280/#281), org-tree drag fixes (#263/#264/#282), avatar clipping (#287), hire drawer alignment (#277), localization fixes (#291/#324), the unified desktop visual language (#285), and changelog housekeeping (#253/#273) need no separate user-facing bullets. Version metadata and this frozen-notes file are release preparation, not additional runtime features.

Downloads

• macOS Apple Silicon: roleweave-0.3.0-arm64.dmg and roleweave-0.3.0-arm64.zip.
• Windows x64: roleweave-0.3.0-x64.exe.
• Intel Mac and Linux installers are not included.

Installation and updates

macOS packages are not Apple Developer ID-signed or notarized; Windows packages are not Authenticode-signed. The operating system may show a security prompt on installation or first launch.

On macOS, first launch of the downloaded .dmg can be blocked outright with the dialog ""RoleWeave" is damaged and can't be opened". This is Gatekeeper treating the missing signature as corruption — the download itself is intact, and right-click → Open does not bypass it. Install like this instead:

1. Open the downloaded .dmg and drag RoleWeave.app into /Applications (do not launch it from the mounted disk image).
2. Clear the quarantine flag in Terminal: xattr -cr /Applications/RoleWeave.app.
3. Launch RoleWeave from /Applications. The first launch may also ask for access to folders such as Documents; choose Allow.

The macOS app verifies an independently signed update manifest, downloads updates in the background and replaces the app on normal exit. Users on v0.2.0 receive v0.3.0 through that channel. Windows can check the existing Electron update channel, but unsigned builds keep in-app download and install disabled without a publisher identity; use the Windows installer manually. Publishing this release exposes its metadata to clients checking those channels.

CI covers native builds, packaged startup and layout, and installer asset integrity. Installation, uninstallation and cross-version automatic updates on user machines are not claimed as fully verified end to end. Users of older Org Workbench development builds need to install RoleWeave manually once.

Publisher handoff

Before allocating the annotated tag, recheck the final main-to-v0.2.0 delta and update these notes in the reviewed release commit if that delta changed. Required checks, protected merge, exact-commit checks and the ByteFolk release process still apply.

The workflow reads docs/releases/vVERSION.md from its frozen release commit. The first line must be # RoleWeave VERSION, followed by a nonempty body. It carries the exact bytes in a separate notes artifact, checks their SHA-256 before creating the draft, and passes them with --notes-file; no manual draft-body edit is required. Notes are not included in the installer asset inventory.

Tag pushes and manual dispatches with draft=false publish only after asset readback; manual dispatches with draft=true leave a draft. Do not rely on the transient draft during a tag-push run as a manual editing window. This preparation does not itself allocate a tag or publish a release. Roll back through a reviewed source revert before publication; never replace published assets or move a published tag.