Use command primitive for templates

[benjaminshafii]

Summary

Use the core command primitive when rendering/executing templates instead of the custom implementation currently in OpenWork. This should align templates with OpenCode’s native tool surface and reduce bespoke logic.

Why

• Keeps parity with OpenCode primitives
• Removes duplicated implementation details
• Simplifies future template features

Notes

• Identify current custom template command flow and swap to the command primitive
• Ensure any UI surfaces map cleanly to the underlying tool

[benjaminshafii]

Automated message: agree — using the OpenCode command primitive for templates aligns with the “parity + thin UI” philosophy and should reduce bespoke logic. Next step is to map template runs in packages/app/src/app/template-state.ts to the command surface and keep the UI as a thin wrapper. I’ll mark this as a priority architecture cleanup.