@usex/mikrotik-mcp 5.4.0 → 5.6.0

package/dist/cli.js

@@ -238,7 +238,7 @@ import {
   validatePolicyText,
   worstSeverity,
   writeBackup
-} from "./shared/cli-cvq8pxvn.js";
+} from "./shared/cli-gyqfq9j6.js";
 
 // src/cli.ts
 import { existsSync as existsSync2 } from "fs";

package/dist/index.d.ts

@@ -75,8 +75,15 @@ declare function listDevices(): {
 };
 /**
 * Resolve a (possibly undefined) device name to a concrete, existing config key.
-* Accepts a config key OR a device's free-text label; falls back to the default.
-* Only resolves to enabled devices.
+* Accepts a config key OR a device's free-text label. An omitted name uses the
+* configured default.
+*
+* FAIL-CLOSED: a name that matches no enabled device THROWS. It must never
+* degrade to the default router — a typo'd or stale device name silently
+* retargeting a write at whichever device happens to be first is the one bug
+* class here that can misconfigure the wrong physical device. `getDevice()`
+* already threw for this, but every caller resolved the name first and then
+* handed the laundered key to `getDevice`, so that guard could never fire.
 *
 * Matching is EXACT (key first, then label) — never fuzzy/substring — so a name
 * like "Ali Home" can never collapse onto a different device such as "home".

package/dist/index.js

@@ -29,7 +29,7 @@ import {
   selectToolModules,
   setConfig,
   updateSummaryLine
-} from "./shared/library-5p5mk963.js";
+} from "./shared/library-135yzct0.js";
 // src/server.ts
 import { McpServer } from "@modelcontextprotocol/sdk/server/mcp.js";
 import { ListToolsRequestSchema } from "@modelcontextprotocol/sdk/types.js";