fix(server): preserve tool lifecycle identity - #7151

💭 Looking at the diff, the changes are in ActivityPayloadProjection.ts and ProviderRuntimeIngestion.ts, which appear to be mostly pure functions without Effect service changes. I want to check the imports and touched regions to confirm there are no violations. This diff is just pure functions with no Effect services, errors, or layers involved, so nothing applies under those conventions. I'm double-checking whether adding command arguments into the projected activity payload counts as an error field concern, but it seems unrelated since that guidance is about error attributes, not general payload data. Given there are no actual findings, I'll produce a JSON response with a success state and "All clear" as the summary, since the schema requires structured output even though the instructions mention a plain-text response.