@qilin-agent/experimental-schedule-bundle 3.1.11 → 3.1.12

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.i18n.yaml CHANGED
@@ -15,14 +15,14 @@
15
15
  en: d152484eb41ac6b4
16
16
  zh: 364c80ee00a374ff
17
17
  /qilin-agent-experimental-schedule-bundle/use-this-package:
18
- en: 888651544355f724
19
- zh: 1bb3f2f055755b91
18
+ en: 312896e9febbe781
19
+ zh: 87bc8f496bab6b48
20
20
  /qilin-agent-experimental-schedule-bundle/understand-the-implementation:
21
21
  en: a444a25df4e2d95c
22
22
  zh: 734725df58302050
23
23
  /qilin-agent-experimental-schedule-bundle/understand-the-implementation/why-the-bundle-is-kept:
24
- en: ecc4ceb59579dfec
25
- zh: 47c3fb5f795b2e91
24
+ en: 189655ce0b86b877
25
+ zh: be6ec468c58bf03a
26
26
  /qilin-agent-experimental-schedule-bundle/further-exploration:
27
27
  en: 83b88b7123bdbb56
28
28
  zh: 3c5c644eb1b99d10
package/README.md CHANGED
@@ -25,7 +25,7 @@ This optional bundle inserts the three Schedule rows the shipped Web composition
25
25
  <a id="use-this-package"></a>
26
26
  ## Use this package
27
27
 
28
- Open Plugins in the Web sidebar and enable Automation tasks, marked by an alarm clock icon. A live root Agent then receives `schedule_create`, `schedule_list`, `schedule_view`, and `schedule_edit`, the Session header shows its reminder catalog, the sidebar's Automation tasks entry opens the task-management page and the right Sidebar holds the selected task's detail, and each eligible step appends one clock reading with the current time, the browser zone attached to the open request, and the elapsed time since the preceding model-visible message. The bundle's page lists Time awareness, Task scheduling, and Task interface with their state. Disabling the bundle restores the shipped composition; stored tasks remain on disk.
28
+ The browser profile templates select this bundle, so Automation tasks is on in Web and Desktop and has no switch anywhere. A live root Agent receives `schedule_create`, `schedule_list`, `schedule_view`, and `schedule_edit`, the Session header shows its reminder catalog, the sidebar's Automation tasks entry opens the task-management page and the right Sidebar holds the selected task's detail, and each eligible step appends one clock reading with the current time, the browser zone attached to the open request, and the elapsed time since the preceding model-visible message. The bundle's page lists Time awareness, Task scheduling, and Task interface with their state. The bundle has no page in Plugins; stored tasks remain on disk.
29
29
 
30
30
  -----
31
31
 
@@ -49,7 +49,7 @@ Open Plugins in the Web sidebar and enable Automation tasks, marked by an alarm
49
49
 
50
50
  ### Why the bundle is kept
51
51
 
52
- Upstream composes the `schedule` service row and the `ui-schedule` page row in the web-app patch and keeps the clock row and the four reminder tools in each preset. This deployment keeps all three rows in this opt-in bundle and the four tools in the shipped `ptc` preset, and it does not retire the bundle into the Web composition.
52
+ Upstream composes the `schedule` service row and the `ui-schedule` page row in the web-app patch and keeps the clock row and the four reminder tools in each preset. This deployment keeps all three rows in this opt-in bundle and the four tools in the shipped `coding` preset, and it does not retire the bundle into the Web composition.
53
53
 
54
54
  - One selection carries the capability together: the service, the page, and the clock reading switch on and off as a unit, and disabling restores the composition without a rebuild or a release.
55
55
  - The enablement path already exists elsewhere: `OPTIONAL_BUNDLES` offers the bundle in the Official group, and [the user guide](../../../docs/user/guide/schedule.md) and [the subsystem page](../../../docs/subsystems/schedule.md) name it as the way to add Schedule to a shipped Web profile.
package/README.zh.md CHANGED
@@ -25,7 +25,7 @@ kind: "package-bundle"
25
25
  <a id="use-this-package"></a>
26
26
  ## 使用此包
27
27
 
28
- 打开 Web 侧栏的插件管理页并启用带闹钟图标的“自动化任务”。此后,活跃的根智能体获得 `schedule_create`、`schedule_list`、`schedule_view` 与 `schedule_edit`,会话头部显示提醒目录,侧栏的自动化任务入口打开任务管理页面、右侧栏承载所选任务的详情,每个符合条件的步骤追加一条时钟读数,包含当前时间、打开请求所带的浏览器时区,以及距上一条模型可见消息的经过时间。此 Bundle 的页面列出时间感知、任务调度与任务界面及其状态。禁用此 Bundle 会恢复随包组合;已存储的任务保留在磁盘上。
28
+ 浏览器端 profile 模板默认选中本 Bundle,因此在 Web 与 Desktop 中「自动化任务」始终开启,界面没有任何开关。活跃的根智能体获得 `schedule_create`、`schedule_list`、`schedule_view` 与 `schedule_edit`,会话头部显示提醒目录,侧栏的自动化任务入口打开任务管理页面、右侧栏承载所选任务的详情,每个符合条件的步骤追加一条时钟读数,包含当前时间、打开请求所带的浏览器时区,以及距上一条模型可见消息的经过时间。此 Bundle 的页面列出时间感知、任务调度与任务界面及其状态。本 Bundle 在插件管理页不设卡片;已存储的任务保留在磁盘上。
29
29
 
30
30
  -----
31
31
 
@@ -49,7 +49,7 @@ kind: "package-bundle"
49
49
 
50
50
  ### 为何保留此 Bundle
51
51
 
52
- 上游把 `schedule` 服务条目与 `ui-schedule` 页面条目组合在 web-app 补丁中,并把时钟条目与四个提醒工具保留在各 preset 中。本部署把三个条目留在可选的 Bundle 中、把四个工具留在随包交付的 `ptc` preset 中,并且不把该 Bundle 退役进 Web 组合。
52
+ 上游把 `schedule` 服务条目与 `ui-schedule` 页面条目组合在 web-app 补丁中,并把时钟条目与四个提醒工具保留在各 preset 中。本部署把三个条目留在可选的 Bundle 中、把四个工具留在随包交付的 `coding` preset 中,并且不把该 Bundle 退役进 Web 组合。
53
53
 
54
54
  - 一次选择即整体承载能力:服务、页面与时钟读数一起开关,禁用即恢复原有组合,无需重新构建或发版。
55
55
  - 启用路径已存在于别处:`OPTIONAL_BUNDLES` 在“官方”分组提供该 Bundle,[用户指南](../../../docs/user/guide/schedule.zh.md)与[子系统页](../../../docs/subsystems/schedule.zh.md)都把它写作为随包 Web profile 加入定时的方式。
package/package.json CHANGED
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "@qilin-agent/experimental-schedule-bundle",
3
3
  "description": "Optional bundle that adds Schedule, its task page, and time context to the Web composition",
4
- "version": "3.1.11",
4
+ "version": "3.1.12",
5
5
  "icon": "./icon.svg",
6
6
  "publishConfig": {
7
7
  "access": "public"
@@ -33,9 +33,9 @@
33
33
  ],
34
34
  "license": "MIT",
35
35
  "dependencies": {
36
- "@qilin-agent/client-ui-schedule": "3.1.11",
37
- "@qilin-agent/schedule": "3.1.11",
38
- "@qilin-agent/time-context": "3.1.11"
36
+ "@qilin-agent/client-ui-schedule": "3.1.12",
37
+ "@qilin-agent/schedule": "3.1.12",
38
+ "@qilin-agent/time-context": "3.1.12"
39
39
  },
40
40
  "peerDependencies": {
41
41
  "@qilin-agent/kylin": "~4.0.7"