fix(acp): keep unknown approvals actionable

[t3-code]

what changed

• map unrecognized ACP permission kinds to dynamic_tool_call
• preserve existing execute, read, and file-change mappings
• verify generic requests remain actionable in the web approval list

why

Cursor and Grok can send permission kinds outside our known set. Those requests were projected as pending but omitted by the client, leaving an Approval status with no card to resolve.

ui changes

No visual styling changes. Previously hidden generic approvals now use the existing command approval card.

checks

• 63 focused ACP and session-logic tests
• server and web typechecks
• targeted formatting
• git diff --check

Model: OpenAI (API model not exposed). Harness: T3bot.

Note

Map unknown ACP permission kinds to dynamic_tool_call instead of unknown

Unrecognized ACP permission kinds previously mapped to 'unknown' in canonicalRequestTypeFromAcpKind, making those approvals non-actionable. The default case in AcpCoreRuntimeEvents.ts now returns 'dynamic_tool_call', and the AcpCanonicalRequestType alias is updated to match. On the web side, dynamic_tool_call request types are derived as requestKind: 'command' pending approvals, so they surface correctly in the UI.

^{Macroscope summarized 2634697.}