unity-open-mcp 0.5.0 → 0.6.1

package/dist/live-client.d.ts

@@ -91,7 +91,56 @@ export declare class LiveClient implements Router {
     private handleToolCall;
     private handleRunTests;
     private pollTestResults;
+    /**
+     * POST a tool call to the bridge and shape the response. Decomposed in
+     * M28-refactoring Plan 3 (T3.3) into named steps so retry, compile-wait,
+     * transient-offline handling, and result shaping are independently readable.
+     *
+     * Pipeline:
+     *   1. {@link postToolFetch} — POST with a timeout floored above the bridge's
+     *      own default wait, handling 503-compile-retry and non-OK HTTP.
+     *   2. {@link shapeToolResult} — parse the body and dispatch mutation-envelope
+     *      vs direct-body vs inline-image vs reload/corruption outcomes.
+     *   3. On a transient fetch failure, {@link handlePostFailure} classifies +
+     *      recovers (re-syncing the endpoint, waiting out a reload, or surfacing
+     *      the structured offline/dead-bridge error) and re-POSTs only when safe.
+     *
+     * The retry/compile contract is unchanged from the former monolithic body.
+     */
     private postTool;
+    /**
+     * Step 1 of {@link postTool}: perform the HTTP POST with the timeout floor,
+     * then handle 503-compile-retry and non-OK HTTP. Returns either a shaped
+     * {@link CallToolResult} (handed straight back by postTool) or a sentinel
+     * `{ _repostAfterCompile: true }` signaling a clean compile settle that
+     * should re-POST without 503 retry. Throws on transient fetch failure so the
+     * caller's catch runs {@link handlePostFailure}.
+     */
+    private postToolFetch;
+    /**
+     * Step 2 of {@link postTool}: parse the bridge response body and shape it into
+     * a {@link CallToolResult}. Handles the four response outcomes:
+     *   - inline-image unwrap (capture_inline → MCP image block + metadata),
+     *   - mutation envelope (derive isError from mutation.success),
+     *   - compile-reload empty body (triggered_reload — likely-success domain
+     *     reload tore down the socket mid-response),
+     *   - direct body (verbatim, isError when a top-level error field is present),
+     *   - unparsable body (bridge_response_unparsable corruption error).
+     */
+    private shapeToolResult;
+    /**
+     * Step 3 of {@link postTool}: classify + recover from a transient POST
+     * failure (ECONNREFUSED / timeout during a domain reload). Re-syncs the cached
+     * endpoint from the lock first (so a Unity restart self-heals), waits out a
+     * reload, and re-POSTs ONLY when safe (endpoint changed during recovery, or a
+     * genuine connection failure where no bytes reached the server).
+     *
+     * Re-POST discipline (specs/feedback.md entry 4A — duplicate side-effects):
+     * when the endpoint is unchanged the same live bridge is still processing —
+     * or has queued — the original POST's Work; re-POSTing would run the mutation
+     * a second time. In that case surface the timeout instead of retrying.
+     */
+    private handlePostFailure;
     private ensureReady;
     /**
      * M20 Plan 4-5 / T-fix-2 — classify a transient /ping or tool-POST failure