@excitedjs/dreamux 0.26.0-beta.243 → 0.26.0-beta.246
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/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@excitedjs/dreamux",
|
|
3
|
-
"version": "0.26.0-beta.
|
|
3
|
+
"version": "0.26.0-beta.246",
|
|
4
4
|
"description": "Dreamux core host for multi-dispatcher agent orchestration through provider interfaces.",
|
|
5
5
|
"license": "MIT",
|
|
6
6
|
"repository": {
|
|
@@ -26,11 +26,11 @@
|
|
|
26
26
|
"CHANGELOG.json"
|
|
27
27
|
],
|
|
28
28
|
"dependencies": {
|
|
29
|
-
"@excitedjs/agent-runtime-claude-code": "0.7.1-beta.
|
|
30
|
-
"@excitedjs/agent-runtime-codex": "0.6.1-beta.
|
|
31
|
-
"@excitedjs/dreamux-types": "0.11.0-beta.
|
|
32
|
-
"@excitedjs/dreamux-utils": "0.6.0-beta.
|
|
33
|
-
"@excitedjs/feishu-channel": "6.3.0-beta.
|
|
29
|
+
"@excitedjs/agent-runtime-claude-code": "0.7.1-beta.246",
|
|
30
|
+
"@excitedjs/agent-runtime-codex": "0.6.1-beta.246",
|
|
31
|
+
"@excitedjs/dreamux-types": "0.11.0-beta.246",
|
|
32
|
+
"@excitedjs/dreamux-utils": "0.6.0-beta.246",
|
|
33
|
+
"@excitedjs/feishu-channel": "6.3.0-beta.246",
|
|
34
34
|
"@modelcontextprotocol/server": "2.0.0",
|
|
35
35
|
"acorn": "^8.16.0",
|
|
36
36
|
"croner": "^10.0.1",
|
|
@@ -26,3 +26,17 @@ where the slug and digest are both derived from the configured channel `id`.
|
|
|
26
26
|
- A document this Dreamux version cannot read fails loud at channel start,
|
|
27
27
|
naming the file. Recreate the bindings through those tools rather than
|
|
28
28
|
editing it.
|
|
29
|
+
|
|
30
|
+
## Collaboration-Space Identity At Team Creation
|
|
31
|
+
|
|
32
|
+
A Collaboration Space's configured `identity` stays exactly as the operator set
|
|
33
|
+
it in the routing document. When the Channel automatically provisions a Team for
|
|
34
|
+
a topic in that space, it creates the Team's leader with that identity plus the
|
|
35
|
+
bound conversation's reply address — the chat and the message that triggered the
|
|
36
|
+
creation — appended after it. An absent space identity creates the Team with the
|
|
37
|
+
reply address alone.
|
|
38
|
+
|
|
39
|
+
The appended text is generated per Team at creation time and belongs to the
|
|
40
|
+
Team's own server-owned identity. It is not written back to the space policy,
|
|
41
|
+
and an already-created Team is not revisited. To change the configured part, use
|
|
42
|
+
`bind_collaboration_space`; do not hand-edit either document.
|