@cueai/omni-reader-mcp 1.5.4 → 1.5.5

package/README.md

@@ -48,7 +48,7 @@ agent workspace remains the default allowed scope.
 For a local file, Bridge requests a Cube parse grant and uses the returned controlled
 granted-data-plane URL to upload the file and stream the result. A `BRIDGE_UPGRADE_REQUIRED`
 error means the running Bridge release is not accepted for direct local-file parsing —
-install `@cueai/omni-reader-mcp@1.5.4` using the official setup instructions, then retry the
+install `@cueai/omni-reader-mcp@1.5.5` using the official setup instructions, then retry the
 same parse. Always run `doctor --json` first when diagnosing a parse failure.
 
 ## Free credits
@@ -72,7 +72,7 @@ differ from the numbers above, report the live values.
 Always use an audited exact version, never an implicit `latest`:
 
 ```sh
-npx -y @cueai/omni-reader-mcp@1.5.4 setup
+npx -y @cueai/omni-reader-mcp@1.5.5 setup
 ```
 
 The interactive setup supports Hermes, Cursor, Claude Desktop, and generic stdio
@@ -80,9 +80,9 @@ configuration. Non-interactive installation uses the same argument parsing and w
 logic:
 
 ```sh
-npx -y @cueai/omni-reader-mcp@1.5.4 setup --client hermes --allowed-root /absolute/minimum/root --yes --json
-npx -y @cueai/omni-reader-mcp@1.5.4 setup --client cursor --add-root /absolute/minimum/root --yes --json
-npx -y @cueai/omni-reader-mcp@1.5.4 setup --client claude-desktop --allowed-root /absolute/minimum/root --yes --json
+npx -y @cueai/omni-reader-mcp@1.5.5 setup --client hermes --allowed-root /absolute/minimum/root --yes --json
+npx -y @cueai/omni-reader-mcp@1.5.5 setup --client cursor --add-root /absolute/minimum/root --yes --json
+npx -y @cueai/omni-reader-mcp@1.5.5 setup --client claude-desktop --allowed-root /absolute/minimum/root --yes --json
 ```
 
 When an agent or script runs under a pty (stdin is still a TTY), declare non-interactive
@@ -90,7 +90,7 @@ mode explicitly with `--headless` (alias `--non-interactive`): no `--yes` is req
 stdin is never read:
 
 ```sh
-npx -y @cueai/omni-reader-mcp@1.5.4 setup --client cursor --allowed-root /absolute/minimum/root --headless --json
+npx -y @cueai/omni-reader-mcp@1.5.5 setup --client cursor --allowed-root /absolute/minimum/root --headless --json
 ```
 
 ## Windows configuration
@@ -109,14 +109,14 @@ automatically; the second is the most robust when you configure by hand.
 1. **`cmd` + `npx` (what `setup` writes on Windows)** — `cmd.exe` is a real executable,
    so a client's no-shell spawn works:
    ```json
-   { "command": "cmd", "args": ["/d", "/c", "npx", "-y", "@cueai/omni-reader-mcp@1.5.4"] }
+   { "command": "cmd", "args": ["/d", "/c", "npx", "-y", "@cueai/omni-reader-mcp@1.5.5"] }
    ```
 2. **`node` + the package entry (most robust)** — skips `npx` entirely; the absolute
    path must be a stable install you control:
    ```json
    { "command": "node", "args": ["C:\\path\\to\\node_modules\\@cueai\\omni-reader-mcp\\dist\\index.js"] }
    ```
-   A deliberate local `npm install @cueai/omni-reader-mcp@1.5.4` gives you that stable
+   A deliberate local `npm install @cueai/omni-reader-mcp@1.5.5` gives you that stable
    path. Do not point the entry at an `_npx` cache directory — its hash subdirectory
    changes between installs.
 3. **Never use a session/timestamp directory** — such paths are cleaned up, and the
@@ -261,16 +261,16 @@ satisfies the constraints.
 ## Commands
 
 ```sh
-npx -y @cueai/omni-reader-mcp@1.5.4 doctor
-npx -y @cueai/omni-reader-mcp@1.5.4 doctor --json
-npx -y @cueai/omni-reader-mcp@1.5.4 clean
-npx -y @cueai/omni-reader-mcp@1.5.4 uninstall --yes --json
+npx -y @cueai/omni-reader-mcp@1.5.5 doctor
+npx -y @cueai/omni-reader-mcp@1.5.5 doctor --json
+npx -y @cueai/omni-reader-mcp@1.5.5 clean
+npx -y @cueai/omni-reader-mcp@1.5.5 uninstall --yes --json
 ```
 
 Running the pinned version without a command starts the stdio MCP server:
 
 ```sh
-npx -y @cueai/omni-reader-mcp@1.5.4
+npx -y @cueai/omni-reader-mcp@1.5.5
 ```
 
 `doctor --json` returns package/npm/client adapter, Key present/absent, allowed-root
@@ -283,15 +283,15 @@ definitively "available" until a real local-file parse validates the route.
 
 ## Network diagnostics
 
-Run `npx -y @cueai/omni-reader-mcp@1.5.4 doctor --json` first. Diagnose failures by
+Run `npx -y @cueai/omni-reader-mcp@1.5.5 doctor --json` first. Diagnose failures by
 stage instead of guessing an endpoint:
 
-| Code | Stage | Meaning |
+| Failure | Stage | Meaning |
 |---|---|---|
 | `CUBE_UNAVAILABLE` | before upload | the control plane could not create a parse grant |
 | `PRINCIPAL_CONCURRENCY_LIMIT` | before upload | the principal already has the maximum active parses; wait for `retry_after`, then retry the same parse |
-| `BRIDGE_UPGRADE_REQUIRED` | before upload | this Bridge release is too old; install `@cueai/omni-reader-mcp@1.5.4` via the official setup, then retry the same parse |
-| `IIIS_UNAVAILABLE` | after grant creation | the granted upload stage could not complete |
+| `BRIDGE_UPGRADE_REQUIRED` | before upload | this Bridge release is too old; install `@cueai/omni-reader-mcp@1.5.5` via the official setup, then retry the same parse |
+| a secure upload-stage failure | after grant creation | the file was granted, but the secure upload stage did not complete |
 | `CUBE_PROTOCOL_ERROR` | control-plane response | the response did not match the required contract |
 | `MCP error -32000: Connection closed` | before Bridge starts | the client launcher shape is invalid; see Windows configuration |
 
@@ -309,12 +309,12 @@ the same way from every client.
 
 ## Uninstall and rollback
 
-`uninstall --yes --json` removes only a trusted 1.5.3 or 1.5.4 Bridge entry, plus
+`uninstall --yes --json` removes only a trusted 1.5.4 or 1.5.5 Bridge entry, plus
 the exact broken bare-`npx` Windows entry written by 1.5.1. When a matching trusted
 backup exists, it restores the original URL-only `omni-reader` entry. Uninstall never
 deletes user source files and never silently removes unexpired local results.
 
-To roll back from 1.5.4:
+To roll back from 1.5.5:
 
 1. stop recommending or installing that version;
 2. run `uninstall --yes --json` to restore the trusted URL-only entry;

package/dist/cli/agent-config.js

@@ -7,7 +7,7 @@ const PACKAGE_SPEC = `@cueai/omni-reader-mcp@${BRIDGE_RELEASE_VERSION}`;
 // The release that the current version is a trusted upgrade from: normal upgrade,
 // uninstall, and rollback recognize exactly {previous, current}. Bump this to the
 // version we just published when BRIDGE_RELEASE_VERSION advances.
-const PREVIOUS_RELEASE_VERSION = "1.5.3";
+const PREVIOUS_RELEASE_VERSION = "1.5.4";
 const PREVIOUS_PACKAGE_SPEC = `@cueai/omni-reader-mcp@${PREVIOUS_RELEASE_VERSION}`;
 // Preserve the one evidenced two-release migration exception: 1.5.1 setup wrote a
 // bare `npx` launcher on Windows, so later setup/uninstall versions must still be able
@@ -641,7 +641,7 @@ export function expectedBridgeVersion(target, value, platform) {
 }
 function isLegacyBridgeEntry(target, value, platform) {
     // Defer the entire invocation-shape decision to the single platform policy:
-    // exact pinned {1.5.3 previous, 1.5.4 current} plus the exact Windows 1.5.1
+    // exact pinned {1.5.4 previous, 1.5.5 current} plus the exact Windows 1.5.1
     // bare-npx migration source. The historical platform-agnostic acceptance of a
     // bare unpinned `npx -y @cueai/omni-reader-mcp` is removed: it widened the
     // frozen trust set to a floating latest on every OS, which expectedBridgeVersion

package/dist/constants.d.ts

@@ -6,7 +6,7 @@ export declare const CUBE_GRANT_PROTOCOL_VERSION = "omni.parse_grant.v1";
 export declare const GRANTED_STREAM_PROTOCOL_VERSION = "omni.granted_parse_stream.v1";
 export declare const DEFAULT_CUBE_BASE_URL = "https://mcp.cuecue.cn";
 export declare const DEFAULT_IIIS_GRANTED_BASE_URL = "https://omni-upload.cuecue.cn/omni/granted/";
-export declare const BRIDGE_RELEASE_VERSION = "1.5.4";
+export declare const BRIDGE_RELEASE_VERSION = "1.5.5";
 export declare const REMOTE_OMNI_MCP_URL = "https://mcp.cuecue.cn/api/omni-reader/mcp/";
 export declare const FOREGROUND_BUDGET_MS = 15000;
 export declare const STATUS_LONG_POLL_MAX_MS = 20000;

package/dist/constants.js

@@ -6,7 +6,7 @@ export const CUBE_GRANT_PROTOCOL_VERSION = "omni.parse_grant.v1";
 export const GRANTED_STREAM_PROTOCOL_VERSION = "omni.granted_parse_stream.v1";
 export const DEFAULT_CUBE_BASE_URL = "https://mcp.cuecue.cn";
 export const DEFAULT_IIIS_GRANTED_BASE_URL = "https://omni-upload.cuecue.cn/omni/granted/";
-export const BRIDGE_RELEASE_VERSION = "1.5.4";
+export const BRIDGE_RELEASE_VERSION = "1.5.5";
 export const REMOTE_OMNI_MCP_URL = "https://mcp.cuecue.cn/api/omni-reader/mcp/";
 export const FOREGROUND_BUDGET_MS = 15_000;
 export const STATUS_LONG_POLL_MAX_MS = 20_000;

package/dist/cube-client.js

@@ -185,7 +185,7 @@ async function grantResponseError(response) {
         if (bridgeUpgradeRequiredSchema.safeParse(body).success) {
             return bridgeError("BRIDGE_UPGRADE_REQUIRED", "This Bridge release is not accepted for direct local-file parsing.", false, {
                 failureScope: "service",
-                userAction: "Upgrade to @cueai/omni-reader-mcp@1.5.4 using the official Omni setup instructions, then retry the same local-file parse.",
+                userAction: `Upgrade to @cueai/omni-reader-mcp@${BRIDGE_RELEASE_VERSION} using the official Omni setup instructions, then retry the same local-file parse.`,
             });
         }
     }

package/package.json

@@ -1,7 +1,20 @@
 {
   "name": "@cueai/omni-reader-mcp",
-  "version": "1.5.4",
+  "version": "1.5.5",
   "description": "Local stdio MCP bridge for direct Omni document parsing",
+  "keywords": [
+    "mcp",
+    "model-context-protocol",
+    "omni-reader",
+    "document-parsing",
+    "pdf",
+    "ocr",
+    "url-parsing",
+    "local-files",
+    "audio",
+    "video",
+    "ai-agents"
+  ],
   "type": "module",
   "license": "UNLICENSED",
   "engines": {