dsh-team-rooms 1.0.0

package/ARCHITECTURE.md

@@ -0,0 +1,127 @@
+# Architecture
+
+`dsh-team-rooms` makes several independent DSH sessions one coordinated team. A **room** is `{members, message bus, task board, shared timeline}` persisted in the harness's own storage layer; every member is an ordinary session that keeps its own durable log. This document records the design decisions; the external contracts live in [README.md](./README.md).
+
+The package was extracted from `dsh-background-agents` 0.9.6, whose background-agent half is superseded by DSH's native continuable subagents. Everything room-shaped moved here verbatim; the identity strings that tie stored data to the old package are frozen (see *Frozen identity* below).
+
+## Frozen identity
+
+Four strings are byte-identical to what `dsh-background-agents` 0.9.6 wrote, because existing profiles and session logs carry them:
+
+| String | Declared in | Why it can never change |
+|---|---|---|
+| `team_rooms` | `src/room/domain.ts` (`defineDomain({ name })`) | The storage domain's on-disk identity. Renaming it orphans every existing room, member row, bus message, and task. |
+| `teamRoom` | `src/room/projection.ts` (`key`) and the `SessionProjectionMap` augmentation | The projection cache key and the client's `faceOf('teamRoom')` lookup. |
+| `team-room/fact` | `src/room/events.ts` (`TEAM_ROOM_FACT`) | The session-log event type. Older member logs contain records with this type. |
+| `team-rooms` | `src/client/index.ts` (`settings.section` registration `id`) | The settings-slot id the shell resolves. |
+
+The producer tag (`PLUGIN` in `src/vocabulary.ts`) deliberately also stays at the 0.9.6 literal `'dsh-background-agents'`: the room tools stamped `presentationMeta.plugin` with it, and nothing parses the value across packages, so keeping it leaves one logical producer under one string in stored logs. `tests/room-projection.spec.ts` pins the first three; the slot id is pinned by inspection and by the client registration itself.
+
+## The room hub (`src/room/hub.ts`)
+
+`RoomHub` is a Cordis `Service` (`roomHub`) constructed in `apply()` once the storage domain is available. It owns every room mutation and all delivery.
+
+- **Open**: `open()` calls `ctx.storageDomain.open(teamRoomsDomainSpec)` and caches the four tables (`rooms`, `bus`, `tasks`, `timeline`). The open is raced against `roomOpenTimeoutMs`; a stuck provider rejects with `RoomError('store-unavailable')` instead of parking `/room` forever without a `command/done`. A domain that arrives *after* the timeout is closed immediately (no orphaned handle), and the close effect is registered on the owning fiber so a normal unload closes the domain too.
+- **Gate**: every operation awaits `this.ready` first, so a failed open fails loudly at the first call rather than hanging or half-writing.
+
+## One write chain
+
+Every mutation — `createRoom`, `join`, `leave`, `postMessage`, `createTask`, `claimTask`, `assignTask`, `completeTask`, `deleteRoom` — is enqueued on a **single promise chain** (`this.tail`). The domain's single write chain is the ordering authority; running all read-modify-write sequences on one chain is what makes that authority observable:
+
+- bus `seq` and timeline `seq` are minted inside the chain, so they are strictly commit-ordered and gap-free;
+- two concurrent posters cannot interleave a read of `busNext` with a write of the same record;
+- `tests/room-tools.spec.ts` exercises this directly (eight concurrent `room_create_task` calls all land).
+
+Delivery is *outside* the mutation chain, on per-room and per-member chains, so a slow inbox never blocks a write.
+
+## Model-visible ⟺ recorded
+
+Every room message a member's model sees is an official inbox delivery, and therefore a durable `user/message` in that member's own session log:
+
+- a **live** member is woken with `agent.followup(...)`;
+- an **offline** member receives its backlog through `agent.inject(...)` when its session next starts (`catchUp`, mounted on `agent/session-start`).
+
+Both directions use `createUserMessage({ source: { kind: 'plugin', plugin: PLUGIN, form: 'notice' } })`, so a room delivery is attributable and replayable. This is the same discipline the background-agent half used for its progress lines, applied to a shared object.
+
+## Cursors: at-least-once, ordered delivery
+
+Each member slot carries two cursors in the durable room record (`src/room/schema.ts`):
+
+| Cursor | Meaning | Advanced when |
+|---|---|---|
+| `lastDeliveredSeq` | bus seq up to which this member's log received the model-visible message (`0` = none) | **after** the inbox delivery returns |
+| `lastFactSeq` | timeline seq up to which this member's log carries the log-only fact (`-1` = none) | **after** the fact append |
+
+Advancing only after the delivery lands is what makes delivery at-least-once: a crash between commit and delivery replays on catch-up instead of losing the message. Per-member chains serialize live delivery against catch-up so the two can never interleave and double-advance a cursor.
+
+## The shared timeline
+
+The room store is the cross-session authority; the timeline is mirrored into every member's own log as log-only `team-room/fact` events (`src/room/events.ts`), each carrying the canonical store `timelineSeq`. Members offline while a fact landed receive every missed fact in store order on their next activation, so the fold always reconstructs the shared view from the member's own log.
+
+The fact vocabulary is a closed discriminated union: `room-joined` (a full snapshot — room identity, roster, open tasks, retained timeline — so a cold member log needs no store read), `member-joined`, `member-left`, `message-posted` (with optional `toSessionId` for a directed delivery), `task-created`, `task-claimed`, `task-assigned`, `task-completed`.
+
+`FactAppender` (`src/facts.ts`) is the single append seam and carries the host gate:
+
+- hosts at `0.1.2-alpha.1` and later fail closed on the session event vocabulary, so `team-room/fact` is never appended there — each fact goes to the logger/panel fallback instead, and the projection degrades to an empty fold;
+- hosts whose `Session.append` predates the `ignorable` marker (every released rc line through `0.1.0-rc.8`, the `0.1.1-rc.2` line, and the `0.1.2-rc` line) are detected before the first append — peer-version pre-check, then a probe of the returned envelope — and appends are skipped with a one-time warning so the session log stays loadable everywhere;
+- `allowUnmarkedFacts: true` opts back into unmarked appends (deliberately dangerous).
+
+## The `teamRoom` projection (`src/room/projection.ts`)
+
+A pure fold over one member's own log: `apply(state, event)` consumes only events whose type is `team-room/fact` and returns the *same state object* for anything else, so the projection cache is a no-op for foreign events.
+
+- `room-joined` inserts a room view if the room is unknown; `member-joined` / `member-left` upsert the roster; the four task facts upsert a board row; `message-posted` appends a timeline entry classified as broadcast or directed.
+- Timeline entries are deduped by `seq` and kept sorted, bounded at `TIMELINE_FOLD_BOUND = 1000`.
+- The fold state keeps **every** done task; the **wire** value (`wire.view`) applies `capDoneTasks` (`DONE_TASK_FOLD_BOUND = 100`) so the browser never receives an unbounded board. `stateVersion: 1` matches the persisted cache written by 0.9.6.
+
+The value is the per-session reconstructed copy; the store remains the authority. That split is why the settings page renders instantly on reopen without a store read, and why a lost projection cache costs only a refold.
+
+## The `/room` command family and the eight tools
+
+- `src/room/commands.ts` registers `name: 'room'` with the subcommands `create|join|leave|list|send|tasks|task add|assign|claim|done|delete`. It is mounted through `ctx.effect(...)`, so the command disappears with the fiber.
+- `src/room/tools.ts` registers the eight model-facing tools: `room_list_rooms`, `room_post`, `room_read`, `room_list_tasks`, `room_create_task`, `room_claim_task`, `room_transfer_task`, `room_complete_task`.
+- **Membership is the authorization boundary**: every tool resolves the calling session's member slot first and rejects a non-member with a stable error instead of a partial write.
+- **`room_transfer_task` is approval-gated**: it asks the optional `approval` service, and a missing service, a missing answerer, a rejection, or an abort all collapse to the same fail-closed `approval-unavailable` / `approval-denied` `RoomError`. Nothing changes on a refusal.
+
+## The client half
+
+`src/client/index.ts` registers exactly one surface: the `settings.section` entry with the frozen id `team-rooms`, order 30, locale namespace `teamRooms`.
+
+- `TeamRoomsController` is a `useSyncExternalStore`-compatible snapshot: it subscribes to the session list, re-binds `sessions.binding(current).session.projections.faceOf('teamRoom')` whenever the current session changes, and runs the snapshot through the pure presenter.
+- `src/client/room-presenter.ts` turns the opaque projection cell into display rows: it validates with the shared zod guard (`isTeamRoomView`), sorts members by join time, ranks tasks `todo → in-progress → done` then by id, and serves the 100 newest timeline entries. It performs no I/O, so it is testable without a DOM.
+- **Every write goes through the host**: the injected action map (`create`, `join`, `leave`, `post`, `addTask`, `claimTask`, `completeTask`, `assignTask`) builds a `/room …` line and executes it with `remote.commands.execute(sessionId, line, [])`. There is no private RPC and no client-side state mutation, so each click keeps the durable `command/run` → `command/done` lifecycle and the host's ordering guarantees.
+
+The bundle is a single CJS face wrapped in `window.__ModuleLoader__.load({ id: 'dsh-team-rooms', factory })`, served from `/plugins/dsh-team-rooms/client.js`. `PLUGIN_ID` in `tsdown.config.ts` is the one string that must match the npm package name, the cordis row name, the stamped bundle id, the logger channel, and the `data-plugin`/`data-plugin-css` CSS tags.
+
+## Data flow
+
+```
+/room …  ──▶ command handler ─┐
+room_*   ──▶ tool execution  ─┤
+                              ▼
+                     RoomHub write chain  ──▶ team_rooms domain (rooms / bus / tasks / timeline)
+                              │                         (single write chain = ordering authority)
+                              ├─▶ team-room/fact  (ignorable, log-only) ──▶ each member's session log
+                              │                                              └─▶ teamRoom projection ──▶ settings page
+                              └─▶ agent.followup / agent.inject ──▶ member session log (user/message)
+                                                                     (model-visible ⟺ recorded)
+
+member session starts ──▶ hub.catchUp(sessionId) ──▶ replay missed bus messages + facts, in store order
+```
+
+## Cross-ecosystem inbound (P2)
+
+`src/inbound.ts` adds a minimal newline-delimited JSON-RPC 2.0 bridge over stdio so external agent runtimes (OpenAI Agents SDK, CrewAI) can publish into a team room. This is a direct-connect minimal set — full ACP wire compatibility waits for the upstream seam. It moved here with the room half: every payload type carries a `roomId`, and its only consumer is `inboundRoomSink` in `src/index.ts`.
+
+- **Wire**: one JSON notification per line on the child's stdout. `method` is the event name (`agent_started` | `agent_message` | `agent_finished`); `params` carries `name`, `room`, `traceId`, optional `status`, `message`, and `usage`. The zod `inboundParamsSchema` is `.strict()` — unknown fields fail closed.
+- **Seam**: `InboundCoordinator.registerInboundAdapter(adapter, sink)` returns a disposer; `StdioJsonRpcInbound` spawns `inbound.command`, parses lines, maps them to normalized `InboundEvent`s, and emits into the sink. Invalid lines are dropped and answered with a JSON-RPC error on the child's stdin.
+- **Mapping**: `deliveriesFor` translates each event onto the room's existing surfaces — `agent_started` → task-board card, `agent_message` → bus post, `agent_finished` → card close + outcome post. The `apply()` bridge (`inboundRoomSink`) executes those deliveries against the `RoomHub`; external runtimes are not DSH sessions, so the room owner's member session is the sender and a room with no owner drops the event.
+- **Lifecycle & config**: `inbound.enabled` (default `false`, fail-closed) and `inbound.command` gate the bridge, which mounts only where the storage domain (and thus the room hub) exists. Start/stop ride the fiber's effect disposer; an unspawnable command degrades to a logged warning with the bridge dormant.
+
+## Boundaries
+
+- **No subagents.** The room half never spawns, messages, or interrupts a child agent: the package declares no `subagent:*` permission, declares no subagent dependency, and its `inject` list carries no `subagents` entry. A member is a session the user (or another seam) already has.
+- **No scheduling.** Rooms own the shared object, not "when" work runs.
+- **No cross-machine membership.** Every member is a process-local session of this deployment.
+- **No currency accounting.** That lived in the background-agent half; room surfaces report structure, not spend.
+- **Storage is the only durability dependency.** Without `@deepseek-ai/dsh-storage-domain` the `/room` command and the `room_*` tools stay dormant while the rest of the plugin loads cleanly.

package/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2026 dsh-background-agents contributors
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/README-es.md

@@ -0,0 +1,248 @@
+<div align="center">
+
+# 🏠 dsh-team-rooms
+- **Canal de la tienda 1024**: ejecuta `npm i -g dsh1024` una vez y luego `dsh1024 plugin --profile web add dsh-team-rooms` (cuenta para el ranking de instalaciones de [deepseek1024.com](https://deepseek1024.com)).
+
+**Salas de equipo multiagente persistentes y entre sesiones para DeepSeek Harness — miembros, un bus de mensajes, un tablero de tareas compartido y una línea de tiempo compartida que sobreviven a los reinicios.**
+
+*Cada miembro es una sesión DSH independiente; la sala es el objeto duradero compartido entre ellas.*
+
+[![License](https://img.shields.io/badge/license-Apache%202.0-blue.svg)](LICENSE)
+[![DSH plugin](https://img.shields.io/badge/dsh--plugin-✅-green)](https://github.com/topics/dsh-plugin)
+[![Node](https://img.shields.io/badge/node-%5E22.19%20%7C%7C%20%3E%3D24-brightgreen.svg)](#)
+
+[English](README.md) · [简体中文](README-zh.md) · [Español](README-es.md) · [Português](README-pt.md) · [हिन्दी](README-hi.md)
+
+</div>
+
+---
+
+> **Extraído de [`dsh-background-agents`](https://github.com/PerryLink/dsh-background-agents) 0.9.6.** La mitad de agentes en segundo plano de ese plugin (`background_agent` y las cinco herramientas `bg_*`) queda superada por los subagentes continuables nativos de DSH; la mitad de salas de equipo no tenía equivalente nativo y continúa aquí como paquete propio. Los dominios de almacenamiento, los registros de sesión y los ajustes escritos por 0.9.6 siguen funcionando sin cambios — ver *Compatibilidad*.
+
+## Compatibilidad
+
+El host `0.1.2-alpha.2` y posteriores fallan cerrado ante el vocabulario de eventos de sesión, así que este plugin ya no escribe allí sus eventos de hecho solo-registro (`team-room/fact`): los hechos van al canal de logger/panel y la proyección `teamRoom` se degrada a un pliegue vacío. Las líneas rc anteriores (hasta `0.1.1-rc.2`) mantienen la disciplina del marcador `ignorable`. La mitad cliente usa los paquetes cliente actuales (`dsh-api-session-controller`, `dsh-client-ui-slots`, `dsh-client-ui-settings`, `dsh-client-locale`, `dsh-client-web`).
+
+**La compatibilidad de datos con `dsh-background-agents` 0.9.6 es una regla dura.** Estas cadenas son idénticas byte a byte a las de 0.9.6 y nunca deben renombrarse: el dominio de almacenamiento `team_rooms`, la clave de proyección `teamRoom`, el tipo de evento de sesión `team-room/fact` y el id de ranura de ajustes `team-rooms`. Por eso un perfil existente conserva sus salas, los registros de sus miembros y su página de ajustes al cambiar el plugin.
+
+| Superficie | Estado |
+|---|---|
+| Harness | DeepSeek Harness `dsh-v0.1.5-rc.2` (tag de GitHub, verificado 2026-09-11; dev y runtime fijan `0.1.5-rc.2`, peers `>=0.1.2-rc.1 <0.2.0 \|\| >=0.1.5-alpha.1 <0.2.0`) |
+| Node | `^22.19.0 \|\| >=24.0.0` |
+| Plataformas | Todas (herramientas de host; la página de ajustes necesita la mitad cliente Web y la capacidad de dominio de almacenamiento) |
+| Modelo | Cualquiera (las salas no llevan ruta de modelo — los miembros son sesiones ordinarias) |
+
+## Qué obtienes
+
+`dsh-team-rooms` convierte varias sesiones independientes en un equipo coordinado:
+
+1. **La familia de comandos `/room`** — `create`, `join`, `leave`, `list`, `send`, `tasks`, `task add|assign|claim|done|delete`. Las salas tienen nombre, dueño y se direccionan con un id estable que puedes pegar en otra sesión.
+2. **Ocho herramientas `room_*`** — `room_list_rooms`, `room_post`, `room_read`, `room_list_tasks`, `room_create_task`, `room_claim_task`, `room_transfer_task`, `room_complete_task`. El modelo trabaja el tablero compartido y el bus desde su propia sesión; `room_transfer_task` pide aprobación antes de un traspaso entre miembros.
+3. **Un almacén de salas duradero** — miembros, el bus de mensajes (dirigido o difundido), el tablero de tareas y la línea de tiempo viven en el dominio de almacenamiento `team_rooms` (backend SQLite o JSONL — lo elige el despliegue; el plugin no añade ningún servicio propio) y se recuperan tras reiniciar DSH.
+4. **Una página de ajustes Web** — la sección Team Rooms muestra el estado de los miembros, el tablero de tareas y la línea de tiempo de cada sala a la que pertenece la sesión actual, leídos de la proyección de sesión `teamRoom` y escritos de vuelta por el comando `/room` del host.
+
+## Inicio rápido
+
+```sh
+# 1. instala el bundle en tu perfil
+dsh plugin --profile web add "github:PerryLink/dsh-team-rooms#main"
+
+# o desde npm (versiones publicadas)
+dsh plugin --profile web add dsh-team-rooms
+
+# 2. reinicia y verifica la fila
+dsh --profile web --dump-config | grep -A4 'id: team-rooms'
+```
+
+El parche del bundle incluye la fila del plugin; no hay ninguna clave de Config obligatoria. El repositorio confirma su salida de compilación (`lib/`), así que las instalaciones por git no necesitan compilar. Las salas se montan donde se compone el dominio de almacenamiento (`@deepseek-ai/dsh-storage-domain`, presente en todo perfil `@deepseek-ai/dsh-base`); sin él, el comando `/room` y las herramientas `room_*` quedan inactivos mientras todo lo demás sigue cargando.
+
+Después, dentro de cualquier sesión:
+
+```
+/room create release-prep
+/room send <roomId> kickoff: I own the changelog, who takes the docs?
+/room task add <roomId> draft the migration note
+/room task claim <roomId> <taskId>
+```
+
+Pega el id de sala impreso en otra sesión y ejecuta `/room join <roomId>`: esa sesión pasa a ser miembro, recibe las entregas de la sala como mensajes normales y ve el mismo tablero.
+
+## Instalación y desinstalación
+
+- **canal git** (último `main`): `dsh plugin --profile web add "github:PerryLink/dsh-team-rooms#main"` — `lib/` confirmado, sin pasos `prepare` ni `allowBuilds`.
+- **canal npm** (versiones publicadas): `dsh plugin --profile web add dsh-team-rooms`.
+- **canal tarball**: `pnpm pack` en este repositorio y luego `dsh plugin --profile web add ./dsh-team-rooms-<version>.tgz`.
+- **desinstalar**: `dsh plugin --profile web remove dsh-team-rooms` (o quita la fila del parche del perfil). Tus salas permanecen en el dominio de almacenamiento `team_rooms` y vuelven si reinstalas.
+- ⚠️ **No montes este paquete y `dsh-background-agents` a la vez.** Durante la ventana de deprecación ambos están publicados, y los dos registran las mismas ocho herramientas `room_*`, el mismo id de slot `settings.section` (`team-rooms`) y el mismo dominio de almacenamiento `team_rooms`, así que las dos mitades de salas chocan. Si ya usas `dsh-background-agents`, quítalo primero (`dsh plugin --profile web remove dsh-background-agents`). Tus salas sobreviven en cualquier caso: viven en el dominio de almacenamiento, no en el plugin.
+
+## Configuración
+
+Cada ajuste es un campo `Config` validado por Schemastery — cámbialo en cordis.yml, nunca en el código. Ninguno es obligatorio.
+
+| Clave | Predeterminado | Significado |
+|---|---|---|
+| `maxRooms` | `16` | Tope de salas de equipo en todo el perfil |
+| `maxMembersPerRoom` | `8` | Tope de miembros por sala (`>= 2`) |
+| `maxRoomsPerMember` | `4` | Tope de salas a las que puede unirse una sesión miembro |
+| `busRetention` | `200` | Mensajes del bus conservados por sala |
+| `timelineRetention` | `500` | Eventos de línea de tiempo conservados por sala |
+| `taskRetention` | `50` | Tareas completadas conservadas por sala |
+| `maxMessageChars` | `4000` | Tope del texto de un mensaje de sala (por encima se rechaza, nunca se trunca) |
+| `injectRoomBrief` | `true` | Inyectar el breve resumen de la sala en las sesiones miembro (al unirse y al reanudar) |
+| `roomOpenTimeoutMs` | `15000` | Cuánto puede tardar la apertura del dominio de almacenamiento `team_rooms` antes de que toda operación de sala falle en voz alta (`store-unavailable`) en lugar de colgarse |
+| `allowUnmarkedFacts` | `false` | Forzar los eventos `team-room/fact` solo-registro en hosts que descartan el marcador `ignorable` (peligroso: los hechos sin marcar vuelven las sesiones irrecuperables en otros hosts); por defecto se detecta y se omite |
+| `inbound.enabled` | `false` | Habilita el puente de entrada stdio JSON-RPC para runtimes de agentes externos (OpenAI Agents SDK / CrewAI). Deshabilitado por defecto (fail-closed). |
+| `inbound.command` | *(ninguno)* | Comando de lanzamiento del runtime externo; cuando está habilitado y presente, el plugin lo lanza y escucha notificaciones JSON-RPC delimitadas por saltos de línea. Ausente/no lanzable = el puente queda inactivo (registrado). |
+
+## Herramientas y superficies
+
+| Superficie | Tipo | Notas |
+|---|---|---|
+| `/room` | command | `create\|join\|leave\|list\|send\|tasks\|task add\|assign\|claim\|done\|delete` |
+| `room_list_rooms` | tool | Cada sala a la que pertenece esta sesión: ids, nombres, plantillas, conteos de tareas |
+| `room_post` | tool | Publicar en el bus (difundido, o dirigido con `to`) |
+| `room_read` | tool | Leer el historial del bus de una sala, desde un cursor de seq |
+| `room_list_tasks` | tool | El tablero de tareas compartido de una sala |
+| `room_create_task` | tool | Añadir una fila al tablero (opcionalmente asignada) |
+| `room_claim_task` | tool | Reclamar una fila para esta sesión (asignado + en progreso) |
+| `room_transfer_task` | tool | Pasar una fila a otro miembro — **con aprobación**, falla cerrado |
+| `room_complete_task` | tool | Marcar una fila como `done` |
+| proyección `teamRoom` | session projection | La vista de sala plegada desde los eventos `team-room/fact` en el registro propio de este miembro |
+| página de ajustes Web | client | Estado de miembros, tablero de tareas, línea de tiempo y acciones de sala; id de ranura `team-rooms` |
+
+Son **ocho** herramientas `room_*`, todas registradas cuando el dominio de almacenamiento está compuesto.
+
+## Cómo funciona — y por qué sobrevive a los reinicios
+
+El almacén de salas es la autoridad entre sesiones; la proyección de sesión es la copia reconstruida de cada miembro. Dos escrituras ocurren a la vez y se mantienen consistentes:
+
+- **Cada mutación de sala** (create, join, leave, post, transiciones de tareas) se encola en UNA cadena de escritura del hub — la cadena única del dominio `team_rooms` es la autoridad de orden, así que dos publicadores concurrentes nunca pueden intercalar una lectura-modificación-escritura y los seq del bus se acuñan estrictamente en orden de commit.
+- **Visible para el modelo ⟺ registrado**: un mensaje de sala entregado es una entrega oficial a la bandeja (`agent.followup` despierta a un miembro en vivo; `agent.inject` entrega su acumulado a un miembro desconectado en el siguiente arranque), de modo que queda como un `user/message` duradero en el registro propio de ese miembro.
+- **La línea de tiempo compartida** se refleja en el registro de cada miembro como eventos `team-room/fact` solo-registro que llevan el `timelineSeq` canónico del almacén; la proyección `teamRoom` pliega el registro propio de cada miembro, así que la vista se reconstruye en cada reapertura sin leer el almacén.
+- **La entrega es al-menos-una-vez y ordenada**: los cursores por miembro (`lastDeliveredSeq`, `lastFactSeq`) avanzan solo cuando una entrega aterriza, así que una caída entre commit y entrega reentrega en la recuperación en lugar de perder el mensaje.
+
+Los hosts cuyo `Session.append` precede al marcador `ignorable` (todas las líneas rc publicadas hasta `0.1.0-rc.8`, la línea `0.1.1-rc.2` y la línea `0.1.2-rc`, que conserva el campo del sobre solo para compatibilidad de lectura de registros ya guardados) se detectan antes de la primera escritura (precomprobación de versión del peer y luego una sonda del sobre devuelto) y las escrituras de hechos se omiten con un aviso único: el almacén duradero, las superficies de API y las entregas visibles para el modelo siguen funcionando, y `teamRoom` se degrada a un pliegue vacío. `allowUnmarkedFacts: true` reactiva la escritura — deliberadamente peligroso.
+
+## No es este plugin
+
+| Proyecto | Qué hace | La frontera |
+|---|---|---|
+| [titanwings/dsh-automation](https://github.com/titanwings/dsh-automation) | Tareas de codificación programadas en sesiones de agente nuevas | Posee **cuándo** se ejecutan las tareas (planificación). Este plugin posee el **objeto compartido** sobre el que trabajan varias sesiones — sin costura de planificador, sin cron. |
+| [YYTbit/dsh-plugin-agent-dashboard](https://github.com/YYTbit/dsh-plugin-agent-dashboard) | Skill de panel multiagente | Orientado a mostrar y mayormente de lectura. Las salas de este plugin son **estado de coordinación escribible**: un bus, un tablero y traspasos con aprobación, persistidos en el almacenamiento propio del harness. |
+| `dsh-background-agents` | Agentes en segundo plano y (antes) salas de equipo | La mitad `bg_*` de ese paquete queda superada por los subagentes continuables nativos de DSH; su mitad de salas es este paquete. No montes las dos mitades de salas a la vez. |
+
+## Permisos y datos
+
+- **Permisos**: el manifiesto del workshop declara `session:append` y `tools:register`. Las salas nunca lanzan un subagente, así que el plugin no pide ningún permiso `subagent:*` ni declara dependencia de subagentes.
+- **Datos**: las salas viven en el dominio de almacenamiento `team_rooms` (SQLite o JSONL — cero servicios extra). Sin base de datos aparte, sin red.
+- **Registro de sesión**: los eventos `team-room/fact` se escriben con el marcador `ignorable: true` del sobre en los hosts que lo respetan (los hosts anteriores al marcador se detectan y se omiten las escrituras — ver `allowUnmarkedFacts`); las entregas de sala visibles para el modelo son registros `user/message` reales.
+
+## Límites de seguridad
+
+- **Traspasos con aprobación.** `room_transfer_task` pasa por la costura oficial de aprobación y falla cerrado cuando no hay servicio de aprobación compuesto o nadie concede: nada cambia ante un rechazo.
+- **Visible para el modelo ⟺ registrado.** Cada mensaje de sala entregado es un `user/message` duradero en el registro propio del miembro; la línea de tiempo compartida se refleja como eventos `team-room/fact` solo-registro. Un mensaje de sala nunca puede llegar a un modelo sin quedar registrado.
+- **La pertenencia es la frontera de autorización.** Cada herramienta `room_*` autoriza contra la pertenencia de la propia sesión llamante; quien no es miembro recibe un rechazo estable, no una escritura parcial.
+- **La retención está acotada.** Las ventanas del bus, la línea de tiempo y las tareas hechas se aplican en cada escritura, así que una sala longeva no puede crecer sin límite.
+- **Sin planificación ni miembros entre máquinas.** Un miembro es una sesión local al proceso de este despliegue.
+
+## Entrada entre ecosistemas (P2)
+
+Los runtimes de agentes externos — OpenAI Agents SDK, CrewAI y similares — pueden publicar en una sala de equipo mediante un **puente stdio JSON-RPC 2.0 delimitado por saltos de línea**. Es un conjunto mínimo de conexión directa JSON-RPC, no el protocolo oficial de cable ACP: la compatibilidad ACP completa espera a la costura upstream.
+
+Actívalo con dos campos de Config y apunta `inbound.command` a un lanzador que emita una notificación JSON por línea en stdout:
+
+```yaml
+# cordis.yml (fila del plugin)
+inbound:
+  enabled: true
+  command: "python external_runtime.py --room <room-id>"
+```
+
+El runtime emite tres tipos de notificación; `method` es el nombre del evento y `params.name` es el nombre visible del agente externo:
+
+```json
+{"jsonrpc":"2.0","method":"agent_started","params":{"name":"researcher","room":"<room-id>","traceId":"t-1"}}
+{"jsonrpc":"2.0","method":"agent_message","params":{"name":"researcher","room":"<room-id>","traceId":"t-1","message":"found the failing test"}}
+{"jsonrpc":"2.0","method":"agent_finished","params":{"name":"researcher","room":"<room-id>","traceId":"t-1","status":"ok","usage":{"inputTokens":100,"outputTokens":40}}}
+```
+
+Cada una se mapea a las superficies existentes de la sala: `agent_started` abre una tarjeta en el tablero, `agent_message` publica en el bus de mensajes y `agent_finished` cierra la tarjeta y publica el resultado. Los mensajes inválidos fallan cerrado — se descartan y se escribe un error JSON-RPC de vuelta. Los runtimes externos no son sesiones DSH, así que la sesión miembro dueña de la sala actúa como remitente; una sala sin miembro dueño descarta el evento. El arranque y la parada los posee la fibra del plugin mediante un disposer; un `inbound.command` no lanzable se degrada a un aviso registrado (el puente queda inactivo, nada más se ve afectado).
+
+## Limitaciones conocidas
+
+- Las salas requieren que el dominio de almacenamiento esté compuesto; sin `@deepseek-ai/dsh-storage-domain`, el comando `/room` y las herramientas `room_*` quedan deshabilitados.
+- Una sala necesita al menos dos miembros para ser interesante, y la plantilla está acotada por `maxMembersPerRoom`; la pertenencia es por sesión, no por usuario.
+- No hay pertenencia entre máquinas: cada miembro es una sesión local al proceso de este despliegue.
+- `room_transfer_task` necesita un respondedor de aprobación. Sin él falla cerrado por diseño, así que los perfiles automatizados que quieran traspasos deben componer un servicio de aprobación.
+- La contabilidad de coste/uso queda fuera de alcance aquí (eso vivía en la mitad de agentes en segundo plano); las superficies de sala informan estructura, no gasto.
+
+## Desarrollo
+
+```sh
+pnpm install        # solo herramientas; los paquetes del harness se resuelven contra un checkout hermano
+pnpm run typecheck  # TS estricto, programas node + cliente
+pnpm test           # vitest: pruebas unitarias, de hub de salas, de proyección y de panel jsdom
+pnpm run build      # lib/index.js (mitad node) + lib/client.js (bundle cliente web)
+pnpm run verify:artifacts && pnpm run check:readmes
+pnpm run gen-aliases  # vuelve a mapear las rutas del harness si el checkout se mueve
+```
+
+`pnpm run pack:smoke` compila, empaqueta y (con `DSH_HARNESS_ROOT` definido) instala el tarball en un perfil desechable para comprobar la fila compuesta.
+
+## Temas
+
+`dsh`, `dsh-plugin`, `deepseek-harness`, `team-rooms`, `multi-agent`, `message-bus`, `task-board`, `collaboration`, `cross-session`
+
+## Contribuidores
+
+- [@PerryLink](https://github.com/PerryLink) — creador y mantenedor: el hub de salas de equipo y su cadena de escritura, los cursores de entrega, la proyección `teamRoom`, la página de ajustes Web, documentación, CI/CD y publicaciones.
+
+## Familia de plugins DSH de PerryLink
+
+Este proyecto es uno de los [36 plugins de DeepSeek Harness](https://github.com/PerryLink) mantenidos por [PerryLink](https://github.com/PerryLink). Si este te ayuda, los otros probablemente también:
+
+| Plugin | Una línea |
+|---|---|
+| **[dsh-auto-review](https://github.com/PerryLink/dsh-auto-review)** | Auto-revisión por segundo modelo en la cadena de aprobación, fail-closed por defecto | |
+| **[dsh-budget](https://github.com/PerryLink/dsh-budget)** | Gobernanza de costes para DeepSeek Harness: presupuestos, carbono y latencia en un panel | |
+| **[dsh-checkpoint-rewind](https://github.com/PerryLink/dsh-checkpoint-rewind)** | Equivalente a /rewind de Claude Code: instantáneas, bifurcaciones de sesión, restauración en un paso | |
+| **[dsh-claude-move](https://github.com/PerryLink/dsh-claude-move)** | Migra sesiones, memoria, skills y CLAUDE.md de Claude Code a DSH | |
+| **[dsh-click](https://github.com/PerryLink/dsh-click)** | Control nativo de escritorio multiplataforma para DeepSeek Harness — Windows primero | |
+| **[dsh-composer-history](https://github.com/PerryLink/dsh-composer-history)** | Historial de entrada estilo terminal para el compositor web: flechas, búsqueda Ctrl+R | |
+| **[dsh-data-quality](https://github.com/PerryLink/dsh-data-quality)** | Comprobaciones de calidad de datasets y cruce de citas | |
+| **[dsh-defend](https://github.com/PerryLink/dsh-defend)** | Defensa contra inyección de prompts, jailbreak y fuga de secretos para DeepSeek Harness | |
+| **[dsh-doublecheck](https://github.com/PerryLink/dsh-doublecheck)** | Guardia de disciplina de ingeniería: interrogatorio de requisitos, puertas de test, revisión adversaria | |
+| **[dsh-draw](https://github.com/PerryLink/dsh-draw)** | Enrutado unificado de generación de imágenes estáticas para DeepSeek Harness | |
+| **[dsh-fast](https://github.com/PerryLink/dsh-fast)** | Diagnóstico de rendimiento de solo lectura para DeepSeek Harness | |
+| **[dsh-fund-research](https://github.com/PerryLink/dsh-fund-research)** | Informes de investigación deterministas para fondos mutuos públicos chinos | |
+| **[dsh-github](https://github.com/PerryLink/dsh-github)** | Integración de PR/issues de GitHub para DSH, cada escritura con aprobación | |
+| **[dsh-industry-research](https://github.com/PerryLink/dsh-industry-research)** | Orquestación de investigación sectorial que sella sus entregables mediante `ctx.researchReport.assemble` | |
+| **[dsh-library](https://github.com/PerryLink/dsh-library)** | Base de conocimiento de documentos locales para DeepSeek Harness | |
+| **[dsh-local-ai](https://github.com/PerryLink/dsh-local-ai)** | Integración de modelos locales (Ollama) para DeepSeek Harness | |
+| **[dsh-lsp-actions](https://github.com/PerryLink/dsh-lsp-actions)** | Diagnósticos, formato, completado, acciones de código y renombrado LSP sobre servidores de lenguaje | |
+| **[dsh-mask](https://github.com/PerryLink/dsh-mask)** | Middleware de enmascarado de PII: anonimiza en la frontera del modelo, restaura en la capa de presentación | |
+| **[dsh-mcp-panel](https://github.com/PerryLink/dsh-mcp-panel)** | Panel de runtime MCP de solo lectura: comando /mcp + pestaña de ajustes con estado, herramientas y errores | |
+| **[dsh-memento](https://github.com/PerryLink/dsh-memento)** | Memoria entre sesiones con aprobación: costura ctx.memory + SQLite + herramienta memory | |
+| **[dsh-observe](https://github.com/PerryLink/dsh-observe)** | Exportador de observabilidad OpenTelemetry y Langfuse para DeepSeek Harness | |
+| **[dsh-output-styles](https://github.com/PerryLink/dsh-output-styles)** | Cambio de estilo en runtime equivalente a outputStyles de Claude Code | |
+| **[dsh-permission-rules](https://github.com/PerryLink/dsh-permission-rules)** | Reglas declarativas de permiso allow/deny/ask estilo Claude Code con auditoría | |
+| **[dsh-personal-directive](https://github.com/PerryLink/dsh-personal-directive)** | Inyector de directivas personales con interruptor en la barra superior (edición framework) | |
+| **[dsh-plugin-guide](https://github.com/PerryLink/dsh-plugin-guide)** | Base de conocimiento de desarrollo de plugins como skill bajo demanda | |
+| **[dsh-reach](https://github.com/PerryLink/dsh-reach)** | Puente multicanal de aprobaciones/preguntas: WeChat/Telegram/Feishu, consola de sesión | |
+| **[dsh-research-report](https://github.com/PerryLink/dsh-research-report)** | Motor de informes de investigación verificables: libro de evidencias direccionado por contenido y versiones selladas | |
+| **[dsh-score](https://github.com/PerryLink/dsh-score)** | Puntuación de calidad multidimensional para plugins de DeepSeek Harness | |
+| **[dsh-session-pin](https://github.com/PerryLink/dsh-session-pin)** | Fija sesiones en la barra lateral Web con orden duradero | |
+| **[dsh-session-sync](https://github.com/PerryLink/dsh-session-sync)** | Sincronización de sesiones entre dispositivos para DeepSeek Harness — un espejo git dedicado de tu almacén de sesiones | |
+| **[dsh-skill-pack-security](https://github.com/PerryLink/dsh-skill-pack-security)** | Paquete de skills de auditoría de seguridad: escaneo de secretos, revisión de dependencias y cadena de suministro | |
+| **[dsh-talk](https://github.com/PerryLink/dsh-talk)** | Bucle de sesión por voz para DeepSeek Harness: háblale y escúchalo responder | |
+| **[dsh-test-drive](https://github.com/PerryLink/dsh-test-drive)** | Pruebas aisladas de instalación y smoke para plugins de DeepSeek Harness | |
+| **[dsh-ticktick](https://github.com/PerryLink/dsh-ticktick)** | Puente de tareas TickTick/Dida365: panel en la cabecera de sesión + 11 herramientas | |
+| **[dsh-translate](https://github.com/PerryLink/dsh-translate)** | Traducción de parámetros de proveedor y reparación determinista de JSON para DeepSeek Harness | |
+
+### Instalar desde el mercado de DSH Desktop
+
+Todos los plugins de PerryLink se pueden explorar en el mercado integrado de DSH Desktop: **Market → Sources → add source → pega** `https://perrylink-dsh-catalog.perrylink.workers.dev/catalog-source.json` **→ selecciónalo**. La instalación sigue pasando por la verificación de identidad npm del mercado y tu confirmación.
+
+## Licencia
+
+[Apache License 2.0](LICENSE) © 2026 dsh-team-rooms contributors