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.

v0.2.0

RoleWeave 0.2.0

This release brings the goal-centered collaboration spine, the Windows WSL runtime for projects and Agent hosts, and the refined employee workspace and avatar workflow to the desktop installers, together with the model-slug and conversation-viewport fixes. Its changelog section also assigns user-visible work that already shipped in the v0.1.2 installers but was never assigned to a release there — the RoleWeave light/dark theme, the Codex Agent hosts, the model line, and the collapsible execution status row — which the v0.1.2 publisher-handoff paragraph anticipated.

Changes

• Goals are a first-class module: declare a goal, associate personal sessions, group chats and turns with it, and review the goal with its related work in one place. The goals contract and API are new, and the surface is bilingual.
• Windows can run the project backend and Agent hosts in a local WSL distribution while keeping the Windows interface. A runtime preference selects the distribution, the project picker starts from its Linux home, and the backend uses Linux Node with a built-in adapter that preserves the Linux CLI's login, proxy and certificate configuration. Cross-distribution selection is rejected.
• First launch starts from an empty workspace: the demo workspace is no longer copied or opened automatically. A previously opened workspace is restored when accessible, explicit overrides are preserved, and existing demo and user files stay untouched.
• Employee and project setup is simplified. Each employee or project binds one Agent with model selection; memory and session collaboration surfaces and conversation routing are new; employee avatars support upload, preset and AI-generation entry points.
• Local doc and mem services get a unified Docker management surface (initialize, verify, start, status/logs, stop) and connect as independent HTTP services: settings store an encrypted token, verify the actual API contract and open the upstream native UI. Source-based tooling pins the upstream commit and preserves history and persistent data paths.
• The Codex service-credential and local-login Agent hosts, the model line under hosts with a model knob, the RoleWeave light/dark theme and the collapsible execution status row are assigned to this release's changelog section; they were already present in the v0.1.2 installers.
• Long model names ellipsize on one line instead of wrapping, and switching employees preserves the conversation panel's scroll viewport.
• Codex turns no longer become unreadable records after write; the report center's audit timeline uses the conversation panel's engine-label source; Codex readiness requires the built-in engine boundary; the local Claude Host no longer offers a bare settings source that disables OAuth reuse.
• Workspace override paths skip local existence checks only in the Windows WSL control-plane mode, and the control-plane switch accepts the RoleWeave-named ROLEWEAVE_CONTROL_PLANE_MODE variable while preserving the legacy name.
• The free macOS GitHub update channel remains part of the package: the release workflow signs ZIP metadata with an Ed25519 key, and the client verifies it before background download and replacement on normal exit.

This packet is reviewed against main revision 971519b06ee24ee4a794b999a174729ea4260c9f. The post-v0.1.2 commits are #235 (goal spine, tracked by #222), #262 (Windows WSL runtime), #265 (employee workspace and avatar workflow), #250 (model-slug ellipsis, tracked by #245), and #252 (conversation viewport, tracked by #234), plus the maintenance commits #266 (design-system pin bump), #268 (unreferenced session-surface removal) and #229 (CodeQL pinned-version annotations), which need no user-facing bullets. Version metadata and frozen-notes publication safeguards are release preparation in #271, not additional runtime features.

Downloads

• macOS Apple Silicon: roleweave-0.2.0-arm64.dmg and roleweave-0.2.0-arm64.zip.
• Windows x64: roleweave-0.2.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.

The macOS app verifies an independently signed update manifest, downloads updates in the background and replaces the app on normal exit. 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.1.2 delta and update these notes in the reviewed release commit if that delta changed. Required review, 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.

v0.1.2

RoleWeave 0.1.2

This release brings the conversation context and concurrent employee work already merged into RoleWeave to the desktop installers. It also includes the Windows persistence and best-effort workspace-startup diagnostic fixes merged after v0.1.1.

Changes

• Follow-up turns can use bounded, redacted conversation history. The app shows what context was included, and the context preference persists per session.
• Different employees can work at the same time. Group conversations support parallel work and ordered relay execution; a failed relay step stops later steps and leaves a visible record.
• Group context is redacted before truncation. Persistence failures release running-turn reservations, and malformed history or a failing event subscriber cannot interrupt other group members.
• Cancellation stays bound to the original workspace and turn. Session rotation and context changes respect active personal and group turns; UI events remain scoped to the workspace, employee and engine.
• Large group messages fit the bounded history store. Relay context remains bounded, and recovery preserves the original acceptance time without duplicating work.
• Windows directory-fsync handling uses the shared atomic writer, and raw filesystem errors remain available through their wrappers. This fixes the case where a local write could report an error after its data had already reached disk.
• Workspace auto-open diagnostics remain best-effort: an unavailable stderr stream cannot turn a diagnostic write into a failed startup. Existing workspace overrides, compatibility paths and fallback behavior are preserved.
• The README now includes customer onboarding, desktop downloads, AI integration guidance and source development instructions.
• Release pages automatically use the matching versioned notes. Missing, empty, mismatched or changed notes stop release creation before anything is published.

This packet is reviewed against main revision 20f532488787c484e9db4defdd35c16aa0e86287. The post-v0.1.1 feature and fix commits are #215 (context and concurrent work, tracked by #214), #211 (Windows persistence, tracked by #155), #212 (README), and #223 (best-effort workspace diagnostics, tracked by #170). #219 corrects the group-navigation test fixture. Version metadata and the frozen-notes publication safeguards are release preparation in #227, not additional runtime features.

Downloads

• macOS Apple Silicon: roleweave-0.1.2-arm64.dmg and roleweave-0.1.2-arm64.zip.
• Windows x64: roleweave-0.1.2-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.

The macOS app verifies an independently signed update manifest, downloads updates in the background and replaces the app on normal exit. 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.1.1 delta and update these notes in the reviewed release commit if that delta changed. Required review, 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.

RoleWeave v0.1.1

RoleWeave v0.1.1

Changed

• Unified product and repository branding as RoleWeave / bytefolk/roleweave, with an R/W app icon that includes transparent padding.
• Added a side-by-side layout for role documents and integrated shared organization documents with the bytefolk/doc v1 API. Access credentials remain on the server.
• Improved project switching, employee creation, group chat member search, and the display of memory sources.

Fixed

• Fixed an issue that incorrectly rejected signed update manifests during macOS releases. Pre-release checks now validate the manifest signature, version, and ZIP size and hash.
• Standardized installer filenames, GitHub release references, and signed macOS update manifests on roleweave, preventing the updater from looking for installers under the old name.
• Preserved legacy environment variable support, workspace data migration, and the application ID. Users of older development builds must manually install the new version once; update trust checks remain unchanged.

Downloads

• macOS Apple Silicon installer (DMG)
• macOS Apple Silicon archive (ZIP)
• Windows x64 installer (EXE)

Installation Notes and Verification Scope

The macOS packages are not yet signed with an Apple Developer ID or notarized, and the Windows installer is not Authenticode-signed. Your operating system may display a security prompt during the first installation or launch. The independent Ed25519 signature on the macOS update manifest is not Apple code signing. Users of older development builds should manually install the new version once.

Native builds on both platforms, packaged app launch checks, and layout checks passed. All nine published assets were downloaded again, and their SHA-256 hashes matched. Update configuration SHA-512 hashes, the macOS update manifest signature, ZIP/DMG integrity, and application version metadata were verified. All nine assets are available for anonymous download. Installation, uninstallation, and automatic updates across versions were not tested on user machines, so these paths are not claimed as fully verified end to end.

Source commit: 61a703b356fc3fa62b8ab07166e6e6f876f678e4 · Release verification record