@excitedjs/dreamux 0.26.0-beta.246 → 0.26.0-beta.249

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.246",
3
+ "version": "0.26.0-beta.249",
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.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",
29
+ "@excitedjs/agent-runtime-claude-code": "0.7.1-beta.249",
30
+ "@excitedjs/agent-runtime-codex": "0.6.1-beta.249",
31
+ "@excitedjs/dreamux-types": "0.11.0-beta.249",
32
+ "@excitedjs/dreamux-utils": "0.6.0-beta.249",
33
+ "@excitedjs/feishu-channel": "6.3.0-beta.249",
34
34
  "@modelcontextprotocol/server": "2.0.0",
35
35
  "acorn": "^8.16.0",
36
36
  "croner": "^10.0.1",
@@ -23,6 +23,18 @@ where the slug and digest are both derived from the configured channel `id`.
23
23
  `get_collaboration_space`, and `list_collaboration_spaces` read it.
24
24
  - A bind names an existing, open Team; Dreamux refuses a bind to a missing or
25
25
  closed Team and writes nothing. Dissolving a Team invalidates its routes.
26
+ - A chat carries either a whole-chat binding or a collaboration space, never
27
+ both, because a whole-chat binding answers for every topic under it and would
28
+ leave a space's new topics without a Team of their own. `bind_channel` refuses
29
+ a chat a space is registered on, and `bind_collaboration_space` refuses a chat
30
+ already bound as a whole; each names the conflict and writes nothing. Unbind
31
+ the one you do not want first. Binding a single topic is unaffected — that is
32
+ the row a space installs as it provisions.
33
+ - A document that already holds both still loads and the channel still starts;
34
+ the rule is enforced on writes, not at startup. Such a chat keeps routing the
35
+ way it has been — every topic under it answers to the whole-chat Team and new
36
+ topics get no Team of their own — until the whole-chat binding is released.
37
+ Nothing has to be rebuilt or hand-edited.
26
38
  - A document this Dreamux version cannot read fails loud at channel start,
27
39
  naming the file. Recreate the bindings through those tools rather than
28
40
  editing it.