fix(tutti): ignore composer permission UI defaults

[jomeswang]

Summary

• stop promoting Tutti composer permission UI defaults into app-owned Agent runs
• preserve target-scoped model/reasoning defaults and explicit AgentRunInput.permission
• restore the autonomous Runtime Core default for omitted permissions
• document the precedence contract and bump the package to 0.7.6
• refresh the transitive body-parser lock resolution to 2.3.0 for the production audit

Root cause

The Tutti runtime integration treated permissionConfig.defaultValue as an explicit execution selection. In managed Workspace Apps this overrode the SDK autonomous default. For Claude, the UI default ask-before-write then ran under non-interactive claude -p, so MCP tool calls could not be approved.

Impact

Managed app-owned runtimes that omit permission now use the documented SDK autonomous default. Explicit narrower permissions continue to win. TSH composer UI behavior, wire schemas, model/reasoning defaults, and provider adapters are unchanged.

Validation

• focused regression tests: 40 passed
• full suite, single worker: 236 passed
• pnpm typecheck
• pnpm build
• pnpm audit --prod --ignore-registry-errors: no known vulnerabilities
• pnpm pack:check
• pnpm test:packed-consumer verified @tutti-os/agent-acp-kit@0.7.6
• GitHub Actions CI: passed
• two independent subagent reviews: no findings

The default parallel full-suite run exposed local child-process timing flakes; the affected files and complete suite pass with a single worker, and the GitHub Actions default test command passed.

Risk

The intended behavior restores full-access for managed autonomous runs that omit permission. Hosts that need narrower permissions must pass an explicit runtime permission. This does not alter explicit permission selections or interactive TSH Agent sessions.

AI-assisted implementation and review.

[devin-ai-integration]

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no bugs or issues to report.