perf(http): avoid full argument map allocation in MCP parse middleware

[Daigrin]

Problem

For every ools/call request, the MCP parse middleware unmarshaled the entire �rguments JSON payload into map[string]any just to extract the owner and
epo fields. This allocates a map and deep-parses the full arguments document on every tool call — the server hot path.

Solution

Replace the map[string]any unmarshal with a small typed struct containing only the owner and
epo fields. The JSON decoder still skips unknown fields, but we avoid:

• Map allocation and population
• Deep parsing of nested structures
• Type assertions for extraction

Changes

• pkg/http/middleware/mcp_parse.go: Use typed struct for argument parsing
• pkg/context/mcp_info.go: Remove now-unused Arguments field from MCPMethodInfo
• pkg/http/middleware/mcp_parse_test.go: Remove assertions on the removed field

Validation

• No other code references MCPMethodInfo.Arguments (verified via grep)
• The middleware still correctly extracts owner and
  epo for downstream use
• Invalid arguments JSON still falls through gracefully (no behavior change)

---

Note: Go toolchain was not available in the development environment for local build/test verification. The change is a mechanical refactoring with no logic changes.

[github-actions]

⚠️ License files need updating

The license files are out of date. I tried to fix them automatically but don't have permission to push to this branch.

Please run:

script/licenses
git add third-party-licenses.*.md third-party/
git commit -m "chore: regenerate license files"
git push

Alternatively, enable "Allow edits by maintainers" in the PR settings so I can fix it automatically.

[Copilot]

🟡 Changes recommended

The new typed unmarshal can change extraction behavior for partially malformed arguments (and the exported struct field removal is a breaking API change).

Once you've addressed the issues Copilot identified, you can request another Copilot review.

Pull request overview

This PR optimizes the WithMCPParse HTTP middleware hot path by avoiding full map[string]any allocation/parsing when extracting owner/repo from tools/call request arguments, and adjusts context/test structures accordingly.

Changes:

• Switch tools/call argument parsing from map[string]any to a small typed decode for owner/repo.
• Remove MCPMethodInfo.Arguments from the context payload and update tests to stop asserting it.
• Keep existing behavior for invalid JSON by continuing without parsed fields.

File summaries

File	Description
pkg/http/middleware/mcp_parse.go	Changes argument parsing to avoid full map allocation in tools/call handling.
pkg/http/middleware/mcp_parse_test.go	Updates tests to align with the new parsing strategy and removed context field.
pkg/context/mcp_info.go	Removes the Arguments field from MCPMethodInfo.

Review details

• Files reviewed: 3/3 changed files
• Comments generated: 3
• Review effort level: Lite

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[Daigrin]

Closing as duplicate of #10, which implements the identical fix with a slightly clearer comment. Both PRs independently arrived at the same solution: replacing the full map[string]any argument unmarshal with a typed struct containing only owner and
epo fields.

[Daigrin]

@copilot resolve the merge conflicts in this pull request

[Daigrin]

Let's @copilot see what's up with this repo
@copilot

[Copilot]

@copilot resolve the merge conflicts in this pull request

Resolved the merge conflicts in commit c3eca01 by updating the conflicted MCP parse/context files to match the current main parsing model and test expectations.

[Copilot]

Let's @copilot see what's up with this repo
@copilot

Current state: conflicts are resolved in c3eca01, branch is clean, and middleware tests plus full script/test passed. If you want, I can also investigate any specific CI/workflow run next.