fix(shell-ball): listen for runtime task notifications

[gdemonc]

Summary

• Part of 任务：前端未完成部分 #327
• Subscribe shell-ball to active-task runtime notifications so task.steered and selected loop.* events can surface in the floating bubble flow
• Keep runtime notifications observation-only in shell-ball: formal visual state still follows task.updated, while task.steered, loop.retrying, and loop.failed render as lightweight local status bubbles
• Update shell-ball contract coverage to reflect the new runtime subscription and message mapping behavior

Changes

• Add active task runtime subscription in apps/desktop/src/features/shell-ball/useShellBallCoordinator.ts
• Add lightweight runtime message mapping for:
  • task.steered
  • loop.retrying
  • loop.failed
• Deduplicate runtime observation bubbles per task/event
• Extend shell-ball contract tests and subscription stubs for subscribeTaskRuntime(...)

Testing

• pnpm --dir apps/desktop typecheck
• pnpm --dir apps/desktop lint
• node -r ./scripts/registerShellBallTestAliases.cjs --test --test-name-pattern "runtime observation helper|coordinator subscribes to formal task, approval, and runtime updates" .cache/shell-ball-tests/features/shell-ball/shellBall.contract.test.js
• go test ./services/local-service/internal/rpc -run "HandleStreamConn(EmitsLoopLifecycleNotifications|FiltersRuntimeNotificationsToRequestTask)"
• go test ./services/local-service/internal/rpc -run "HandleStreamConnStreamsLoopLifecycleNotificationsBeforeResponseForSubmitInput"
• go test ./services/local-service/internal/runengine -run "(EmitRuntimeNotificationPersistsLoopStopReason|ContinueTaskMergesContinuationStateAndDrainsSteeringMessages)"
• go test ./services/local-service/internal/orchestrator -run "TaskSteerPersistsFollowUpMessage"

Notes

• This change does not alter backend or protocol behavior
• Full pnpm --dir apps/desktop test:shell-ball still has unrelated pre-existing baseline failures, so validation here uses targeted contract coverage plus backend notification tests

[fennoai]

1 finding from the review passes.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[gdemonc]

@xgopilot 解决你提到的问题

[fennoai]

Result

Fixed the race I called out in review by changing shell-ball runtime observation handling from per-task late subscription to a global runtime subscription with task-scoped buffering and replay.

What Changed

• Added subscribeAllTaskRuntime(...) in apps/desktop/src/rpc/subscriptions.ts and kept subscribeTaskRuntime(...) as the filtered wrapper for task-detail consumers.
• Updated apps/desktop/src/features/shell-ball/useShellBallCoordinator.ts to queue task.steered / loop.* notifications that arrive before the submit response registers the formal task_id, then replay them once the task is bound locally.
• Extended apps/desktop/src/features/shell-ball/shellBall.contract.test.ts with a runtime-race contract case and updated subscription stubs in apps/desktop/src/features/shell-ball/test-stubs/rpcSubscriptions.ts.

Validation

• Passed: git diff --check
• Not run: pnpm --dir apps/desktop typecheck
• Not run: pnpm --dir apps/desktop lint
• Not run: shell-ball contract test command from the PR description

The desktop workspace in this runner does not have pnpm/corepack or installed node_modules, and .cache/shell-ball-tests/... had not been generated, so I could not execute the requested local checks here.

Git

• Pushed to the PR branch: gdemonc:issue-327-shell-ball-runtime-subscriptions
• Commit: 3d36dbe (fix(shell-ball): buffer early runtime notifications)
• Fork PR helper result: fix(shell-ball): buffer early runtime notifications gdemonc/CialloClaw#8

View job run

[gdemonc]

@xgopilot 还有什么问题

[fennoai]

Review

No additional issues found in the updated patch.

I re-checked the change against origin/main...HEAD, including the new subscribeAllTaskRuntime(...) path in apps/desktop/src/rpc/subscriptions.ts and the task-scoped runtime queue/replay flow in apps/desktop/src/features/shell-ball/useShellBallCoordinator.ts. The earlier race around runtime notifications arriving before local task registration is addressed by the global subscription plus per-task_id buffering, and I did not find another behavioral regression in the changed code.

I did not rerun the desktop checks in this runner.

View job run