fix(module): prefer structuredContent in code mode dispatch

[Mat4m0]

The problem

structuredContent silently dropped in code mode dispatch (data loss)

When a tool handler returns structuredContent (the MCP spec's typed data channel), the dispatch function in buildDispatchFunctions() ignores it entirely and falls through to extracting text from result.content[].text. This silently loses IDs, booleans, and nested objects — the agent receives a stringified summary instead of the actual structured data.

This breaks any workflow that chains operations using returned data:

// Tool returns: { structuredContent: { ok: true, data: { id: "abc123" } } }
const created = await codemode.create_item({ title: "Test" });

// Expected: created.data.id === "abc123"
// Actual:   created === "Created item 'Test' successfully" (text fallback)
//           created.data is undefined → follow-up call fails

Root cause

buildDispatchFunctions() went straight to result.content text extraction without ever checking result.structuredContent.

Solution

Added a structuredContent check before the text extraction fallback:

// Prefer structuredContent when available (preserves typed data)
if (result.structuredContent != null) {
  return result.structuredContent
}

When structuredContent is present, it is returned directly — preserving typed fields (booleans, numbers, nested objects, IDs) for use in sandbox code. When absent, the existing content[].text extraction continues to work unchanged.

Files changed

File	What changed
index.ts	buildDispatchFunctions(): check result.structuredContent before text extraction
codemode.test.ts	5 new tests covering structuredContent dispatch

Test coverage

5 new tests in test/codemode.test.ts:

• structuredContent preferred over text content — verifies the structured object is returned, not the text summary
• typed fields preserved — booleans, numbers, nested objects pass through intact
• operation chaining — create → use returned ID → update works end-to-end
• text fallback unchanged — tools without structuredContent still work via content[].text
• structuredContent-only result — handles results with no content array

All 150 tests pass (20 test files).

Test plan

• pnpm test passes (150/150)
• Tool returning structuredContent with an ID → sandbox code receives the ID, uses it in a follow-up call
• Tool returning only content[].text (no structuredContent) → existing behavior unchanged

AI tools used

• Claude Opus 4.6

[vercel]

@Mat4m0 is attempting to deploy a commit to the Nuxt Team on Vercel.

A member of the Team first needs to authorize it.

[github-actions]

Thank you for following the naming conventions! 🙏

[pkg-pr-new]

npm i https://pkg.pr.new/@nuxtjs/mcp-toolkit@207

commit: 736a70c