Skip to content

tip: bound Meta/Muse tool schema nesting (#50320) - #173

Open
kvnloo wants to merge 1 commit into
devfrom
tip/50320-bound-tool-schema-nesting
Open

kvnloo wants to merge 1 commit into
devfrom
tip/50320-bound-tool-schema-nesting

Conversation

@kvnloo

@kvnloo kvnloo commented Sep 27, 2026

Copy link
Copy Markdown
Owner

Tip leaf (fork-only) — CLEAN

Maps to work-order issue #172. Upstream origin anomalyco#50320 (not touched / not promoted).

What: Bound Meta/Muse tool schema nesting depth so deeply nested schemas are truncated safely.

Commit: 3bbf1f2a726d75969f4f9e1a588c873966a55131
Origin tip SHA: 479881dc40ea5543154a19a4bd89efe1b0a69746

Proof: fail→pass on ProviderTransform.schema - meta nesting depth tip tests (GREEN 8 / NEG 7 fail / RESTORE 8).

github_writes_origin: 0. Codex promote parked.

Meta's Model API rejects tool schemas nested deeper than 10 levels and fails
the whole request instead of the offending tool, so one deep MCP tool (the
Vercel MCP server publishes twelve) breaks every request for Muse Spark, both
on the `meta` provider and through the opencode gateways.

Drop the members that would nest past the limit for Meta/Muse models. Every
other keyword stays on the node, so a lowered tool keeps its shape and stays
callable instead of failing the request.
@kvnloo kvnloo added the grok bot Posted by Grok Bot OSS review dump label Sep 27, 2026
@github-actions

Copy link
Copy Markdown

This PR doesn't fully meet our contributing guidelines and PR template.

What needs to be fixed:

  • PR description is missing required template sections. Please use the PR template.

Please edit this PR description to address the above within 2 hours, or it will be automatically closed.

If you believe this was flagged incorrectly, please let a maintainer know.

@github-actions

Copy link
Copy Markdown

Hey! Your PR title tip: bound Meta/Muse tool schema nesting (#50320) doesn't follow conventional commit format.

Please update it to start with one of:

  • feat: or feat(scope): new feature
  • fix: or fix(scope): bug fix
  • docs: or docs(scope): documentation changes
  • chore: or chore(scope): maintenance tasks
  • refactor: or refactor(scope): code refactoring
  • test: or test(scope): adding or updating tests

Where scope is the package name (e.g., app, desktop, opencode).

See CONTRIBUTING.md for details.

kvnloo commented Sep 29, 2026

Copy link
Copy Markdown
Owner Author

READY_UPSTREAM

Exact-head gate passed:

Post the evidence upstream via local gh/Hermes; do not open a duplicate PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

grok bot Posted by Grok Bot OSS review dump needs:title

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants