@logictan/dsh-plugins-all 0.5.11 → 0.5.12

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.
Files changed (2) hide show
  1. package/cordis.patch.yml +10 -7
  2. package/package.json +3 -3
package/cordis.patch.yml CHANGED
@@ -168,9 +168,9 @@
168
168
  # dsh-browser-agent bundle patch layer.
169
169
  #
170
170
  # One bare plugin row. The package ships two halves — the host half
171
- # (exports ".") registers the `browser-agent` settings namespace and the
172
- # `browser_agent` model tool, the browser half (exports "./client") registers
173
- # the Plugins-page configuration card.
171
+ # (exports ".") registers the `browser_agent` model tool and exports the
172
+ # `Config` schema the Plugins page derives its form from, the browser half
173
+ # (exports "./client") registers the Plugins-page configuration card.
174
174
  #
175
175
  # The row must stay a BARE package name: the web plugin table locates each
176
176
  # package's `dsh.client` manifest from the specifier of the loader row that
@@ -192,10 +192,13 @@
192
192
  # from ../dsh-loop-guard
193
193
  # The dsh-loop-guard bundle patch: the guard needs no deployment-specific
194
194
  # config to mount (its defaults detect reasoning-only steps and steer on the
195
- # second strike). Every key below is also editable from the Plugins page — the
196
- # guard registers the `loop-guard` settings namespace, and that user layer is
197
- # layered over this composition layer. Use this file for values that must be
198
- # baked into the deployment; use the Plugins page for the rest.
195
+ # second strike). Every key below is also editable from the Plugins page — as of
196
+ # the 0.1.7-alpha.1 settings redesign the guard's own `Config` schema is the one
197
+ # configuration surface, and `dsh-settings` derives that page's form from it,
198
+ # keyed by this row's id. There is no separate settings namespace and no
199
+ # precedence rule between layers: the row's `config` IS the entry's config, and
200
+ # the page edits that same entry. Use this file for values that must be baked
201
+ # into the deployment; use the Plugins page for the rest.
199
202
  #
200
203
  # - insert:
201
204
  # - id: loop-guard
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@logictan/dsh-plugins-all",
3
- "version": "0.5.11",
3
+ "version": "0.5.12",
4
4
  "description": "DSH plugin aggregate bundle: one install for every plugin in this repo.",
5
5
  "license": "MIT",
6
6
  "type": "module",
@@ -20,13 +20,13 @@
20
20
  ],
21
21
  "dependencies": {
22
22
  "@logictan/dsh-agy-link": "^0.4.37",
23
- "@logictan/dsh-browser-agent": "^0.1.1",
23
+ "@logictan/dsh-browser-agent": "^0.2.0",
24
24
  "@logictan/dsh-config-manager": "^0.1.63",
25
25
  "@logictan/dsh-ctx-mem": "^0.5.1",
26
26
  "@logictan/dsh-easyrewrite": "^2.5.4",
27
27
  "@logictan/dsh-fakeip-fetch": "^0.1.0",
28
28
  "@logictan/dsh-imagegen": "^1.5.13",
29
- "@logictan/dsh-loop-guard": "^1.0.1",
29
+ "@logictan/dsh-loop-guard": "^1.1.0",
30
30
  "@logictan/dsh-openviking": "^0.4.4",
31
31
  "@logictan/dsh-workbuddy-connect": "^0.5.4",
32
32
  "@logictan/dshmarket": "^1.48.0"