@logictan/dsh-plugins-all 0.5.13 → 0.5.15

package/cordis.patch.yml

@@ -97,56 +97,6 @@
     - id: fakeip-fetch
       name: '@logictan/dsh-fakeip-fetch'
 
-# from ../ctx-mem
-# ctx-mem bundle patch layer.
-#
-# ONE row. The package ships two halves, but only the bridge has a row here.
-#
-# `ctx-mem-bridge` runs on the PROFILE plane and is ENABLED. The host's cordis
-# loader resolves every loader entry's config through the synchronous
-# `internal/config` waterfall, so this row hangs off it and injects a `patches`
-# array into each preset composition as it is mounted: the preset's own
-# `compaction-basic` row is disabled and `ctx-mem` is inserted into the same
-# `compaction` group. That is what makes the backend work in ANY mode without a
-# dedicated preset copy.
-#
-# The ENGINE (`@logictan/dsh-ctx-mem/engine`) has no row here on purpose. A compaction
-# backend is a `ctx.compaction` SERVICE replacement, and every shipped preset
-# composes its own backend inside an `isolate: { compaction: true }` group
-# (`dsh-agent-presets/presets/*/agent.cordis.yml`), so an agent context resolves
-# `ctx.compaction` inside that realm and never sees a profile-plane provider.
-# A profile-plane engine row would therefore not replace the preset's backend —
-# it would add a SECOND engine beside it: a listener registered there carries no
-# scope tag, and an untagged listener is admitted for every agent in the process
-# (`dsh-scope`'s scope filter returns true when the dispatch context has no
-# tag), so its pressure listener would fire for every agent and both engines
-# would compact the same session. A DISABLED engine row is equally pointless: it
-# never mounts, and `dsh-plugin-manager`'s `declaredRows` lists every row the
-# bundle declares — disabled ones included — so it only adds a second, useless
-# entry beside the bridge row in the plugin UI.
-#
-# The package must still be INSTALLED even though no row here names the engine:
-# this row names `@logictan/dsh-ctx-mem`, and the row the bridge injects names
-# `@logictan/dsh-ctx-mem/engine` — both resolve by package name from the profile
-# root.
-#
-# This row must stay a BARE package name. The web plugin table locates each
-# package's `dsh.client` manifest from the specifier of the loader row that
-# mounts it (`dsh-client-modules`'s `exactPackageSpecifier`), and that function
-# accepts only a bare name: a subpath row resolves to no manifest, so the
-# package's browser half would silently never load. That is why the bridge owns
-# `exports["."]` and the engine was moved to `./engine`.
-#
-# The bridge only covers `standard`, `ptc` and `cordis` (see COVERED_PRESETS in
-# src/bridge.js). `minimal` and user-authored presets have no compaction group
-# by design, and a profile without `agent-presets` never mounts a preset subtree
-# at all, so the bridge is inert there.
-- insert:
-    - id: ctx-mem-bridge
-      name: '@logictan/dsh-ctx-mem'
-      config:
-        engine: {}
-
 # from ../dsh-agy-link
 # dsh-agy-link bundle patch — inserts the antigravity (agy CLI) provider
 # plugin entry into the composition. Users install via:

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@logictan/dsh-plugins-all",
-  "version": "0.5.13",
+  "version": "0.5.15",
   "description": "DSH plugin aggregate bundle: one install for every plugin in this repo.",
   "license": "MIT",
   "type": "module",
@@ -23,12 +23,11 @@
     "@logictan/dsh-better-reasoning-effort": "^0.5.0",
     "@logictan/dsh-browser-agent": "^0.2.0",
     "@logictan/dsh-config-manager": "^0.1.63",
-    "@logictan/dsh-ctx-mem": "^0.5.1",
     "@logictan/dsh-easyrewrite": "^2.5.4",
     "@logictan/dsh-fakeip-fetch": "^0.1.0",
     "@logictan/dsh-imagegen": "^1.5.13",
-    "@logictan/dsh-loop-guard": "^1.1.0",
-    "@logictan/dsh-openviking": "^0.4.4",
+    "@logictan/dsh-loop-guard": "^1.1.1",
+    "@logictan/dsh-openviking": "^0.4.5",
     "@logictan/dsh-workbuddy-connect": "^0.5.4",
     "@logictan/dshmarket": "^1.48.0"
   }