@jcy2387/dsh-suite 0.2.0-rc.2 → 0.2.0-rc.2.1

package/README.md

@@ -8,7 +8,7 @@ A pure [DeepSeek Harness](https://github.com/deepseek-ai/deepseek-harness) (DSH)
 ## What it installs
 
 - [`@jcy2387/dsh-codex-provider`](../codex-provider/README.md) — the Codex provider: ChatGPT OAuth, usage dashboard, proxy-aware networking, native Settings page.
-- [`@jcy2387/dsh-conversation-ui`](../conversation-ui/README.en.md) — the Codex-style conversation UI: event stream, turn folding, streaming reveal, deliverables.
+- [`@jcy2387/dsh-conversation-ui`](../conversation-ui/README.en.md) — native DSH assistant reveal, auto-expanded thinking, and deliverables.
 
 Both plugins remain independently configurable; the suite only wires them into the profile. To install or configure just one of them, install its package directly instead — but avoid keeping the suite and a standalone copy of the same plugin in one profile at the same time (see below).
 
@@ -23,23 +23,23 @@ After installing, follow each plugin's quick start: connect a ChatGPT account in
 
 ## How the bundle works
 
-The package's `dsh.bundle.patch` metadata points at `cordis.patch.yml`, which inserts both plugins inside a nested loader group:
+The package's `dsh.bundle.patch` metadata points at `cordis.patch.yml`, which inserts the two plugin rows directly:
 
 ```yaml
 - insert:
-    - id: suite-plugins
-      name: cordis:group
-      group: true
-      config:
-        - id: codex-provider
-          name: '@jcy2387/dsh-codex-provider'
-        - id: conversation-ui
-          name: '@jcy2387/dsh-conversation-ui'
+    - id: codex-provider
+      name: '@jcy2387/dsh-codex-provider'
+    - id: conversation-ui
+      name: '@jcy2387/dsh-conversation-ui'
 ```
 
-The nested group keeps the suite **crash-safe against coexistence**: the loader rejects two rows with the same id inside one group (the original `duplicate loader entry id` boot failure), but rows at different levels are allowed. If a profile also contains one of the plugins installed directly, the direct row and the suite's child row map onto one shared loader entry and the plugin runs exactly once.
+The plugin page lists these two components. Their ids and individual configuration stay the same as a standalone installation.
 
-**Coexistence caveat:** while both rows are present, removing either one (the suite or the direct install) from the bundle list of a *running* dsh process disposes that shared entry, and the plugin silently stops working until the next restart. The safest policy is to install either the suite **or** the standalone packages in a given profile, and to restart dsh after any bundle-list change.
+Install either the suite or the standalone bundles in a profile. Combining both declares duplicate loader entry ids and prevents startup. Restart dsh after changing the bundle list.
+
+### Upgrading from the grouped suite
+
+The `suite-plugins` group has been removed. Remove overlays targeting that group and configure `codex-provider` or `conversation-ui` directly. Existing plugin preferences, credentials, and session data remain unchanged.
 
 ## Development
 

package/cordis.patch.yml

@@ -1,30 +1,7 @@
-# Install both independent plugins as one Suite bundle.
-#
-# The children live inside a nested loader group so their rows never collide
-# at the profile root level. A profile may also list one of the child bundles
-# directly (the provider or the conversation UI installed on its own); two
-# root-level rows with the same id would abort boot with
-# "duplicate loader entry id". Inside the group the ids coexist instead: the
-# loader maps both rows onto one shared entry and the plugin runs once.
-#
-# Do NOT re-add `disabled: !!js ctx.loader.store[...]` guards here. They never
-# worked — `ctx.loader.store` is the root loader store (it only ever holds the
-# `include` entry), while profile entries live in the include subtree's store,
-# so the expression is always false. Pointing it at the right store would be
-# worse: the entry is registered before `disabled` is evaluated, so the check
-# would always see itself and disable the suite's children unconditionally.
-#
-# Coexistence caveat (loader semantics): while a direct row and the suite's
-# child row share one entry, removing either side from the bundle list of a
-# RUNNING dsh process disposes the shared entry and the plugin silently stops
-# until the next restart. Prefer installing either the suite OR the standalone
-# packages in a profile, and restart dsh after changing the bundle list.
+# Install the Suite or the standalone bundles in a profile, so each plugin id
+# is declared once. Settings address the same ids in either installation.
 - insert:
-    - id: suite-plugins
-      name: cordis:group
-      group: true
-      config:
-        - id: codex-provider
-          name: '@jcy2387/dsh-codex-provider'
-        - id: conversation-ui
-          name: '@jcy2387/dsh-conversation-ui'
+    - id: codex-provider
+      name: '@jcy2387/dsh-codex-provider'
+    - id: conversation-ui
+      name: '@jcy2387/dsh-conversation-ui'

package/package.json

@@ -2,7 +2,7 @@
   "name": "@jcy2387/dsh-suite",
   "displayName": "DSH Codex Suite",
   "description": "Use ChatGPT accounts with Codex models and a Codex-style conversation view.",
-  "version": "0.2.0-rc.2",
+  "version": "0.2.0-rc.2.1",
   "author": "jcy2387",
   "type": "module",
   "engines": {
@@ -42,8 +42,8 @@
   ],
   "license": "MIT",
   "dependencies": {
-    "@jcy2387/dsh-codex-provider": "0.2.0-rc.2",
-    "@jcy2387/dsh-conversation-ui": "0.2.0-rc.2"
+    "@jcy2387/dsh-codex-provider": "0.2.0-rc.2.1",
+    "@jcy2387/dsh-conversation-ui": "0.2.0-rc.2.1"
   },
   "exports": {
     "./package.json": "./package.json",