@excitedjs/dreamux 0.24.0-beta.205 → 0.24.0
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/CHANGELOG.json +20 -0
- package/CHANGELOG.md +8 -1
- package/package.json +4 -4
package/CHANGELOG.json
CHANGED
|
@@ -1,6 +1,26 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@excitedjs/dreamux",
|
|
3
3
|
"entries": [
|
|
4
|
+
{
|
|
5
|
+
"version": "0.24.0",
|
|
6
|
+
"tag": "@excitedjs/dreamux_v0.24.0",
|
|
7
|
+
"date": "Sun, 06 Sep 2026 09:34:07 GMT",
|
|
8
|
+
"comments": {
|
|
9
|
+
"minor": [
|
|
10
|
+
{
|
|
11
|
+
"comment": "BREAKING: The bundled `team-workflow` skill is renamed `teamwork` and the shared `workflow` skill is renamed `dynamic-workflow`, with both new names reserved like the old ones, and the channel MCP server is named after its provider instead of its configured channel id, so the fully qualified tool name a model calls changes on both engines — `mcp__channel-<id>__reply` becomes `mcp__channel-feishu__reply` on Claude Code, and `channel_<id>__…` becomes `channel_feishu__…` on Codex — while the tool's own local name, its input/output schema, its result shape, `channels[].id`, and routing state are all unchanged. Rebuild: before restarting a Team created with custom `skill_sources`, rename any custom skill directory named `teamwork` or `dynamic-workflow`; `team.create` now rejects such a root, and an existing Team's Claude Code TeamLeader fails at its next start with `duplicate Claude skill name` until the rename. No config or persisted state changes shape, so nothing else needs a rebuild. A managed worktree requested without `cleanup` now defaults to `delete-on-close` — it is removed when its agent closes or its Team dissolves and the tree is clean; pass `cleanup: keep` to retain it (identities created before this release keep the `cleanup` they recorded). Dispatcher and TeamLeader role prompts are reduced to identity plus the MCP server map; the rules those prompts used to state are either owned once by the surface nearest the action (a dispatch-result reminder, a tool description, or the channel's own reminder) or dropped. The dispatch-result reminders (spawn/send/team.create with a prompt/team.send/workflow_run) now state the consequence the caller cannot see — the result arrives later as a pushed message, so there is nothing to report or predict in the meantime — and the matching hand-off tool descriptions state the same fact as a short contract sentence for the engine where the reminder text itself is not visible. `teamwork`, `dynamic-workflow`, and `dispatcher-workflow` carry narrow load triggers: load only when about to spawn or send to a TeamMate, create or send to a Team, or write or run a workflow script, never as a standing condition of the turn. A Team-scoped TeamMate's system prompt now opens with an identity sentence naming its Team (an ordinary TeamMate is also told that its TeamLeader receives what it outputs; a workflow agent is not, since the workflow consumes its output). A TeamLeader's prompt names the Team's workspace and its cleanup mode; the TeamLeader-facing `dissolve` description states what the mode means at dissolve and asks it to check a `delete-on-close` worktree for uncommitted, untracked, or unmerged work before dissolving. `team.status` now reports the Team's `worktree_mode` and `worktree_cleanup_mode` next to the lifecycle state `worktree_cleanup`, so a Dispatcher can tell whether a dissolve removes the Team's worktree. A pushed completion notification now states once that it is an automated Dreamux notification, not a message from the user. Every Dreamux MCP tool input property carries a description, and tool descriptions carry the operational cautions role prompts used to state — this continues PR #369's relocation work, which was not merged and ships through this PR instead."
|
|
12
|
+
}
|
|
13
|
+
],
|
|
14
|
+
"dependency": [
|
|
15
|
+
{
|
|
16
|
+
"comment": "Updating dependency \"@excitedjs/agent-runtime-claude-code\" to `0.6.1`"
|
|
17
|
+
},
|
|
18
|
+
{
|
|
19
|
+
"comment": "Updating dependency \"@excitedjs/feishu-channel\" to `6.1.0`"
|
|
20
|
+
}
|
|
21
|
+
]
|
|
22
|
+
}
|
|
23
|
+
},
|
|
4
24
|
{
|
|
5
25
|
"version": "0.23.0",
|
|
6
26
|
"tag": "@excitedjs/dreamux_v0.23.0",
|
package/CHANGELOG.md
CHANGED
|
@@ -1,6 +1,13 @@
|
|
|
1
1
|
# Change Log - @excitedjs/dreamux
|
|
2
2
|
|
|
3
|
-
This log was last generated on
|
|
3
|
+
This log was last generated on Sun, 06 Sep 2026 09:34:08 GMT and should not be manually modified.
|
|
4
|
+
|
|
5
|
+
## 0.24.0
|
|
6
|
+
Sun, 06 Sep 2026 09:34:07 GMT
|
|
7
|
+
|
|
8
|
+
### Minor changes
|
|
9
|
+
|
|
10
|
+
- BREAKING: The bundled `team-workflow` skill is renamed `teamwork` and the shared `workflow` skill is renamed `dynamic-workflow`, with both new names reserved like the old ones, and the channel MCP server is named after its provider instead of its configured channel id, so the fully qualified tool name a model calls changes on both engines — `mcp__channel-<id>__reply` becomes `mcp__channel-feishu__reply` on Claude Code, and `channel_<id>__…` becomes `channel_feishu__…` on Codex — while the tool's own local name, its input/output schema, its result shape, `channels[].id`, and routing state are all unchanged. Rebuild: before restarting a Team created with custom `skill_sources`, rename any custom skill directory named `teamwork` or `dynamic-workflow`; `team.create` now rejects such a root, and an existing Team's Claude Code TeamLeader fails at its next start with `duplicate Claude skill name` until the rename. No config or persisted state changes shape, so nothing else needs a rebuild. A managed worktree requested without `cleanup` now defaults to `delete-on-close` — it is removed when its agent closes or its Team dissolves and the tree is clean; pass `cleanup: keep` to retain it (identities created before this release keep the `cleanup` they recorded). Dispatcher and TeamLeader role prompts are reduced to identity plus the MCP server map; the rules those prompts used to state are either owned once by the surface nearest the action (a dispatch-result reminder, a tool description, or the channel's own reminder) or dropped. The dispatch-result reminders (spawn/send/team.create with a prompt/team.send/workflow_run) now state the consequence the caller cannot see — the result arrives later as a pushed message, so there is nothing to report or predict in the meantime — and the matching hand-off tool descriptions state the same fact as a short contract sentence for the engine where the reminder text itself is not visible. `teamwork`, `dynamic-workflow`, and `dispatcher-workflow` carry narrow load triggers: load only when about to spawn or send to a TeamMate, create or send to a Team, or write or run a workflow script, never as a standing condition of the turn. A Team-scoped TeamMate's system prompt now opens with an identity sentence naming its Team (an ordinary TeamMate is also told that its TeamLeader receives what it outputs; a workflow agent is not, since the workflow consumes its output). A TeamLeader's prompt names the Team's workspace and its cleanup mode; the TeamLeader-facing `dissolve` description states what the mode means at dissolve and asks it to check a `delete-on-close` worktree for uncommitted, untracked, or unmerged work before dissolving. `team.status` now reports the Team's `worktree_mode` and `worktree_cleanup_mode` next to the lifecycle state `worktree_cleanup`, so a Dispatcher can tell whether a dissolve removes the Team's worktree. A pushed completion notification now states once that it is an automated Dreamux notification, not a message from the user. Every Dreamux MCP tool input property carries a description, and tool descriptions carry the operational cautions role prompts used to state — this continues PR #369's relocation work, which was not merged and ships through this PR instead.
|
|
4
11
|
|
|
5
12
|
## 0.23.0
|
|
6
13
|
Fri, 04 Sep 2026 10:24:24 GMT
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@excitedjs/dreamux",
|
|
3
|
-
"version": "0.24.0
|
|
3
|
+
"version": "0.24.0",
|
|
4
4
|
"description": "Dreamux core host for multi-dispatcher agent orchestration through provider interfaces.",
|
|
5
5
|
"license": "MIT",
|
|
6
6
|
"repository": {
|
|
@@ -26,8 +26,6 @@
|
|
|
26
26
|
"CHANGELOG.json"
|
|
27
27
|
],
|
|
28
28
|
"dependencies": {
|
|
29
|
-
"@excitedjs/agent-runtime-claude-code": "0.6.1-beta.205",
|
|
30
|
-
"@excitedjs/feishu-channel": "6.1.0-beta.205",
|
|
31
29
|
"@modelcontextprotocol/server": "2.0.0",
|
|
32
30
|
"acorn": "^8.16.0",
|
|
33
31
|
"croner": "^10.0.1",
|
|
@@ -37,9 +35,11 @@
|
|
|
37
35
|
"execa": "^9.6.1",
|
|
38
36
|
"pino": "^9.5.0",
|
|
39
37
|
"plist": "^5.0.0",
|
|
38
|
+
"@excitedjs/agent-runtime-claude-code": "0.6.1",
|
|
40
39
|
"@excitedjs/agent-runtime-codex": "0.5.0",
|
|
41
40
|
"@excitedjs/dreamux-utils": "0.5.0",
|
|
42
|
-
"@excitedjs/dreamux-types": "0.9.0"
|
|
41
|
+
"@excitedjs/dreamux-types": "0.9.0",
|
|
42
|
+
"@excitedjs/feishu-channel": "6.1.0"
|
|
43
43
|
},
|
|
44
44
|
"devDependencies": {
|
|
45
45
|
"@modelcontextprotocol/client": "2.0.0",
|