v0.4.0

RoleWeave 0.4.0

RoleWeave 0.4.0 brings project execution, human acceptance, approvals, and shared knowledge into the desktop workspace. It includes the 96 commits after v0.3.0 through main revision 223add9b75c972e3c3aa05416286f261fb0ce95f; the preparation commit adds version metadata and these frozen notes. The release record tracks the final reviewed source commit, checks, publication, and asset verification.

What changed

• Projects and goals: a persistent task board, priorities and schedules, assignment to employees, live execution progress, and navigation to the original conversation. Human acceptance checks every criterion against the recorded output revision before a task becomes complete; stale decisions are rejected. Goals show actual branch progress, health, evidence, and failed or blocked turns.
• Approvals and reports: a persistent approval center with contextual details, integrity-bound change previews, multi-party decisions, policy-gated batch operations, and an audit trail. The inbox connects decisions to execution evidence and exact conversations. Expired requests cannot be approved; disconnected views retain a read-only snapshot.
• Resources and notes: file browsing for connected Mem or bdpan drives, filters and selection, authorized image previews, and explicit connection/failure states. A workspace Markdown vault supports Chinese paths, full-text search, role references, conversation conclusions, version-checked history recovery, and manual Mem synchronization with conflict copies.
• Organization and relationship views: searchable organization layouts, optional 3D star maps, and relationship graphs connecting employees, sources, resources, goals, and tasks. Graphs read connected drive metadata and preserve source evidence; labels, layout, scrolling, and restore flows are clearer.
• Conversations and Agent hosts: image/PDF attachments, a visible thought/tool activity trail, live launch progress, a Gemini CLI host, and one-click Qoder sign-in. Employee switches preserve the previous view while loading and restrict actions to the selected employee. Existing per-employee Agent bindings survive reporting-line changes.
• Creation and settings: project/employee templates and explicitly accepted generated drafts, unified date/time controls, language and theme settings in Settings → General, and native Windows caption controls. New roles have read-only default tools, with working files under their own work/ territory.
• Optional local suggestions: Laya can offer collaboration, goal-health, approval-risk, and relay-stop suggestions. It is disabled by default, accepts only local loopback service endpoints, and preserves rule-based authority and bounded fallback when unavailable. Design-only memory proposals are not shipped durable-memory runtime features.
• Windows updates: unsigned Windows builds can check, download, and install an update after explicit user confirmation. Release verification checks that latest.yml identifies the actual EXE and its size and SHA-512. Build dependencies also incorporate the audited fixes already merged on main.

The complete development history remains in the 0.4.0 changelog. Native mobile clients remain source projects; this desktop release does not distribute iOS, Android, or HarmonyOS applications.

Compatibility and upgrade notes

RoleWeave remains a pre-1.0 preview. The optional inference configuration now uses ROLEWEAVE_LAYA_*; ROLEWEAVE_JEV_* is no longer read. Operators using the old opt-in configuration must migrate to the local Laya service settings. Suggestions stay disabled unless explicitly enabled.

Existing workspaces without a top-level work/ directory remain valid. New workspace initialization creates it, and hiring creates work// with read-only tools by default; write capabilities require explicit operator configuration. RoleWeave-owned execution state uses .roleweave/, and the existing attachment migration preserves older workspace attachments. External services and CLI installations remain operator-managed.

Windows v0.3.0 clients that disable in-app installation need to install the 0.4.0 EXE manually once. The updated Windows client can then download and install later updates with confirmation. Users of older Org Workbench development builds also need a manual RoleWeave installation.

Downloads

• macOS Apple Silicon: roleweave-0.4.0-arm64.dmg and roleweave-0.4.0-arm64.zip.
• Windows x64: roleweave-0.4.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 Ed25519 update manifest, downloads updates in the background and replaces the app on normal exit. This update signature does not provide Apple code-signing trust. Windows verifies installer SHA-512 against the HTTPS release feed without publisher pinning and requires explicit confirmation to download and install. Publication exposes this version to existing update clients.

CI verifies native packaging, staged startup/layout, and installer integrity. Installation, uninstallation, real provider entitlement, and cross-version updates on user machines still require separate product validation; mocked startup checks do not establish those results.

Publisher handoff

Prepare this release through the ByteFolk release process: independent final-head review, protected squash merge, exact-commit checks, version/ref absence checks, and tag-protection readback. An eligible release actor creates the annotated tag once from the recorded main commit. Do not use a manual dispatch to bypass tag permissions.

The existing workflow freezes docs/releases/vVERSION.md from that commit, checks the notes digest, uploads installers to a draft, and reads back the inventory before publishing. Tag pushes publish automatically after those checks. Stop before publication if a gate fails; correct a defective published artifact with a new patch version, never by moving the tag or replacing assets.