@excitedjs/dreamux 0.27.0-beta.274 → 0.27.0-beta.276
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.27.0-beta.
|
|
3
|
+
"version": "0.27.0-beta.276",
|
|
4
4
|
"description": "Dreamux core host for multi-dispatcher agent orchestration through provider interfaces.",
|
|
5
5
|
"license": "MIT",
|
|
6
6
|
"repository": {
|
|
@@ -26,10 +26,10 @@
|
|
|
26
26
|
"CHANGELOG.json"
|
|
27
27
|
],
|
|
28
28
|
"dependencies": {
|
|
29
|
-
"@excitedjs/agent-runtime-claude-code": "0.8.1-beta.
|
|
30
|
-
"@excitedjs/agent-runtime-codex": "0.7.1-beta.
|
|
31
|
-
"@excitedjs/dreamux-utils": "0.7.0-beta.
|
|
32
|
-
"@excitedjs/feishu-channel": "6.
|
|
29
|
+
"@excitedjs/agent-runtime-claude-code": "0.8.1-beta.276",
|
|
30
|
+
"@excitedjs/agent-runtime-codex": "0.7.1-beta.276",
|
|
31
|
+
"@excitedjs/dreamux-utils": "0.7.0-beta.276",
|
|
32
|
+
"@excitedjs/feishu-channel": "6.4.0-beta.276",
|
|
33
33
|
"@modelcontextprotocol/server": "2.0.0",
|
|
34
34
|
"acorn": "^8.16.0",
|
|
35
35
|
"croner": "^10.0.1",
|
|
@@ -31,17 +31,28 @@ extensions close.
|
|
|
31
31
|
closed Team and writes nothing. Dissolving a Team invalidates its routes and
|
|
32
32
|
drops its document subscriptions, in the same commit.
|
|
33
33
|
- A chat carries either a whole-chat binding or a collaboration space, never
|
|
34
|
-
both, because a whole-chat binding
|
|
35
|
-
leave a space's new topics without a Team of
|
|
36
|
-
|
|
37
|
-
|
|
38
|
-
|
|
39
|
-
the
|
|
34
|
+
both, because a whole-chat binding claims every topic under it that has no
|
|
35
|
+
binding of its own and would leave a space's new topics without a Team of
|
|
36
|
+
their own. A topic's own exact binding always wins over the whole-chat one.
|
|
37
|
+
`bind_channel` refuses a chat a space is registered on, and
|
|
38
|
+
`bind_collaboration_space` refuses a chat already bound as a whole; each
|
|
39
|
+
names the conflict and writes nothing. Unbind the one you do not want first.
|
|
40
|
+
Binding a single topic is unaffected — that is the row a space installs as
|
|
41
|
+
it provisions.
|
|
40
42
|
- A document that already holds both still loads and the channel still starts;
|
|
41
43
|
the rule is enforced on writes, not at startup. Such a chat keeps routing the
|
|
42
|
-
way it has been — every topic under it
|
|
43
|
-
topics get no Team of their own — until the
|
|
44
|
-
Nothing has to be rebuilt or hand-edited.
|
|
44
|
+
way it has been — every topic under it that has no binding of its own answers
|
|
45
|
+
to the whole-chat Team, and new topics get no Team of their own — until the
|
|
46
|
+
whole-chat binding is released. Nothing has to be rebuilt or hand-edited.
|
|
47
|
+
- Saved topic bindings answer independently of the group's current message
|
|
48
|
+
format. An ordinary group can switch between thread and chat message format
|
|
49
|
+
at any time; that switch changes only whether an unbound topic may receive a
|
|
50
|
+
new Team automatically. In chat message format a registered space stays
|
|
51
|
+
registered, every saved topic binding — provisioned or hand-bound — keeps
|
|
52
|
+
reaching its own Team, and its unbound threads reach the Dispatcher instead
|
|
53
|
+
of being provisioned. Switching back to thread message format restores
|
|
54
|
+
automatic provisioning without re-registering the space. None of this is a
|
|
55
|
+
repair case: do not hand-edit the document over a format switch.
|
|
45
56
|
- A document subscription belongs to whoever created it — a Team, or the
|
|
46
57
|
Dispatcher Agent. Neither recipient can create or remove another's, and
|
|
47
58
|
`list_subscriptions` shows the caller's own rows only. Subscribing refuses a
|