[Feature]: QwenPaw Traffic Light

## Summary
I've been using QwenPaw frequently for daily tasks and development work. Sometimes the processing takes a long time, so I switch to other windows to keep working, but I often forget the current status. This traffic light lets me clearly see whether I should come back and click Yes.
Added a QwenPaw traffic light status indicator, packaged as a plugin. It has already been submitted at[traffic-light](https://github.com/Single430/traffic-light) . I noticed the upload channel isn't open yet — hoping it can be integrated in the future.

An always-on-top desktop traffic light that shows what your QwenPaw agents
are doing — visible from any window:


| Lamp | Meaning |
|---|---|
| 🟢 Green | everything idle / done |
| 🟡 Yellow | an agent is working |
| 🔴 Red (blinking) | an agent is blocked and needs you |

Hand an agent a long task, switch away, and just glance at the lamp:
green = come back for the result, blinking red = it's waiting for you.

现在经常用QwenPaw 处理日常工作，开发什么的，有时这个处理的流程时间比较长，就切换页面去其他窗口工作，会忘了进行的状态，用这个红绿灯可以让人清晰的知道是不是该回来点**Yes**了
增加QwenPaw 红绿灯状态灯，已打包成插件形式，目前已提交 [traffic-light](https://github.com/Single430/traffic-light)，看到上传途径还未开放，希望后续可以集成

一个置顶桌面的红绿灯小挂件，让你切到任何窗口也能一眼知道 QwenPaw 智能体的状态：

| 灯 | 含义 |
|---|---|
| 🟢 绿灯 | 全部空闲 / 任务完成 |
| 🟡 黄灯 | 有智能体正在干活 |
| 🔴 红灯（闪烁） | 有智能体被卡住，需要你回来处理 |

交给智能体一个长任务后切去干别的，黄灯变绿 = 回来看结果；红灯闪烁 = 它在等你。

[One or two sentences: what do you want and why?]

## Component(s) Affected

- [ ] Core / Backend (app, agents, config, providers, utils, local_models)
- [ ] Console (frontend web UI)
- [ ] Channels (DingTalk, Feishu, QQ, Discord, iMessage, etc.)
- [ ] Skills
- [ ] CLI
- [ ] Documentation (website)
- [ ] Tests
- [ ] CI/CD
- [ ] Scripts / Deploy

## Problem / Motivation

[What problem does this solve? Who benefits?]

## Proposed Solution

[Describe the feature or change you have in mind. Be as specific as possible.]

## Alternatives Considered

[Any other approaches or workarounds you thought about.]

## Additional Context

[Screenshots, examples, links to docs or similar features elsewhere.]

## Willing to Contribute

- [ ] I am willing to open a PR for this feature (after discussion).

No source files or tests are named, so begin with the QwenPaw docs or entry points for plugin upload/distribution and external integrations. Confirm how core agent state (idle/working/blocked) is emitted today and where a desktop plugin can subscribe to those updates. Review the external traffic-light repository to align behavior, then wire and expose it through the existing integration path. A completed integration should make the lamp show the three states from any window and be installable through QwenPaw’s current plugin channel.

Vom Indexierungsmodell aus dem Issue-Text verfasst.