@khorsheed/dsh-context-guard 0.2.1 → 0.2.2

package/lib/types/index.d.ts

@@ -1,19 +1,33 @@
 /**
- * Context-guard plugin, node half. Registers the `context-guard` settings
- * namespace so the web settings page can render the compact-timing card and
- * the browser half can bind its `settingsScope` to the same section. The
- * plugin's own runtime behavior is purely client-side (the composer compact
- * button); this registration only exists to make the two tunables
- * (`thresholdRatio`, `maxTokens`) editable from the GUI instead of YAML.
+ * Context-guard plugin, node half. Serves the `context-guard` settings
+ * section so the web settings page can render the compact-timing card and
+ * the browser half can bind its scope to the same section — on rc.1 through
+ * the entry's own Config (below; SettingsForms serves and edits its volatile
+ * field), on 0.1.5 through an explicit `settings.register` namespace whose
+ * base layer is the composition entry. The plugin's own runtime behavior is
+ * purely client-side (the composer compact button); this registration only
+ * exists to make the two tunables (`thresholdRatio`, `maxTokens`) editable
+ * from the GUI instead of YAML.
  * @module @khorsheed/dsh-context-guard
  */
 import type { Context } from '@deepseek-ai/cordis';
+import type z from '@deepseek-ai/schemastery';
 export { CONTEXT_GUARD_NS } from './namespace.ts';
 export { ContextGuardSettingsSchema } from './settings.ts';
 /**
- * Register the compact-timing section when a settings provider exists.
+ * The entry Config: rc.1's SettingsForms serves exactly this schema under the
+ * row id (`context-guard` — the settings namespace by construction) and
+ * persists edits to its volatile field through the profile patch. On 0.1.5
+ * the same schema validates the legacy namespace instead; the volatile
+ * marker is probed at schema build time and simply absent there. The bare
+ * `z` annotation keeps the emitted type nameable under pnpm's layout.
+ */
+export declare const Config: z;
+/**
+ * Serve the compact-timing section on whichever settings face the host line
+ * carries.
  * @param ctx - Host context whose optional settings service owns the section.
- * @param config - the plugin's composition entry, used as the section's base layer.
+ * @param config - the plugin's composition entry, the legacy path's base layer.
  */
 export declare function apply(ctx: Context, config?: Record<string, unknown>): void;
 //# sourceMappingURL=index.d.ts.map

package/lib/types/index.js

@@ -1,10 +1,13 @@
 /**
- * Context-guard plugin, node half. Registers the `context-guard` settings
- * namespace so the web settings page can render the compact-timing card and
- * the browser half can bind its `settingsScope` to the same section. The
- * plugin's own runtime behavior is purely client-side (the composer compact
- * button); this registration only exists to make the two tunables
- * (`thresholdRatio`, `maxTokens`) editable from the GUI instead of YAML.
+ * Context-guard plugin, node half. Serves the `context-guard` settings
+ * section so the web settings page can render the compact-timing card and
+ * the browser half can bind its scope to the same section — on rc.1 through
+ * the entry's own Config (below; SettingsForms serves and edits its volatile
+ * field), on 0.1.5 through an explicit `settings.register` namespace whose
+ * base layer is the composition entry. The plugin's own runtime behavior is
+ * purely client-side (the composer compact button); this registration only
+ * exists to make the two tunables (`thresholdRatio`, `maxTokens`) editable
+ * from the GUI instead of YAML.
  * @module @khorsheed/dsh-context-guard
  */
 import { CONTEXT_GUARD_NS } from './namespace.js';
@@ -12,12 +15,32 @@ import { ContextGuardSettingsSchema } from './settings.js';
 export { CONTEXT_GUARD_NS } from './namespace.js';
 export { ContextGuardSettingsSchema } from './settings.js';
 /**
- * Register the compact-timing section when a settings provider exists.
+ * The entry Config: rc.1's SettingsForms serves exactly this schema under the
+ * row id (`context-guard` — the settings namespace by construction) and
+ * persists edits to its volatile field through the profile patch. On 0.1.5
+ * the same schema validates the legacy namespace instead; the volatile
+ * marker is probed at schema build time and simply absent there. The bare
+ * `z` annotation keeps the emitted type nameable under pnpm's layout.
+ */
+export const Config = ContextGuardSettingsSchema;
+/**
+ * Serve the compact-timing section on whichever settings face the host line
+ * carries.
  * @param ctx - Host context whose optional settings service owns the section.
- * @param config - the plugin's composition entry, used as the section's base layer.
+ * @param config - the plugin's composition entry, the legacy path's base layer.
  */
 export function apply(ctx, config = {}) {
     ctx.inject(['settings'], (settingsCtx) => {
-        settingsCtx.settings.register(CONTEXT_GUARD_NS, ContextGuardSettingsSchema, { base: config });
+        const settings = settingsCtx.settings;
+        if (typeof settings.register === 'function') {
+            // 0.1.5: the explicit namespace, the composition entry as its base layer.
+            settings.register(CONTEXT_GUARD_NS, ContextGuardSettingsSchema, { base: config });
+            return;
+        }
+        // rc.1: the entry's own Config (above) is the served form. Keep the
+        // auto-generated page out of the settings tree — the bundle's own cards
+        // (plugins.bundle.config / the legacy tab seat) edit the same field.
+        if (typeof settings.configure === 'function')
+            settings.configure({ auto: false }, ctx.fiber);
     });
 }

package/lib/types/namespace.d.ts

@@ -1,8 +1,8 @@
 /**
  * The settings namespace owned by the context-guard plugin. Plain string so
  * both the host half (settings registration) and the browser half
- * (settingsScope binding and the settings.plugin.item card key) import it
- * without dragging host-only dependencies into the client bundle.
+ * (settingsScope binding and the 0.1.5 settings.plugin.item card key) import
+ * it without dragging host-only dependencies into the client bundle.
  */
 /** Settings namespace owned by the context-guard plugin. */
 export declare const CONTEXT_GUARD_NS = "context-guard";

package/lib/types/namespace.js

@@ -1,8 +1,8 @@
 /**
  * The settings namespace owned by the context-guard plugin. Plain string so
  * both the host half (settings registration) and the browser half
- * (settingsScope binding and the settings.plugin.item card key) import it
- * without dragging host-only dependencies into the client bundle.
+ * (settingsScope binding and the 0.1.5 settings.plugin.item card key) import
+ * it without dragging host-only dependencies into the client bundle.
  */
 /** Settings namespace owned by the context-guard plugin. */
 export const CONTEXT_GUARD_NS = 'context-guard';

package/lib/types/settings.d.ts

@@ -1,9 +1,11 @@
 /**
  * Host-side settings section of the context-guard plugin: the schemastery
- * schema that validates the `context-guard` settings namespace. The browser
- * half reads the resolved section through `ctx.settingsScope` and the
- * settings page renders it as a plugin card; the composition entry (the
- * cordis.yml row) becomes the section's `base` layer, so YAML values keep
+ * schema of the `context-guard` configuration entry. rc.1's SettingsForms
+ * serves the entry's own Config and edits only its volatile fields; 0.1.5
+ * validates the legacy `settings.register` namespace with the same schema.
+ * The browser half reads the resolved section through whichever settings
+ * scope the line serves (see client/scope.ts); the composition entry (the
+ * cordis.yml row) becomes the section's base layer, so YAML values keep
  * working as the defaults the card can override.
  *
  * These two fields tune ONLY when the compact button appears — the official
@@ -11,10 +13,14 @@
  * `maxTokens` config and never touches this section.
  */
 import z from '@deepseek-ai/schemastery';
-/** Section shape: the context-occupancy fraction at which the button appears. */
-export declare const ContextGuardSettingsSchema: z<Schemastery.ObjectS<{
-    thresholdRatio: z<number, number>;
-}>, Schemastery.ObjectT<{
-    thresholdRatio: z<number, number>;
-}>>;
+/**
+ * Section shape: the context-occupancy fraction at which the button appears.
+ * The field is marked `.volatile()` when the running schemastery supports it
+ * (3.18.4, host rc.1 — SettingsForms serves and edits ONLY volatile fields);
+ * 0.1.5's schemastery (3.18.2) has no such method, the probe leaves the field
+ * plain, and the legacy register path carries the section (the marker is
+ * inert there). The inline probe (not a helper) keeps the emitted type
+ * nameable under pnpm's layout.
+ */
+export declare const ContextGuardSettingsSchema: z;
 //# sourceMappingURL=settings.d.ts.map

package/lib/types/settings.js

@@ -1,9 +1,11 @@
 /**
  * Host-side settings section of the context-guard plugin: the schemastery
- * schema that validates the `context-guard` settings namespace. The browser
- * half reads the resolved section through `ctx.settingsScope` and the
- * settings page renders it as a plugin card; the composition entry (the
- * cordis.yml row) becomes the section's `base` layer, so YAML values keep
+ * schema of the `context-guard` configuration entry. rc.1's SettingsForms
+ * serves the entry's own Config and edits only its volatile fields; 0.1.5
+ * validates the legacy `settings.register` namespace with the same schema.
+ * The browser half reads the resolved section through whichever settings
+ * scope the line serves (see client/scope.ts); the composition entry (the
+ * cordis.yml row) becomes the section's base layer, so YAML values keep
  * working as the defaults the card can override.
  *
  * These two fields tune ONLY when the compact button appears — the official
@@ -11,7 +13,18 @@
  * `maxTokens` config and never touches this section.
  */
 import z from '@deepseek-ai/schemastery';
-/** Section shape: the context-occupancy fraction at which the button appears. */
+const thresholdField = z.number().min(0.01).max(1).default(0.8);
+/**
+ * Section shape: the context-occupancy fraction at which the button appears.
+ * The field is marked `.volatile()` when the running schemastery supports it
+ * (3.18.4, host rc.1 — SettingsForms serves and edits ONLY volatile fields);
+ * 0.1.5's schemastery (3.18.2) has no such method, the probe leaves the field
+ * plain, and the legacy register path carries the section (the marker is
+ * inert there). The inline probe (not a helper) keeps the emitted type
+ * nameable under pnpm's layout.
+ */
 export const ContextGuardSettingsSchema = z.object({
-    thresholdRatio: z.number().min(0.01).max(1).default(0.8),
+    thresholdRatio: typeof thresholdField.volatile === 'function'
+        ? thresholdField.volatile()
+        : thresholdField,
 });

package/locale/en.json

@@ -0,0 +1,6 @@
+{
+  "meta": {
+    "title": "Context Guard",
+    "description": "Show a composer compact button when context occupancy crosses the threshold."
+  }
+}

package/locale/zh.json

@@ -0,0 +1,6 @@
+{
+  "meta": {
+    "title": "上下文守卫",
+    "description": "上下文占用越过设定比例时在输入框提醒一键压缩。"
+  }
+}

package/package.json

@@ -8,7 +8,7 @@
     "context",
     "compaction"
   ],
-  "version": "0.2.1",
+  "version": "0.2.2",
   "type": "module",
   "main": "lib/index.js",
   "types": "lib/types/index.d.ts",
@@ -26,9 +26,13 @@
       "default": "./lib/client.js"
     },
     "./src/*": "./src/*",
-    "./package.json": "./package.json"
+    "./package.json": "./package.json",
+    "./locale/*.json": "./locale/*.json"
   },
   "dsh": {
+    "references": [
+      "@khorsheed/dsh-bundle-conversation-toolbox"
+    ],
     "bundle": {
       "patch": "./cordis.patch.yml"
     },
@@ -60,28 +64,10 @@
     "@deepseek-ai/dsh-token-meter": "^0.1.0-rc.6",
     "react": "^18.2.0"
   },
-  "devDependencies": {
-    "@deepseek-ai/cordis": "^4.0.1",
-    "@deepseek-ai/dsh-api-remotes": "^0.1.5-rc.1",
-    "@deepseek-ai/dsh-client-locale": "^0.1.5-rc.1",
-    "@deepseek-ai/dsh-client-test-runtime": "^0.1.5-rc.1",
-    "@deepseek-ai/dsh-client-ui-conversation": "^0.1.5-rc.1",
-    "@deepseek-ai/dsh-client-ui-primitives": "^0.1.5-rc.1",
-    "@deepseek-ai/dsh-client-ui-renderer": "^0.1.5-rc.1",
-    "@deepseek-ai/dsh-client-ui-settings": "^0.1.5-rc.1",
-    "@deepseek-ai/dsh-client-ui-settings-plugins": "^0.1.5-rc.1",
-    "@deepseek-ai/dsh-client-ui-slots": "^0.1.5-rc.1",
-    "@deepseek-ai/dsh-invariants": "^0.1.5-rc.1",
-    "@deepseek-ai/dsh-session": "^0.1.5-rc.1",
-    "@deepseek-ai/dsh-token-meter": "^0.1.5-rc.1",
-    "@testing-library/react": "^16.1.0",
-    "@types/react": "~18.3.1",
-    "react": "^18.2.0",
-    "react-dom": "^18.2.0"
-  },
   "files": [
     "lib",
     "cordis.patch.yml",
+    "locale/*.json",
     "LICENSE",
     "CHANGELOG.md"
   ]