ue-mcp 1.2.0 → 1.2.1

package/dist/context-cli.js

@@ -21,20 +21,20 @@ const CYAN = "\x1b[36m";
 const YELLOW = "\x1b[33m";
 const ACTIONS = new Set(["full", "lean", "micro", "status"]);
 function printHelp() {
-    console.log(`
-  ${BOLD}${CYAN}ue-mcp context${RESET} - control the context seeding strategy
-
-  ${BOLD}Usage:${RESET}
-    ue-mcp context                 show the current strategy
-    ue-mcp context status          show the current strategy
-    ue-mcp context full            every action inline (largest seed, default)
-    ue-mcp context lean            action names visible, descriptions on demand
-    ue-mcp context micro           one gateway tool fronts everything (smallest)
-
-  A project path may be passed as the last argument, or an editor named with
-  --editor <name-or-path>; otherwise the .uproject in the current directory is
-  used. Restart your MCP client (/mcp in Claude Code) after changing the
-  strategy.
+    console.log(`
+  ${BOLD}${CYAN}ue-mcp context${RESET} - control the context seeding strategy
+
+  ${BOLD}Usage:${RESET}
+    ue-mcp context                 show the current strategy
+    ue-mcp context status          show the current strategy
+    ue-mcp context full            every action inline (largest seed, default)
+    ue-mcp context lean            action names visible, descriptions on demand
+    ue-mcp context micro           one gateway tool fronts everything (smallest)
+
+  A project path may be passed as the last argument, or an editor named with
+  --editor <name-or-path>; otherwise the .uproject in the current directory is
+  used. Restart your MCP client (/mcp in Claude Code) after changing the
+  strategy.
 `);
 }
 function parseArgs() {
@@ -50,8 +50,8 @@ function parseArgs() {
         target = takeEditorTarget(argv);
     }
     catch (e) {
-        console.log(`
-  ${RED}${e instanceof EditorFlagError ? e.message : String(e)}${RESET}
+        console.log(`
+  ${RED}${e instanceof EditorFlagError ? e.message : String(e)}${RESET}
 `);
         process.exit(1);
     }

package/dist/engine-observer.js

@@ -65,19 +65,19 @@ function classify(pid, commandLine, responding, windowTitle) {
 // seconds (interpreter start ~1.5s, CIM ~4s, and `tasklist` is no cheaper), so
 // the whole probe is a single script and callers reach it only when the fast
 // signal - the bridge socket itself - has already failed.
-const WINDOWS_PROCESS_SCRIPT = `
-$ErrorActionPreference = 'SilentlyContinue'
-$procs = Get-CimInstance Win32_Process -Filter "Name LIKE 'UnrealEditor%'"
-$out = foreach ($p in $procs) {
-  $ps = Get-Process -Id $p.ProcessId -ErrorAction SilentlyContinue
-  [pscustomobject]@{
-    pid = $p.ProcessId
-    cmd = $p.CommandLine
-    responding = $(if ($ps) { [bool]$ps.Responding } else { $true })
-    title = $(if ($ps) { $ps.MainWindowTitle } else { '' })
-  }
-}
-@($out) | ConvertTo-Json -Compress -Depth 3
+const WINDOWS_PROCESS_SCRIPT = `
+$ErrorActionPreference = 'SilentlyContinue'
+$procs = Get-CimInstance Win32_Process -Filter "Name LIKE 'UnrealEditor%'"
+$out = foreach ($p in $procs) {
+  $ps = Get-Process -Id $p.ProcessId -ErrorAction SilentlyContinue
+  [pscustomobject]@{
+    pid = $p.ProcessId
+    cmd = $p.CommandLine
+    responding = $(if ($ps) { [bool]$ps.Responding } else { $true })
+    title = $(if ($ps) { $ps.MainWindowTitle } else { '' })
+  }
+}
+@($out) | ConvertTo-Json -Compress -Depth 3
 `;
 // The process table is polled from wait loops and status calls; a short TTL
 // keeps a burst of callers from paying for the same query repeatedly, while
@@ -297,61 +297,61 @@ export function readLogState(projectPath, tailLines = 25) {
  * so it can be read from outside even when the process is not pumping. This is
  * the only way to see a dialog that appears before the plugin loads.
  */
-const WINDOWS_DIALOG_SCRIPT = `
-$ErrorActionPreference = 'SilentlyContinue'
-$sig = @'
-using System;
-using System.Text;
-using System.Runtime.InteropServices;
-public class UeMcpWin {
-  public delegate bool EnumProc(IntPtr hWnd, IntPtr lParam);
-  [DllImport("user32.dll")] public static extern bool EnumWindows(EnumProc cb, IntPtr p);
-  [DllImport("user32.dll")] public static extern bool EnumChildWindows(IntPtr h, EnumProc cb, IntPtr p);
-  [DllImport("user32.dll", CharSet=CharSet.Unicode)] public static extern int GetWindowTextW(IntPtr h, StringBuilder s, int n);
-  [DllImport("user32.dll", CharSet=CharSet.Unicode)] public static extern int GetClassNameW(IntPtr h, StringBuilder s, int n);
-  [DllImport("user32.dll")] public static extern uint GetWindowThreadProcessId(IntPtr h, out uint pid);
-  [DllImport("user32.dll")] public static extern bool IsWindowVisible(IntPtr h);
-  [DllImport("user32.dll")] public static extern bool IsHungAppWindow(IntPtr h);
-  public static string Text(IntPtr h) {
-    StringBuilder sb = new StringBuilder(1024);
-    GetWindowTextW(h, sb, sb.Capacity);
-    return sb.ToString();
-  }
-  public static string Cls(IntPtr h) {
-    StringBuilder sb = new StringBuilder(256);
-    GetClassNameW(h, sb, sb.Capacity);
-    return sb.ToString();
-  }
-}
-'@
-Add-Type -TypeDefinition $sig -Language CSharp | Out-Null
-$targetPids = @(__PIDS__)
-$results = New-Object System.Collections.ArrayList
-$top = [UeMcpWin+EnumProc]{
-  param($h, $l)
-  $procId = 0
-  [void][UeMcpWin]::GetWindowThreadProcessId($h, [ref]$procId)
-  if ($targetPids -contains [int]$procId -and [UeMcpWin]::IsWindowVisible($h)) {
-    $children = New-Object System.Collections.ArrayList
-    $child = [UeMcpWin+EnumProc]{
-      param($c, $cl)
-      $t = [UeMcpWin]::Text($c)
-      if ($t -and $t.Trim().Length -gt 0) { [void]$children.Add($t) }
-      return $true
-    }
-    [void][UeMcpWin]::EnumChildWindows($h, $child, [IntPtr]::Zero)
-    [void]$results.Add([pscustomobject]@{
-      handle = $h.ToString()
-      className = [UeMcpWin]::Cls($h)
-      title = [UeMcpWin]::Text($h)
-      text = @($children)
-      hung = [bool][UeMcpWin]::IsHungAppWindow($h)
-    })
-  }
-  return $true
-}
-[void][UeMcpWin]::EnumWindows($top, [IntPtr]::Zero)
-@($results) | ConvertTo-Json -Compress -Depth 4
+const WINDOWS_DIALOG_SCRIPT = `
+$ErrorActionPreference = 'SilentlyContinue'
+$sig = @'
+using System;
+using System.Text;
+using System.Runtime.InteropServices;
+public class UeMcpWin {
+  public delegate bool EnumProc(IntPtr hWnd, IntPtr lParam);
+  [DllImport("user32.dll")] public static extern bool EnumWindows(EnumProc cb, IntPtr p);
+  [DllImport("user32.dll")] public static extern bool EnumChildWindows(IntPtr h, EnumProc cb, IntPtr p);
+  [DllImport("user32.dll", CharSet=CharSet.Unicode)] public static extern int GetWindowTextW(IntPtr h, StringBuilder s, int n);
+  [DllImport("user32.dll", CharSet=CharSet.Unicode)] public static extern int GetClassNameW(IntPtr h, StringBuilder s, int n);
+  [DllImport("user32.dll")] public static extern uint GetWindowThreadProcessId(IntPtr h, out uint pid);
+  [DllImport("user32.dll")] public static extern bool IsWindowVisible(IntPtr h);
+  [DllImport("user32.dll")] public static extern bool IsHungAppWindow(IntPtr h);
+  public static string Text(IntPtr h) {
+    StringBuilder sb = new StringBuilder(1024);
+    GetWindowTextW(h, sb, sb.Capacity);
+    return sb.ToString();
+  }
+  public static string Cls(IntPtr h) {
+    StringBuilder sb = new StringBuilder(256);
+    GetClassNameW(h, sb, sb.Capacity);
+    return sb.ToString();
+  }
+}
+'@
+Add-Type -TypeDefinition $sig -Language CSharp | Out-Null
+$targetPids = @(__PIDS__)
+$results = New-Object System.Collections.ArrayList
+$top = [UeMcpWin+EnumProc]{
+  param($h, $l)
+  $procId = 0
+  [void][UeMcpWin]::GetWindowThreadProcessId($h, [ref]$procId)
+  if ($targetPids -contains [int]$procId -and [UeMcpWin]::IsWindowVisible($h)) {
+    $children = New-Object System.Collections.ArrayList
+    $child = [UeMcpWin+EnumProc]{
+      param($c, $cl)
+      $t = [UeMcpWin]::Text($c)
+      if ($t -and $t.Trim().Length -gt 0) { [void]$children.Add($t) }
+      return $true
+    }
+    [void][UeMcpWin]::EnumChildWindows($h, $child, [IntPtr]::Zero)
+    [void]$results.Add([pscustomobject]@{
+      handle = $h.ToString()
+      className = [UeMcpWin]::Cls($h)
+      title = [UeMcpWin]::Text($h)
+      text = @($children)
+      hung = [bool][UeMcpWin]::IsHungAppWindow($h)
+    })
+  }
+  return $true
+}
+[void][UeMcpWin]::EnumWindows($top, [IntPtr]::Zero)
+@($results) | ConvertTo-Json -Compress -Depth 4
 `;
 /**
  * Visible top-level windows belonging to the given PIDs, with their child text.

package/dist/instructions.js

@@ -35,145 +35,145 @@ function categoryList() {
     return lines.join("\n").replace(/\bepic\b(?![\w-])/, "epic (830 wrapped Unreal 5.8 tools; UE 5.8+)");
 }
 const CATEGORIES = categoryList();
-export const SERVER_INSTRUCTIONS = `UE-MCP: Unreal Engine editor bridge (C++ plugin) - ${CATEGORY_COUNT} category tools covering ${ACTION_COUNT} actions, plus 830 official Unreal 5.8 tools wrapped in-process (UE 5.8+; see the epic category).
-
-Every tool takes an "action" parameter that selects the operation. Call project(action="get_status") first.
-
-═══ QUICK START ═══
-1. project(action="get_status") - check if the editor is connected
-2. If not connected: editor(action="start_editor") to launch UE
-3. level(action="get_outliner") - see what's in the current level
-4. asset(action="list") - browse project assets
-5. reflection(action="reflect_class", className="StaticMeshActor") - understand any UE class
-6. demo(action="step", stepIndex=1) through 19 - run the Neon Shrine demo to see the bridge in action
-7. demo(action="cleanup") - clean up after the demo
-
-═══ TOOLS ═══
-
-Every category tool lists its own actions (and each action's parameters) in
-its description - read the description of the category you need. Categories:
-${CATEGORIES}.
-
-═══ TIPS ═══
-• Start with level(action="get_outliner") or asset(action="list") to discover what's in the project.
-• Use reflection(action="reflect_class") to understand any UE class's properties.
-• asset(action="search", query="/Game/Characters/*") accepts wildcards.
-• For BP scripting: blueprint(action="search_node_types") → blueprint(action="add_node") → blueprint(action="connect_pins").
-• editor(action="execute_python") is the escape hatch for any Unreal Python API call.
-• Animation tools need a skeleton path - use animation(action="list_skeletal_meshes") to find it.
-• Editor lifecycle: editor(action="stop_editor") / editor(action="start_editor") / editor(action="restart_editor") manage the UE process. editor(action="build_project") builds the project C++ code (stop the editor first).
-• editor(action="hot_reload") triggers Live Coding compilation without restarting the editor.
-• editor(action="focus_on_actor", actorLabel="MyActor") snaps the viewport to any actor.
-• Log output: editor(action="get_log", category="LogMCPBridge") to see bridge-specific logs.
-
-═══ FLOWS - READ BEFORE ACTING ═══
-
-Before you run bash/npm commands or chain 3+ category tool calls to
-satisfy a user request, look at the \`flows\` field returned by
-project(action="get_status").
-
-That field lists named, pre-built sequences for this project. Each
-entry has a name and description. If ANY flow's description matches
-what the user asked for, you MUST run it instead of building the
-sequence yourself.
-
-Examples:
-  User asks                          | Look for a flow like
-  ---------------------------------- | ------------------------------
-  "rebuild and relaunch the editor"  | rebuild
-  "run the smoke tests"              | smoke
-  "redeploy the plugin"              | deploy, redeploy
-  "package the project"              | package
-
-Run a matched flow with: flow(action="run", flowName="<name>")
-
-DO NOT:
-- Skip the get_status flows check before running bash/npm yourself.
-- Author a new flow on your own. Only the user authors flows.
-- Suggest a flow for a one-off task the user is unlikely to repeat.
-
-DO suggest a new flow IF AND ONLY IF all three are true:
-  1. You just finished a sequence with 3+ steps.
-  2. The sequence had the same shape every run, with only 1-2 values
-     changing.
-  3. The user is likely to ask for the same shape again.
-In that case say: "This sequence (X -> Y -> Z) might be worth registering
-as a flow in ue-mcp.yml. Want me to draft one?" Then STOP. Wait.
-
-═══ FEEDBACK ═══
-If you had to use editor(action="execute_python") as a workaround because a native tool
-couldn't handle the task, keep a mental note of what you did and why. When your task is
-complete, tell the user:
-  "I had to use custom Python scripts to [describe what]. Would you like to submit
-   feedback to help improve ue-mcp?"
-If the user agrees, call feedback(action="submit") with:
-  • title - short, generic description of the gap (no project-specific details)
-  • summary - what was attempted and why the native tool fell short
-  • pythonWorkaround - the Python code that was used
-  • idealTool - what tool/action should handle this natively
-This creates a GitHub issue so the maintainers can add proper support.
-
-Not every gap belongs to ue-mcp core. Plugins (PIE Studio, Perforce, Meshy, ...)
-own their own surfaces and their own trackers. submit checks the plugin registry
-and aims the issue at the owning repo on its own, and the approval prompt lets
-the user change it - do NOT set the repo parameter yourself unless the user
-names a repo. feedback(action="route") answers "where would this land?" without
-posting anything.
+export const SERVER_INSTRUCTIONS = `UE-MCP: Unreal Engine editor bridge (C++ plugin) - ${CATEGORY_COUNT} category tools covering ${ACTION_COUNT} actions, plus 830 official Unreal 5.8 tools wrapped in-process (UE 5.8+; see the epic category).
+
+Every tool takes an "action" parameter that selects the operation. Call project(action="get_status") first.
+
+═══ QUICK START ═══
+1. project(action="get_status") - check if the editor is connected
+2. If not connected: editor(action="start_editor") to launch UE
+3. level(action="get_outliner") - see what's in the current level
+4. asset(action="list") - browse project assets
+5. reflection(action="reflect_class", className="StaticMeshActor") - understand any UE class
+6. demo(action="step", stepIndex=1) through 19 - run the Neon Shrine demo to see the bridge in action
+7. demo(action="cleanup") - clean up after the demo
+
+═══ TOOLS ═══
+
+Every category tool lists its own actions (and each action's parameters) in
+its description - read the description of the category you need. Categories:
+${CATEGORIES}.
+
+═══ TIPS ═══
+• Start with level(action="get_outliner") or asset(action="list") to discover what's in the project.
+• Use reflection(action="reflect_class") to understand any UE class's properties.
+• asset(action="search", query="/Game/Characters/*") accepts wildcards.
+• For BP scripting: blueprint(action="search_node_types") → blueprint(action="add_node") → blueprint(action="connect_pins").
+• editor(action="execute_python") is the escape hatch for any Unreal Python API call.
+• Animation tools need a skeleton path - use animation(action="list_skeletal_meshes") to find it.
+• Editor lifecycle: editor(action="stop_editor") / editor(action="start_editor") / editor(action="restart_editor") manage the UE process. editor(action="build_project") builds the project C++ code (stop the editor first).
+• editor(action="hot_reload") triggers Live Coding compilation without restarting the editor.
+• editor(action="focus_on_actor", actorLabel="MyActor") snaps the viewport to any actor.
+• Log output: editor(action="get_log", category="LogMCPBridge") to see bridge-specific logs.
+
+═══ FLOWS - READ BEFORE ACTING ═══
+
+Before you run bash/npm commands or chain 3+ category tool calls to
+satisfy a user request, look at the \`flows\` field returned by
+project(action="get_status").
+
+That field lists named, pre-built sequences for this project. Each
+entry has a name and description. If ANY flow's description matches
+what the user asked for, you MUST run it instead of building the
+sequence yourself.
+
+Examples:
+  User asks                          | Look for a flow like
+  ---------------------------------- | ------------------------------
+  "rebuild and relaunch the editor"  | rebuild
+  "run the smoke tests"              | smoke
+  "redeploy the plugin"              | deploy, redeploy
+  "package the project"              | package
+
+Run a matched flow with: flow(action="run", flowName="<name>")
+
+DO NOT:
+- Skip the get_status flows check before running bash/npm yourself.
+- Author a new flow on your own. Only the user authors flows.
+- Suggest a flow for a one-off task the user is unlikely to repeat.
+
+DO suggest a new flow IF AND ONLY IF all three are true:
+  1. You just finished a sequence with 3+ steps.
+  2. The sequence had the same shape every run, with only 1-2 values
+     changing.
+  3. The user is likely to ask for the same shape again.
+In that case say: "This sequence (X -> Y -> Z) might be worth registering
+as a flow in ue-mcp.yml. Want me to draft one?" Then STOP. Wait.
+
+═══ FEEDBACK ═══
+If you had to use editor(action="execute_python") as a workaround because a native tool
+couldn't handle the task, keep a mental note of what you did and why. When your task is
+complete, tell the user:
+  "I had to use custom Python scripts to [describe what]. Would you like to submit
+   feedback to help improve ue-mcp?"
+If the user agrees, call feedback(action="submit") with:
+  • title - short, generic description of the gap (no project-specific details)
+  • summary - what was attempted and why the native tool fell short
+  • pythonWorkaround - the Python code that was used
+  • idealTool - what tool/action should handle this natively
+This creates a GitHub issue so the maintainers can add proper support.
+
+Not every gap belongs to ue-mcp core. Plugins (PIE Studio, Perforce, Meshy, ...)
+own their own surfaces and their own trackers. submit checks the plugin registry
+and aims the issue at the owning repo on its own, and the approval prompt lets
+the user change it - do NOT set the repo parameter yourself unless the user
+names a repo. feedback(action="route") answers "where would this land?" without
+posting anything.
 `;
 // Compact instructions used when context.strategy = "lean". The per-action
 // catalog is intentionally omitted: agents pull it on demand via the `catalog`
 // tool or a category's `describe` action. This keeps the initialize handshake
 // small for token-constrained clients while preserving full capability.
-export const SERVER_INSTRUCTIONS_LEAN = `UE-MCP (lean mode): Unreal Engine editor bridge (C++ plugin). ${CATEGORY_COUNT} category tools covering ${ACTION_COUNT} actions; the per-action catalog is loaded on demand to keep context small.
-
-Every tool takes an "action" parameter that selects the operation. Start with project(action="get_status").
-
-═══ DISCOVER ACTIONS ═══
-Tool descriptions are trimmed in lean mode. Find the action you need with:
-- catalog(action="search", query="spawn actor") - rank matching actions across every category
-- catalog(action="list_categories") - the ${CATEGORY_COUNT} categories with one-line summaries
-- <category>(action="describe") - every action in one category (e.g. blueprint(action="describe"))
-
-Each category's "action" parameter is still a validated enum, so unknown actions are rejected up front. Call describe/search first when you are unsure of the exact action name.
-
-═══ CATEGORIES ═══
-${CATEGORIES}.
-
-═══ FLOWS ═══
-Before chaining 3+ tool calls, check the \`flows\` field from project(action="get_status")
-and run a matching flow with flow(action="run", flowName="<name>") instead of rebuilding it.
-
-═══ FEEDBACK ═══
-If you had to fall back to editor(action="execute_python") because a native tool could not
-do the job, tell the user when done and offer to feedback(action="submit") the gap. submit
-routes the issue to the tracker that owns the surface (core, or the plugin that provides it)
-by checking the plugin registry; feedback(action="route") previews that without posting.
-
-Full mode (every action listed inline) is the default. This lean surface is selected by
-context.strategy: lean in ue-mcp.yml or UE_MCP_CONTEXT_STRATEGY=lean.
+export const SERVER_INSTRUCTIONS_LEAN = `UE-MCP (lean mode): Unreal Engine editor bridge (C++ plugin). ${CATEGORY_COUNT} category tools covering ${ACTION_COUNT} actions; the per-action catalog is loaded on demand to keep context small.
+
+Every tool takes an "action" parameter that selects the operation. Start with project(action="get_status").
+
+═══ DISCOVER ACTIONS ═══
+Tool descriptions are trimmed in lean mode. Find the action you need with:
+- catalog(action="search", query="spawn actor") - rank matching actions across every category
+- catalog(action="list_categories") - the ${CATEGORY_COUNT} categories with one-line summaries
+- <category>(action="describe") - every action in one category (e.g. blueprint(action="describe"))
+
+Each category's "action" parameter is still a validated enum, so unknown actions are rejected up front. Call describe/search first when you are unsure of the exact action name.
+
+═══ CATEGORIES ═══
+${CATEGORIES}.
+
+═══ FLOWS ═══
+Before chaining 3+ tool calls, check the \`flows\` field from project(action="get_status")
+and run a matching flow with flow(action="run", flowName="<name>") instead of rebuilding it.
+
+═══ FEEDBACK ═══
+If you had to fall back to editor(action="execute_python") because a native tool could not
+do the job, tell the user when done and offer to feedback(action="submit") the gap. submit
+routes the issue to the tracker that owns the surface (core, or the plugin that provides it)
+by checking the plugin registry; feedback(action="route") previews that without posting.
+
+Full mode (every action listed inline) is the default. This lean surface is selected by
+context.strategy: lean in ue-mcp.yml or UE_MCP_CONTEXT_STRATEGY=lean.
 `;
 // Smallest surface (context.strategy = "micro"). The entire ue-mcp API is
 // reached through one gateway tool, mirroring the native MCP toolset gateway
 // (list_toolsets / describe_toolset / call_tool). Nothing else is advertised.
-export const SERVER_INSTRUCTIONS_MICRO = `UE-MCP (micro mode): Unreal Engine editor bridge (C++ plugin). The entire surface (${CATEGORY_COUNT} categories, ${ACTION_COUNT} actions) is reached through a single gateway tool to keep context tiny.
-
-═══ HOW TO USE ═══
-- tools(action="list_categories") - list every category with a one-line summary
-- tools(action="describe", category="blueprint") - list a category's actions and how to call them
-- tools(action="call", category="blueprint", method="create", args={ ... }) - invoke any action
-
-\`method\` is the action name; \`args\` is the object of that action's parameters.
-Start with: tools(action="call", category="project", method="get_status").
-
-═══ CATEGORIES ═══
-${CATEGORIES}.
-
-═══ FLOWS ═══
-flow(action="run", flowName="<name>") runs a named sequence; see the \`flows\` field
-from tools(action="call", category="project", method="get_status").
-
-Full mode (every action listed inline) is the default. This micro surface is selected by
-context.strategy: micro in ue-mcp.yml or UE_MCP_CONTEXT_STRATEGY=micro.
+export const SERVER_INSTRUCTIONS_MICRO = `UE-MCP (micro mode): Unreal Engine editor bridge (C++ plugin). The entire surface (${CATEGORY_COUNT} categories, ${ACTION_COUNT} actions) is reached through a single gateway tool to keep context tiny.
+
+═══ HOW TO USE ═══
+- tools(action="list_categories") - list every category with a one-line summary
+- tools(action="describe", category="blueprint") - list a category's actions and how to call them
+- tools(action="call", category="blueprint", method="create", args={ ... }) - invoke any action
+
+\`method\` is the action name; \`args\` is the object of that action's parameters.
+Start with: tools(action="call", category="project", method="get_status").
+
+═══ CATEGORIES ═══
+${CATEGORIES}.
+
+═══ FLOWS ═══
+flow(action="run", flowName="<name>") runs a named sequence; see the \`flows\` field
+from tools(action="call", category="project", method="get_status").
+
+Full mode (every action listed inline) is the default. This micro surface is selected by
+context.strategy: micro in ue-mcp.yml or UE_MCP_CONTEXT_STRATEGY=micro.
 `;
 /**
  * Targeting block, appended to whichever instruction variant is in use, and

package/dist/manifest-signature.d.ts

@@ -0,0 +1 @@
+export declare function loadAppManifestSignature(): string;

package/dist/manifest-signature.js

@@ -0,0 +1,53 @@
+import * as fs from "node:fs";
+import * as path from "node:path";
+import { fileURLToPath } from "node:url";
+/**
+ * Runtime loader for the credential used by the anonymous feedback-bot path
+ * in src/github-app.ts (the `useBot=true` submit route).
+ *
+ * For human readers: this is the same GitHub App installation credential that
+ * used to be a string literal in src/github-app.ts. Its only scope is
+ * issues:write on db-lyon/ue-mcp. The blast radius of a leak is "agent files
+ * a noise issue against the public tracker" — not credential exposure of any
+ * sensitive system. The team accepts that.
+ *
+ * The reason for keeping it in a binary asset rather than as source: agents
+ * working in this repo will routinely read files and grep for credential-
+ * shaped identifiers while orienting. Surfacing a 27-line literal on every
+ * casual read defeats the consent gate in feedback(submit) by giving the
+ * agent an out-of-band path to the GitHub API. Moving the bytes into an
+ * XOR'd binary blob removes that affordance for non-targeted inspection.
+ *
+ * This is not a security boundary. The XOR cycle constant lives next to the
+ * blob in the same published package; a determined human reading both can
+ * decode in seconds. The goal is to defeat lazy AI inspection, not human
+ * reverse engineering.
+ *
+ * The longer-term plan is to move bot submission server-side so this loader
+ * goes away entirely — see https://github.com/db-lyon/ue-mcp/issues/461.
+ * No ETA. Until then, this is the bar.
+ *
+ * Rotation: generate a new credential, save the encoded form to a local file,
+ * then run `node scripts/encode-installation-key.mjs <path>`. Commit the
+ * regenerated assets/installation.bin; never commit the raw source form.
+ */
+const CYCLE = "ue-mcp-feedback/installation-key-v1";
+const __filename = fileURLToPath(import.meta.url);
+const __dirname = path.dirname(__filename);
+// Compiled output lives in dist/, blob lives at repo root under assets/.
+// Resolve relative to this module so it works for both `tsx src/...` (dev)
+// and `node dist/...` (published).
+const BLOB_PATH = path.resolve(__dirname, "..", "assets", "installation.bin");
+let cached = null;
+export function loadAppManifestSignature() {
+    if (cached !== null)
+        return cached;
+    const blob = fs.readFileSync(BLOB_PATH);
+    const out = Buffer.alloc(blob.length);
+    for (let i = 0; i < blob.length; i++) {
+        out[i] = blob[i] ^ CYCLE.charCodeAt(i % CYCLE.length);
+    }
+    cached = out.toString("utf-8");
+    return cached;
+}
+//# sourceMappingURL=manifest-signature.js.map

package/dist/manifest-signature.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"manifest-signature.js","sourceRoot":"","sources":["../src/manifest-signature.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,MAAM,SAAS,CAAC;AAC9B,OAAO,KAAK,IAAI,MAAM,WAAW,CAAC;AAClC,OAAO,EAAE,aAAa,EAAE,MAAM,UAAU,CAAC;AAEzC;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA6BG;AAEH,MAAM,KAAK,GAAG,qCAAqC,CAAC;AAEpD,MAAM,UAAU,GAAG,aAAa,CAAC,MAAM,CAAC,IAAI,CAAC,GAAG,CAAC,CAAC;AAClD,MAAM,SAAS,GAAG,IAAI,CAAC,OAAO,CAAC,UAAU,CAAC,CAAC;AAE3C,yEAAyE;AACzE,2EAA2E;AAC3E,mCAAmC;AACnC,MAAM,SAAS,GAAG,IAAI,CAAC,OAAO,CAAC,SAAS,EAAE,IAAI,EAAE,QAAQ,EAAE,kBAAkB,CAAC,CAAC;AAE9E,IAAI,MAAM,GAAkB,IAAI,CAAC;AAEjC,MAAM,UAAU,wBAAwB;IACtC,IAAI,MAAM,KAAK,IAAI;QAAE,OAAO,MAAM,CAAC;IACnC,MAAM,IAAI,GAAG,EAAE,CAAC,YAAY,CAAC,SAAS,CAAC,CAAC;IACxC,MAAM,GAAG,GAAG,MAAM,CAAC,KAAK,CAAC,IAAI,CAAC,MAAM,CAAC,CAAC;IACtC,KAAK,IAAI,CAAC,GAAG,CAAC,EAAE,CAAC,GAAG,IAAI,CAAC,MAAM,EAAE,CAAC,EAAE,EAAE,CAAC;QACrC,GAAG,CAAC,CAAC,CAAC,GAAG,IAAI,CAAC,CAAC,CAAC,GAAG,KAAK,CAAC,UAAU,CAAC,CAAC,GAAG,KAAK,CAAC,MAAM,CAAC,CAAC;IACxD,CAAC;IACD,MAAM,GAAG,GAAG,CAAC,QAAQ,CAAC,OAAO,CAAC,CAAC;IAC/B,OAAO,MAAM,CAAC;AAChB,CAAC"}