[SaladDay]

Claude hosted Sessions can now use declared public functions alongside native workspace tools. Codex and Claude use one service qualification catalog and the existing Runtime contract; native limits remain in adapter profiles, and shared dispatch uses verified capabilities instead of engine-name allowlists.

The change preserves existing lifecycle, tenant/credential/history isolation and workspace controls. It documents the minimal onboarding surface and remaining native gaps. Hosted HTTP MCP, image-result conversion, self-hosted executor changes and new protocol resources are outside this batch.

Validation:

• make check, API generation, focused Go suites and race tests passed on zju_a100_2.
• Claude adapter Linux tests: 96 passed.
• The same fixed OpenAI SDK 3.13.0/raw HTTP assertions passed with real Kimi K3 on Codex 0.153.4 and Claude SDK 0.3.269/native 2.1.269: function success/error, exact native file/artifact bytes, cold history continuation, foreign result rejection and pending-call cancellation.
• Independent Core/database/Docker deployment used the current daemon. Cold restart restores Core before Runtime startup; startup during Core unavailability is a separately recorded limitation.

Evidence: ~/.parsar/remediation/20260919/harness-parity/ on the validation server. This qualifies the bounded profile; it does not claim complete engine parity or full Agents API compatibility.