@excitedjs/dreamux 0.25.0-beta.236 → 0.25.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 +63 -0
- package/CHANGELOG.md +19 -1
- package/package.json +7 -7
package/CHANGELOG.json
CHANGED
|
@@ -1,6 +1,69 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@excitedjs/dreamux",
|
|
3
3
|
"entries": [
|
|
4
|
+
{
|
|
5
|
+
"version": "0.25.0",
|
|
6
|
+
"tag": "@excitedjs/dreamux_v0.25.0",
|
|
7
|
+
"date": "Thu, 10 Sep 2026 04:59:50 GMT",
|
|
8
|
+
"comments": {
|
|
9
|
+
"none": [
|
|
10
|
+
{
|
|
11
|
+
"comment": "Drop the unused `inviteMembers` fake from the Feishu bot test helper."
|
|
12
|
+
},
|
|
13
|
+
{
|
|
14
|
+
"comment": "Define BREAKING in Rush change notes strictly as an upgrade-blocking config or persisted-file migration: a note leads with BREAKING: and Rebuild: only when the upgraded daemon or CLI cannot start until the operator migrates by hand. API, MCP, CLI contract changes and behavior changes that leave persisted files readable are ordinary notes and never use BREAKING:, Rebuild:, or Review:. The superseded same-shape semantic BREAKING: Review: category is removed from the rule docs."
|
|
15
|
+
}
|
|
16
|
+
],
|
|
17
|
+
"minor": [
|
|
18
|
+
{
|
|
19
|
+
"comment": "The teammate.spawn and team.create MCP tools no longer accept repo.slug in their repo input; the repo schema is closed, so a call that passes slug now fails input validation before the handler runs. The worktree directory and default branch already derive from the allocated entity name (dreamux/<teammate_name>, or dreamux/team-<team_name> for a Team), and repo.branch still overrides the default. Existing worktrees, persisted state, and canonical Commands are unchanged."
|
|
20
|
+
},
|
|
21
|
+
{
|
|
22
|
+
"comment": "Adds the team.interrupt Command and includes the TeamLeader runtime in team.list. A non-forced team.dissolve now checks worktree reclaimability before returning its receipt, so a blocked dissolve is rejected while the Team is still open."
|
|
23
|
+
},
|
|
24
|
+
{
|
|
25
|
+
"comment": "Return the TeamLeader runtime ID and runtime cwd directly from team.create so callers do not need a follow-up status query."
|
|
26
|
+
},
|
|
27
|
+
{
|
|
28
|
+
"comment": "Add the provider-neutral `channel.list` Core command: lists the dispatcher's configured Channels in config order as `{channel_id, provider, identity, live}` without starting any Channel session. Additive; no existing command, tool, or state changes."
|
|
29
|
+
},
|
|
30
|
+
{
|
|
31
|
+
"comment": "Publish tool call arguments and invocations to conversation displays exactly as the runtime wrote them, without secret masking or workspace/home path renaming; summaries, items, results, and message bodies keep their existing redaction. Completion push-backs now also state which TeamMate or Workflow reported, so a display can label them without parsing the notification body."
|
|
32
|
+
},
|
|
33
|
+
{
|
|
34
|
+
"comment": "Callers of team.create and team.status must consume the same flat Team summary and lifecycle status; create no longer reports an operation outcome, and member_count on a live Team now counts member-directory occupancy (closed and unreadable members included) instead of readable members. team.list keeps its compact row with the same field names and meanings."
|
|
35
|
+
}
|
|
36
|
+
],
|
|
37
|
+
"patch": [
|
|
38
|
+
{
|
|
39
|
+
"comment": "Stop pushing a stopped completion into the owner whose own close, Workflow stop, Team dissolve, or service stop ended the work. A stopping dispatcher delivers nothing that settles behind its fence; an independently failed or stopped turn is still reported once."
|
|
40
|
+
},
|
|
41
|
+
{
|
|
42
|
+
"comment": "The bundled `teamwork` skill now tells a TeamLeader what a member has that a subagent does not, a judgment of its own, and how to use it: the brief carries the question the work turns on before the leader's answer, the leader's design is marked as a guess, a member's identity includes standing to contradict the leader's framing, and when review rounds keep adding mechanism to one area the leader stops patching, writes the premise, and puts it to members that have not seen the draft. No skill name, description, or load trigger changes."
|
|
43
|
+
},
|
|
44
|
+
{
|
|
45
|
+
"comment": "Restore explicit no-polling guidance on task dispatch receipts and forward Channel-owned success text through MCP."
|
|
46
|
+
}
|
|
47
|
+
],
|
|
48
|
+
"dependency": [
|
|
49
|
+
{
|
|
50
|
+
"comment": "Updating dependency \"@excitedjs/agent-runtime-claude-code\" to `0.7.0`"
|
|
51
|
+
},
|
|
52
|
+
{
|
|
53
|
+
"comment": "Updating dependency \"@excitedjs/agent-runtime-codex\" to `0.6.0`"
|
|
54
|
+
},
|
|
55
|
+
{
|
|
56
|
+
"comment": "Updating dependency \"@excitedjs/dreamux-types\" to `0.10.0`"
|
|
57
|
+
},
|
|
58
|
+
{
|
|
59
|
+
"comment": "Updating dependency \"@excitedjs/dreamux-utils\" to `0.5.1`"
|
|
60
|
+
},
|
|
61
|
+
{
|
|
62
|
+
"comment": "Updating dependency \"@excitedjs/feishu-channel\" to `6.2.0`"
|
|
63
|
+
}
|
|
64
|
+
]
|
|
65
|
+
}
|
|
66
|
+
},
|
|
4
67
|
{
|
|
5
68
|
"version": "0.24.0",
|
|
6
69
|
"tag": "@excitedjs/dreamux_v0.24.0",
|
package/CHANGELOG.md
CHANGED
|
@@ -1,6 +1,24 @@
|
|
|
1
1
|
# Change Log - @excitedjs/dreamux
|
|
2
2
|
|
|
3
|
-
This log was last generated on
|
|
3
|
+
This log was last generated on Thu, 10 Sep 2026 04:59:50 GMT and should not be manually modified.
|
|
4
|
+
|
|
5
|
+
## 0.25.0
|
|
6
|
+
Thu, 10 Sep 2026 04:59:50 GMT
|
|
7
|
+
|
|
8
|
+
### Minor changes
|
|
9
|
+
|
|
10
|
+
- The teammate.spawn and team.create MCP tools no longer accept repo.slug in their repo input; the repo schema is closed, so a call that passes slug now fails input validation before the handler runs. The worktree directory and default branch already derive from the allocated entity name (dreamux/<teammate_name>, or dreamux/team-<team_name> for a Team), and repo.branch still overrides the default. Existing worktrees, persisted state, and canonical Commands are unchanged.
|
|
11
|
+
- Adds the team.interrupt Command and includes the TeamLeader runtime in team.list. A non-forced team.dissolve now checks worktree reclaimability before returning its receipt, so a blocked dissolve is rejected while the Team is still open.
|
|
12
|
+
- Return the TeamLeader runtime ID and runtime cwd directly from team.create so callers do not need a follow-up status query.
|
|
13
|
+
- Add the provider-neutral `channel.list` Core command: lists the dispatcher's configured Channels in config order as `{channel_id, provider, identity, live}` without starting any Channel session. Additive; no existing command, tool, or state changes.
|
|
14
|
+
- Publish tool call arguments and invocations to conversation displays exactly as the runtime wrote them, without secret masking or workspace/home path renaming; summaries, items, results, and message bodies keep their existing redaction. Completion push-backs now also state which TeamMate or Workflow reported, so a display can label them without parsing the notification body.
|
|
15
|
+
- Callers of team.create and team.status must consume the same flat Team summary and lifecycle status; create no longer reports an operation outcome, and member_count on a live Team now counts member-directory occupancy (closed and unreadable members included) instead of readable members. team.list keeps its compact row with the same field names and meanings.
|
|
16
|
+
|
|
17
|
+
### Patches
|
|
18
|
+
|
|
19
|
+
- Stop pushing a stopped completion into the owner whose own close, Workflow stop, Team dissolve, or service stop ended the work. A stopping dispatcher delivers nothing that settles behind its fence; an independently failed or stopped turn is still reported once.
|
|
20
|
+
- The bundled `teamwork` skill now tells a TeamLeader what a member has that a subagent does not, a judgment of its own, and how to use it: the brief carries the question the work turns on before the leader's answer, the leader's design is marked as a guess, a member's identity includes standing to contradict the leader's framing, and when review rounds keep adding mechanism to one area the leader stops patching, writes the premise, and puts it to members that have not seen the draft. No skill name, description, or load trigger changes.
|
|
21
|
+
- Restore explicit no-polling guidance on task dispatch receipts and forward Channel-owned success text through MCP.
|
|
4
22
|
|
|
5
23
|
## 0.24.0
|
|
6
24
|
Sun, 06 Sep 2026 09:34:07 GMT
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@excitedjs/dreamux",
|
|
3
|
-
"version": "0.25.0
|
|
3
|
+
"version": "0.25.0",
|
|
4
4
|
"description": "Dreamux core host for multi-dispatcher agent orchestration through provider interfaces.",
|
|
5
5
|
"license": "MIT",
|
|
6
6
|
"repository": {
|
|
@@ -26,11 +26,6 @@
|
|
|
26
26
|
"CHANGELOG.json"
|
|
27
27
|
],
|
|
28
28
|
"dependencies": {
|
|
29
|
-
"@excitedjs/agent-runtime-claude-code": "0.7.0-beta.236",
|
|
30
|
-
"@excitedjs/agent-runtime-codex": "0.6.0-beta.236",
|
|
31
|
-
"@excitedjs/dreamux-types": "0.10.0-beta.236",
|
|
32
|
-
"@excitedjs/dreamux-utils": "0.5.1-beta.236",
|
|
33
|
-
"@excitedjs/feishu-channel": "6.2.0-beta.236",
|
|
34
29
|
"@modelcontextprotocol/server": "2.0.0",
|
|
35
30
|
"acorn": "^8.16.0",
|
|
36
31
|
"croner": "^10.0.1",
|
|
@@ -39,7 +34,12 @@
|
|
|
39
34
|
"@clack/prompts": "^1.5.0",
|
|
40
35
|
"execa": "^9.6.1",
|
|
41
36
|
"pino": "^9.5.0",
|
|
42
|
-
"plist": "^5.0.0"
|
|
37
|
+
"plist": "^5.0.0",
|
|
38
|
+
"@excitedjs/agent-runtime-claude-code": "0.7.0",
|
|
39
|
+
"@excitedjs/agent-runtime-codex": "0.6.0",
|
|
40
|
+
"@excitedjs/dreamux-types": "0.10.0",
|
|
41
|
+
"@excitedjs/dreamux-utils": "0.5.1",
|
|
42
|
+
"@excitedjs/feishu-channel": "6.2.0"
|
|
43
43
|
},
|
|
44
44
|
"devDependencies": {
|
|
45
45
|
"@modelcontextprotocol/client": "2.0.0",
|