dsh-perm-gate 4.1.0-beta.1 → 4.1.0

package/lib/index.js

@@ -1,10 +1,10 @@
 import { readFileSync } from 'node:fs';
 import { join } from 'node:path';
-import { Config, resolveDshHome, resolveDataDir, ensureDataDir, resolveGatePresets, resolvePermissiveStrategies, resolveRulesFile } from './config.js';
+import { Config, RULES_NAMESPACE, RulesSchema, readRulesFromSettings, resolveDshHome, resolveDataDir, ensureDataDir, resolveGatePresets, resolvePermissiveStrategies, resolveRulesFile } from './config.js';
 import { runDryRun } from './dry-run.js';
 import { registerDryRunRoute, registerEventsRoute, registerHealthRoute, registerLearningRoute, registerNetworkRoute, registerReceiverRoute, registerReviewRoutes, registerRulesRoute } from './events.js';
 import { buildReceiverInfo } from './receiver-info.js';
-import { readRulesView } from './rules-view.js';
+import { readRulesView, readRulesViewFromSettings } from './rules-view.js';
 import { PermGateRuntime } from './runtime.js';
 import { classifySessions, sweepSessionData } from './session-sweep.js';
 import { decideNetworkTarget } from './network.js';
@@ -192,6 +192,11 @@ export function apply(ctx, config = {}) {
     // Runtime-adjustable config: the composition entry is the base; the settings
     // namespace layers on top and `current()` always reads the active section.
     let current = () => config;
+    // ─── Rules settings scope (dsh-perm-gate-rules namespace) ────────────────
+    // Holds the live settings-sourced rules document. When non-undefined, the
+    // runtime prefers it over the rules file on disk.
+    let rulesScope;
+    const readRulesDocument = () => readRulesFromSettings(rulesScope);
     // Plugin-owned data files live under $DSH_HOME (node_modules may be
     // read-only). The default resolves to `$DSH_HOME` / `~/.dsh`, so a profile
     // entry that omits `config` still records events, snapshots and learning.
@@ -338,6 +343,8 @@ export function apply(ctx, config = {}) {
         // `$DSH_HOME/perm-gate/rules.yml` the user writes is actually loaded without
         // also having to declare `rulesFile` in the composition entry.
         rulesFile: resolveRulesFile(typeof config.rulesFile === 'string' ? config.rulesFile : undefined, dataDir),
+        // Settings-sourced rules take precedence over the file when present.
+        readRulesDocument,
         // The whole gate is scoped to the presets that opt into it (default: the
         // `permissive` tier this plugin adds); elsewhere it stands down entirely.
         gatePresets: resolveGatePresets(Array.isArray(config.gatePresets) ? config.gatePresets : undefined),
@@ -456,6 +463,21 @@ export function apply(ctx, config = {}) {
             });
         },
     });
+    // ─── Rules settings namespace (dsh-perm-gate-rules) ─────────────────────
+    // Registers the rules document in its own DSH settings namespace so the gate
+    // loads rules from settings (when configured) instead of the rules file.
+    installSettingsSection(ctx, RULES_NAMESPACE, RulesSchema, {}, {
+        setSource: (source) => {
+            rulesScope = { get: source };
+        },
+        onChange: () => { },
+        onScope: (scope) => {
+            rulesScope = scope;
+            // When rules change in settings, reload the runtime so the new ruleset
+            // takes effect on the next tool call.
+            scope.watch(() => { runtime.reload(); });
+        },
+    });
     // Event feed HTTP API (best effort): the dsh webServer service exposes the
     // JSONL decision events to the browser half; without it events stay on disk.
     try {
@@ -518,12 +540,17 @@ export function apply(ctx, config = {}) {
             });
             if (offDryRun !== undefined)
                 ctx.effect(() => () => { offDryRun(); }, 'dsh-perm-gate: dry-run route');
-            // Permissions YAML view: the document the gate is actually loading, shown
-            // so the panel is never editing a file it cannot display. Read-only, and
-            // resolved exactly as the gate resolves it — a view that resolved its own
-            // path could describe a different file than the one in force.
+            // Permissions view: prefer the settings namespace (dsh-perm-gate-rules)
+            // when it carries a real configuration; fall back to the rules file.
             const rulesFilePath = resolveRulesFile(typeof config.rulesFile === 'string' ? config.rulesFile : undefined, dataDir);
-            const offRules = registerRulesRoute(webServer, { view: () => readRulesView(rulesFilePath) });
+            const offRules = registerRulesRoute(webServer, {
+                view: () => {
+                    const settingsDoc = readRulesDocument();
+                    return settingsDoc !== undefined
+                        ? readRulesViewFromSettings(settingsDoc)
+                        : readRulesView(rulesFilePath);
+                },
+            });
             if (offRules !== undefined)
                 ctx.effect(() => () => { offRules(); }, 'dsh-perm-gate: rules route');
             // Receiver projection for the settings card (provider/model catalog is

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "dsh-perm-gate",
-  "version": "4.1.0-beta.1",
+  "version": "4.1.0",
   "publishConfig": {
     "registry": "https://registry.npmjs.org",
     "access": "public",