chore(release): publish v0.4.3

Author: ChesterRa

desktop/src-tauri/capabilities/default.json

@@ -6,7 +6,6 @@
   "permissions": [
     "core:default",
     "core:event:default",
-    "core:window:allow-close",
     "core:window:allow-start-dragging",
     "opener:default",
     "notification:default",

desktop/src-tauri/src/lib.rs

@@ -98,6 +98,21 @@ fn toggle_panel_window(window: tauri::WebviewWindow, state: State<'_, RuntimeSta
     manager.toggle_panel_window(window.app_handle(), group_id)
 }
 
+#[tauri::command]
+fn close_pet_window(window: tauri::WebviewWindow, state: State<'_, RuntimeState>) -> Result<(), String> {
+    let label = window.label().to_string();
+    let group_id = label
+        .strip_prefix("pet-")
+        .ok_or_else(|| format!("unsupported pet window label {}", label))?;
+
+    let manager = state
+        .window_manager
+        .lock()
+        .map_err(|_| "window manager mutex poisoned".to_string())?;
+    manager.hide_pet_window_ui(window.app_handle(), group_id);
+    Ok(())
+}
+
 #[tauri::command]
 fn resize_panel_window(
     window: tauri::WebviewWindow,
@@ -172,6 +187,7 @@ pub fn run() {
         .invoke_handler(tauri::generate_handler![
             open_cccc_web,
             toggle_panel_window,
+            close_pet_window,
             resize_panel_window,
             get_panel_data,
         ])

desktop/src/ipc.js

@@ -58,8 +58,8 @@ closeBtn.addEventListener("pointerup", (event) => {
   event.preventDefault();
   event.stopPropagation();
   if (window.__TAURI__) {
-    const win = window.__TAURI__.window.getCurrentWindow();
-    void win.close();
+    const { invoke } = window.__TAURI__.core;
+    void invoke("close_pet_window");
   } else {
     console.log("[IPC] Close button clicked (demo mode)");
   }

docs/release/v0.4.3_release_notes.md

@@ -0,0 +1,86 @@
+# CCCC v0.4.3 Release Notes
+
+`v0.4.3` is a major refinement release over `v0.4.2`.
+It tightens the core collaboration model, reduces prompt and control-plane drift, hardens Windows and runtime integration, and makes long-running group operation more predictable across Web, MCP, IM, and Group Space workflows.
+
+## Highlights
+
+## 1) Prompt, help, and role guidance were re-layered
+
+The guidance stack was simplified so stable startup rules, live runtime guidance, and actor-specific notes no longer compete with each other.
+
+Key changes:
+
+- the startup prompt is slimmer and more focused on durable operating rules
+- live runtime guidance now belongs to `cccc_help`, so optional capability-specific instructions appear only when actually relevant
+- actor role notes are now canonically stored in the group help document `@actor` blocks instead of leaking into working-state fields
+- agent working stance and role guidance are now more clearly separated, which reduces confusion between long-term role intent and current execution context
+
+## 2) Context and task authority semantics were hardened
+
+Several core collaboration boundaries were tightened so the system behaves more predictably under real multi-actor usage.
+
+This includes:
+
+- `task.restore` now follows a clear archived-only precondition and matches the same authority model as the other task-mutating operations
+- peers can no longer mutate arbitrary unassigned tasks; task control is limited to the actor actually responsible for the work
+- actor-owned `agent_state` semantics are now aligned across docs, daemon behavior, MCP tooling, and Web expectations
+- system-driven task-to-working-state synchronization remains in place where it materially reduces manual upkeep cost
+
+## 3) Group Space and memory workflows became more coherent
+
+`v0.4.3` significantly improves the operational behavior of notebook-backed workflows.
+
+Key improvements:
+
+- work-lane and memory-lane status now track the current binding more accurately instead of leaking stale sync residue after unbind/rebind cycles
+- NotebookLM-related runtime guidance is injected only when the relevant capability is actually active
+- the login, bind, use, unbind, and disconnect flow is cleaner from both the daemon and Web state-model perspective
+- memory and daily-memory coordination stays intentionally connected, but the surrounding guidance and runtime status are now clearer
+
+## 4) Runtime support and Windows robustness were strengthened
+
+This release continues the push toward a more disciplined and supportable runtime surface.
+
+Highlights:
+
+- Windows MCP reliability was hardened, including runtime-context resolution and stdio/encoding robustness
+- the officially supported runtime surface was narrowed and clarified to the runtimes CCCC can set up and operate reliably
+- standalone Web startup now follows the same local-first binding model as the main CLI entrypoint
+- release verification was tightened to better match the project's claimed Linux, macOS, and Windows support surface
+
+## 5) Operator-facing surfaces saw broad stabilization
+
+A large amount of polish landed across the everyday control surfaces used by operators and agent teams.
+
+Notable areas:
+
+- user-scoped actor profiles now work end to end across daemon, Web, and MCP paths
+- IM integration continued to improve, especially around DingTalk sender identity, revoke behavior, `@` targeting, and streaming fallback behavior
+- blueprint export/import portability was fixed so round-trips keep the intended portable fields
+- Web settings, modal behavior, overflow handling, context presentation, and translation coverage were substantially cleaned up
+- global browser surfaces were trimmed so scoped users see less irrelevant machine-global data by default
+
+## Validation Summary
+
+The `0.4.3` line was stabilized through multiple release candidates and targeted regression work across the highest-risk areas, including:
+
+- context and task authority rules
+- role-notes source-of-truth handling
+- Group Space bind/unbind status correctness
+- Windows MCP stability
+- scoped actor profiles and permission boundaries
+- IM bridge revoke and delivery behavior
+- blueprint round-trip portability
+
+## Upgrade Notes
+
+From `v0.4.2`, this is still a drop-in minor upgrade for most deployments.
+No explicit data migration step is required.
+
+Recommended post-upgrade checks:
+
+1. restart the daemon and Web once to ensure all runtime surfaces are on the new prompt/help/control-plane behavior
+2. if you use custom help or prompt overrides, re-check your local overrides against the new guidance layering
+3. if you use Group Space or NotebookLM workflows, verify current lane bindings and status after the upgrade
+4. if you use scoped users, actor profiles, or remote/browser access, verify one non-admin path end to end

pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "cccc-pair"
-version = "0.4.3rc4"
+version = "0.4.3"
 description = "Global multi-agent delivery kernel with working groups, scopes, and an append-only collaboration ledger"
 readme = { file = "README.md", content-type = "text/markdown" }
 requires-python = ">=3.9"

tests/test_web_group_settings_desktop_pet.py

@@ -131,6 +131,23 @@ def test_launch_token_endpoint_returns_current_scoped_token(self) -> None:
         finally:
             cleanup()
 
+    def test_launch_token_endpoint_allows_empty_token_when_no_access_tokens_exist(self) -> None:
+        from cccc.ports.web.app import create_app
+
+        _, cleanup = self._with_home()
+        try:
+            group_id = self._create_group()
+            app = create_app()
+            client = TestClient(app)
+
+            resp = client.get(f"/api/v1/groups/{group_id}/desktop_pet/launch_token")
+            self.assertEqual(resp.status_code, 200)
+            body = resp.json()
+            self.assertTrue(body.get("ok"))
+            self.assertEqual((body.get("result") or {}).get("token"), "")
+        finally:
+            cleanup()
+
     def test_launch_token_endpoint_respects_group_scope(self) -> None:
         from cccc.kernel.access_tokens import create_access_token
         from cccc.ports.web.app import create_app