Skip to content

refactor(runtime-host): unify tool ceiling projection - #3620

Open
Astro-Han wants to merge 1 commit into
apache:mainfrom
Astro-Han:refactor/tool-ceiling-single-authority
Open

refactor(runtime-host): unify tool ceiling projection#3620
Astro-Han wants to merge 1 commit into
apache:mainfrom
Astro-Han:refactor/tool-ceiling-single-authority

Conversation

@Astro-Han

Copy link
Copy Markdown
Contributor

Summary

Unify Interactive Run tool ceilings around concrete MakaTool[] bindings.

Hosted execution profiles now own both tool selection and schema projection. This removes the parallel boundToolNames composer input while preserving the exact child ceiling and the headless-coding-v1 tool contract.

Refs #1099

Verification

  • npm --workspace @maka/runtime-host run build
  • node --test packages/runtime-host/dist/__tests__/hosted-execution-tool-profile.test.js
  • focused execution-model-composition.test.js cases for bound ceilings, Client Capabilities, and the headless coding profile
  • npm run format:check

The complete execution-model-composition.test.js file was also run before the change: 23/24 cases passed; the unrelated implementation-child patch case failed its completion assertion. The focused affected cases passed before and after the change.

AI use

  • No generative tool made a substantive contribution
  • Generative tooling made a substantive contribution

Tool(s) and scope: Maka audited the duplicate ceiling representations, implemented the refactor, updated tests, and ran focused validation.

Checklist

  • Tests cover the change and fail without it
  • Lint, format, typecheck and the affected suites pass locally

Does this PR entail a change in behavior?

  • Yes — described under Summary above
  • No

Make hosted execution profiles own both tool selection and schema projection so Interactive Run composition has one concrete bound-tools ceiling instead of parallel object and name inputs.

Generated-by: Maka
@Astro-Han
Astro-Han marked this pull request as ready for review August 23, 2026 14:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant