0xray 3.0.14 → 3.1.0

package/src/mcps/lint.server.ts

@@ -51,7 +51,7 @@ class XrayLintServer {
     this.setupToolHandlers();
     void frameworkLogger.log(
       "lint.server",
-      "-strray-lint-mcp-server-initialized-",
+      "-xray-lint-mcp-server-initialized-",
       "info",
       { message: "0xRay Lint MCP Server initialized" },
     );
@@ -467,7 +467,7 @@ ${checkResults.details.map((d) => `• ${d}`).join("\n")}
     await this.server.connect(transport);
     await frameworkLogger.log(
       "lint.server",
-      "-strray-lint-mcp-server-started-",
+      "-xray-lint-mcp-server-started-",
       "info",
       { message: "0xRay Lint MCP Server started" },
     );

package/src/mcps/mcp-client.ts

@@ -153,7 +153,7 @@ export class MCPClient extends EventEmitter {
    * Pure MCP mode — simulation and generic fallbacks are disabled.
    */
   private get isPureMcpMode(): boolean {
-    return process.env.STRRAY_FORCE_MCP_GOVERNANCE === 'true';
+    return process.env.XRAY_FORCE_MCP_GOVERNANCE === 'true';
   }
 
   /**
@@ -344,17 +344,17 @@ export class MCPClient extends EventEmitter {
       ],
       'framework-help': [
         {
-          name: 'strray_get_capabilities',
+          name: 'xray_get_capabilities',
           description: 'Get 0xRay framework capabilities',
           inputSchema: { type: 'object', properties: {} },
         },
         {
-          name: 'strray_get_commands',
+          name: 'xray_get_commands',
           description: 'Get available 0xRay commands',
           inputSchema: { type: 'object', properties: {} },
         },
         {
-          name: 'strray_explain_capability',
+          name: 'xray_explain_capability',
           description: 'Explain a specific capability',
           inputSchema: {
             type: 'object',
@@ -470,7 +470,7 @@ export class MCPClient extends EventEmitter {
       if (this.isPureMcpMode) {
         throw new Error(
           `[PURE MCP] No real response for ${serverName}/${toolName}. ` +
-          `All fallbacks are disabled when STRRAY_FORCE_MCP_GOVERNANCE=true.`
+          `All fallbacks are disabled when XRAY_FORCE_MCP_GOVERNANCE=true.`
         );
       }
 

package/src/mcps/orchestrator/server.ts

@@ -12,7 +12,7 @@ import {
   ListToolsRequestSchema,
 } from '@modelcontextprotocol/sdk/types.js';
 import { frameworkLogger } from '../../core/framework-logger.js';
-import { StringRayStateManager } from '../../state/state-manager.js';
+import { XrayStateManager } from '../../state/state-manager.js';
 import { MultiAgentOrchestrationCoordinator } from '../../orchestrator/multi-agent-orchestration-coordinator.js';
 
 import { TaskHandler } from './handlers/task-handler.js';
@@ -45,7 +45,7 @@ export class OrchestratorServer {
 
   constructor() {
     // Initialize actual coordinator
-    const stateManager = new StringRayStateManager();
+    const stateManager = new XrayStateManager();
     this.coordinator = new MultiAgentOrchestrationCoordinator(stateManager);
     
     // Initialize handlers

package/src/mcps/researcher.server.ts

@@ -18,6 +18,7 @@ import {
 import * as fs from "fs";
 import * as path from "path";
 import { frameworkLogger } from "../core/framework-logger.js";
+import { tryLLMGovernance } from "../governance/llm-governance-provider.js";
 
 interface SearchResult {
   file: string;
@@ -482,47 +483,31 @@ class XrayLibrarianServer {
    */
   async analyzeProposal(args: AnalyzeProposalArgs): Promise<CallToolResult> {
     const { proposalTitle = "", proposalDescription = "", evidence = [], proposalType = "" } = args || {};
-    const text = `${proposalTitle} ${proposalDescription} ${(evidence || []).join(" ")}`.toLowerCase();
-
-    let decision: "approve" | "reject" | "abstain" = "approve";
-    let confidence = 0.80;
-    let reasoning = "From a project-wide analysis perspective, the proposal aligns with observed recurring patterns and has supporting evidence in the corpus.";
-
-    if (text.includes("aml") || text.includes("kyc") || text.includes("anti-money")) {
-      decision = "approve";
-      confidence = 0.86;
-      reasoning = "AML/KYC compliance integration is a recurring pattern across financial services codebases. The corpus shows that automated transaction monitoring reduces regulatory incident frequency by approximately 60% when properly integrated with sanction list APIs.";
-    } else if (text.includes("psd2") || text.includes("strong customer authentication") || text.includes("payment initiation")) {
-      decision = "approve";
-      confidence = 0.88;
-      reasoning = "PSD2 SCA patterns are well-established in the corpus across multiple implementations. The Berlin Group standards provide a reliable reference architecture, and existing integrations show consistent compliance with EBA regulatory technical standards.";
-    } else if (text.includes("gdpr") || text.includes("right to erasure") || text.includes("data protection")) {
-      decision = "approve";
-      confidence = 0.91;
-      reasoning = "GDPR data erasure pipeline patterns appear in approximately 35% of enterprise codebases in the corpus. The most successful implementations use the saga pattern with compensating transactions for cross-system consistency.";
-    } else if (text.includes("extract method")) {
-      decision = "approve";
-      confidence = 0.89;
-      reasoning = "The Extract Method pattern is a core refactoring technique that improves modularity; the corpus shows consistent positive outcomes when applied to repeated logic across many sessions.";
-    } else if (text.includes("test coverage")) {
-      decision = "approve";
-      confidence = 0.94;
-      reasoning = "Test coverage expansion is one of the highest-leverage improvements for long-term project health, directly reducing regression incidents across 100+ sessions in the historical data.";
-    } else if (text.includes("technical debt")) {
-      decision = "approve";
-      confidence = 0.85;
-      reasoning = "Systematic technical debt reduction is strongly supported by historical data showing fewer critical violations and faster feature delivery in low-debt modules.";
-    }
 
-    if (proposalType === "fix" && !text.includes("pattern") && !text.includes("recurring")) {
-      confidence = Math.max(0.68, confidence - 0.10);
+    const vote = await tryLLMGovernance(
+      "researcher",
+      proposalTitle || "",
+      proposalDescription || "",
+      evidence || [],
+      proposalType || "",
+    );
+
+    if (!vote) {
+      return {
+        content: [
+          {
+            type: "text",
+            text: "DECISION: abstain\nCONFIDENCE: 0.50\nREASONING: No LLM governance provider configured. Set XRAY_GOVERNANCE_LLM_ENABLED=true + XRAY_LLM_ENDPOINT, or install Hermes and run: hermes auth add xai-oauth --no-browser",
+          },
+        ],
+      };
     }
 
     return {
       content: [
         {
           type: "text",
-          text: `DECISION: ${decision}\nCONFIDENCE: ${confidence.toFixed(2)}\nREASONING: ${reasoning}`,
+          text: `DECISION: ${vote.decision}\nCONFIDENCE: ${vote.confidence.toFixed(2)}\nREASONING: ${vote.reasoning}`,
         },
       ],
     };

package/src/mcps/simulation/server-simulations.ts

@@ -86,7 +86,7 @@ export const researcherSimulations: Record<string, SimulatorFunction> = {
  * Framework Help server simulations
  */
 export const frameworkHelpSimulations: Record<string, SimulatorFunction> = {
-  strray_get_capabilities: (): MCPToolResult => ({
+  xray_get_capabilities: (): MCPToolResult => ({
     content: [
       {
         type: 'text',
@@ -118,7 +118,7 @@ export const frameworkHelpSimulations: Record<string, SimulatorFunction> = {
     ],
   }),
 
-  strray_get_commands: (): MCPToolResult => ({
+  xray_get_commands: (): MCPToolResult => ({
     content: [
       {
         type: 'text',
@@ -146,7 +146,7 @@ framework-reporting-system - Generate comprehensive framework reports
     ],
   }),
 
-  strray_explain_capability: (): MCPToolResult => ({
+  xray_explain_capability: (): MCPToolResult => ({
     content: [
       {
         type: 'text',

package/src/skills/hermes-agent/SKILL.md

@@ -1,21 +1,21 @@
 ---
 name: hermes-agent
-description: Manage StringRay framework from Hermes Agent via the native strray-hermes plugin. Covers the 4 plugin tools (validate, codex_check, health, hooks), lifecycle hooks, slash commands, bridge architecture, and CLI fallback.
+description: Manage 0xRay framework from Hermes Agent via the native xray-hermes plugin. Covers the 4 plugin tools (validate, codex_check, health, hooks), lifecycle hooks, slash commands, bridge architecture, and CLI fallback.
 version: 2.1.0
-author: StringRay AI
+author: 0xRay AI
 metadata:
   hermes:
-    tags: [StringRay, Plugin, Validation, Codex, GitHooks, Bridge]
+    tags: [0xRay, Plugin, Validation, Codex, GitHooks, Bridge]
     related_skills: []
 ---
 
-# StringRay Hermes Plugin (strray-hermes)
+# 0xRay Hermes Plugin (xray-hermes)
 
-Native Hermes plugin providing StringRay framework integration — quality gates, codex enforcement, git hooks, and full pre/post processing pipeline. Runs via a Node.js bridge to compiled framework components.
+Native Hermes plugin providing 0xRay framework integration — quality gates, codex enforcement, git hooks, and full pre/post processing pipeline. Runs via a Node.js bridge to compiled framework components.
 
 ## When to Use
 
-- User asks about StringRay health, validation, or codex checks
+- User asks about 0xRay health, validation, or codex checks
 - User wants to install/manage git hooks for automated enforcement
 - User asks about the plugin's tools, hooks, or slash commands
 - User asks about bridge errors or framework not loading
@@ -24,11 +24,11 @@ Native Hermes plugin providing StringRay framework integration — quality gates
 ## Plugin Architecture
 
 ```
-~/.hermes/plugins/strray-hermes/
+~/.hermes/plugins/xray-hermes/
 ├── __init__.py         # Plugin registration, hooks, slash commands
 ├── tools.py            # 4 tool handlers (validate, codex_check, health, hooks)
 ├── schemas.py          # JSON schemas the LLM sees
-├── bridge.mjs          # Node.js bridge to compiled StringRay framework
+├── bridge.mjs          # Node.js bridge to compiled 0xRay framework
 ├── plugin.yaml         # Plugin metadata (name, version, tools, hooks)
 ├── types.py            # TypeScript-equivalent type definitions
 ├── after-install.md    # Post-install instructions
@@ -43,17 +43,17 @@ Native Hermes plugin providing StringRay framework integration — quality gates
 
 **Fallback:** When bridge is unavailable, tools fall back to `npx 0xray` CLI commands.
 
-**Config path resolution:** `STRRAY_CONFIG_DIR/` > `.strray/` > `.opencode/strray/` > built-in defaults.
+**Config path resolution:** `XRAY_CONFIG_DIR/` > `.xray/` > `.opencode/xray/` > built-in defaults.
 
 ## 4 Tools
 
-### strray_validate
+### xray_validate
 
 Run pre-commit validation on files. Uses bridge quality gate + processor pipeline, falls back to CLI.
 
 ```
-strray_validate(files=["src/my-module.ts"], operation="commit")
-strray_validate(files=["src/auth.ts", "src/auth.test.ts"], operation="modify")
+xray_validate(files=["src/my-module.ts"], operation="commit")
+xray_validate(files=["src/auth.ts", "src/auth.test.ts"], operation="modify")
 ```
 
 Parameters:
@@ -62,13 +62,13 @@ Parameters:
 
 Returns: pass/fail with per-file results and violations.
 
-### strray_codex_check
+### xray_codex_check
 
 Validate code against the 60-term Universal Development Codex. Checks error-handling, type-safety, performance, security, architecture.
 
 ```
-strray_codex_check(code="const x: any = foo()", operation="create")
-strray_codex_check(code=snippet, operation="modify", focus_areas=["security", "error-handling"])
+xray_codex_check(code="const x: any = foo()", operation="create")
+xray_codex_check(code=snippet, operation="modify", focus_areas=["security", "error-handling"])
 ```
 
 Parameters:
@@ -78,25 +78,25 @@ Parameters:
 
 Returns: violations list with actionable remediation.
 
-### strray_health
+### xray_health
 
 Framework health check. Returns version, loaded components, project root.
 
 ```
-strray_health()
+xray_health()
 ```
 
 Returns: framework status, version, component availability, node version.
 
-### strray_hooks
+### xray_hooks
 
-Manage StringRay git hooks (install, uninstall, list, status).
+Manage 0xRay git hooks (install, uninstall, list, status).
 
 ```
-strray_hooks(action="install")
-strray_hooks(action="status")
-strray_hooks(action="list")
-strray_hooks(action="uninstall", hooks=["pre-commit"])
+xray_hooks(action="install")
+xray_hooks(action="status")
+xray_hooks(action="list")
+xray_hooks(action="uninstall", hooks=["pre-commit"])
 ```
 
 Parameters:
@@ -122,7 +122,7 @@ Fires before ANY tool executes:
 1. Tracks session stats
 2. Logs tool-start event to `logs/framework/plugin-tool-events.log`
 3. For code-producing tools (write_file, patch, execute_code, write, edit): runs quality gate + pre-processors via bridge
-4. For other tools: nudges when a StringRay MCP alternative exists (e.g., grep → search_codebase, eslint → strray_lint)
+4. For other tools: nudges when a 0xRay MCP alternative exists (e.g., grep → search_codebase, eslint → xray_lint)
 
 ### post_tool_call
 
@@ -137,16 +137,16 @@ Fires when a new session starts. Resets stats and logs to disk. Registration is
 ## Slash Command
 
 ```
-/strray status    — Plugin and framework health (calls bridge)
-/strray stats     — Session pipeline statistics
-/strray help      — Show available commands
+/xray status    — Plugin and framework health (calls bridge)
+/xray stats     — Session pipeline statistics
+/xray help      — Show available commands
 /sr status        — Alias
 ```
 
 ## Session Stats (tracked automatically)
 
-The plugin tracks per-session counters visible via `/strray stats`:
-- total_tool_calls, code_operations, strray_mcp_calls, native_tool_calls
+The plugin tracks per-session counters visible via `/xray stats`:
+- total_tool_calls, code_operations, xray_mcp_calls, native_tool_calls
 - quality_gate_runs, quality_gate_blocks
 - pre_processor_runs, post_processor_runs
 - bridge_calls, bridge_errors
@@ -164,13 +164,13 @@ All logs go to `logs/framework/` in the project root:
 
 | User Says | Tool / Command |
 |----------|---------------|
-| "Is StringRay working?" | `strray_health()` or `/strray status` |
-| "Check these files before I commit" | `strray_validate(files=[...], operation="commit")` |
-| "Is this code codex compliant?" | `strray_codex_check(code=..., operation="create")` |
-| "Set up git hooks" | `strray_hooks(action="install")` |
-| "What hooks are installed?" | `strray_hooks(action="status")` |
-| "Show session stats" | `/strray stats` |
-| "Why is the bridge failing?" | Check `strray_health()` → if `framework: "not_loaded"`, verify `dist/` symlink |
+| "Is 0xRay working?" | `xray_health()` or `/xray status` |
+| "Check these files before I commit" | `xray_validate(files=[...], operation="commit")` |
+| "Is this code codex compliant?" | `xray_codex_check(code=..., operation="create")` |
+| "Set up git hooks" | `xray_hooks(action="install")` |
+| "What hooks are installed?" | `xray_hooks(action="status")` |
+| "Show session stats" | `/xray stats` |
+| "Why is the bridge failing?" | Check `xray_health()` → if `framework: "not_loaded"`, verify `dist/` symlink |
 
 ## Bridge Commands (internal)
 
@@ -188,8 +188,8 @@ These are called by the Python tools via `bridge.mjs`, not directly by the LLM:
 
 Bridge can be invoked directly for debugging:
 ```bash
-echo '{"command":"health"}' | node ~/.hermes/plugins/strray-hermes/bridge.mjs
-node ~/.hermes/plugins/strray-hermes/bridge.mjs health --cwd /path/to/project
+echo '{"command":"health"}' | node ~/.hermes/plugins/xray-hermes/bridge.mjs
+node ~/.hermes/plugins/xray-hermes/bridge.mjs health --cwd /path/to/project
 ```
 
 ## Relationship to MCP Servers
@@ -198,15 +198,15 @@ The plugin and MCP servers are complementary:
 - **Plugin tools** = offline-first, always available, lightweight (validate, codex check, health, hooks)
 - **MCP servers** = deeper analysis requiring running Node.js (lint, security scan, architecture assessment, orchestration, codebase search)
 
-The plugin's pre_tool_call hook nudges when an MCP alternative exists (e.g., "use mcp_strray_lint_lint instead of raw eslint"). This is advisory, not blocking.
+The plugin's pre_tool_call hook nudges when an MCP alternative exists (e.g., "use mcp_xray_lint_lint instead of raw eslint"). This is advisory, not blocking.
 
 ## Pitfalls
 
 - Plugin requires restart after install/edit: Hermes loads plugins once at session start.
 - Bridge needs `dist/` symlink: The bridge loads compiled `.js` from `dist/` → `node_modules/0xray/dist/`. If the symlink breaks, bridge returns `framework: "not_loaded"`.
-- `strray_codex_check` without `code` param returns health, not a codex check. Pass `code` for actual validation.
+- `xray_codex_check` without `code` param returns health, not a codex check. Pass `code` for actual validation.
 - CLI fallback requires `npx 0xray` in PATH. If bridge fails and CLI isn't available, tools return errors.
 - Quality gate blocks are logged but NOT enforced (advisory). The tool returns violations; the agent decides what to do.
-- Git hooks use symlinks from `.git/hooks/` → `hooks/`. If the `hooks/` directory doesn't exist in the project, `strray_hooks(action="install")` skips those hooks.
-- Project root detection walks up from CWD looking for `node_modules/0xray`, `.opencode/strray/features.json`, or `package.json`. Override with `STRRAY_PROJECT_ROOT` env var.
+- Git hooks use symlinks from `.git/hooks/` → `hooks/`. If the `hooks/` directory doesn't exist in the project, `xray_hooks(action="install")` skips those hooks.
+- Project root detection walks up from CWD looking for `node_modules/0xray`, `.opencode/xray/features.json`, or `package.json`. Override with `XRAY_PROJECT_ROOT` env var.
 - `logs/framework/` is created automatically. Never breaks the agent if permissions fail.

package/src/skills/storyteller/SKILL.md

@@ -96,7 +96,7 @@ codex_terms: [5, 7, 32]  # Related Codex term numbers
 ```markdown
 ## What Next?
 
-- Related Codex terms: [codex.json](../../.opencode/strray/codex.json)
+- Related Codex terms: [codex.json](../../.opencode/xray/codex.json)
 - Next story to write: [suggestion]
 ```