feat(tarko): agent resolver should respect workspace

[ulivz]

Summary

This pull request improves how agent implementations are resolved in the server by allowing workspace context to be specified when loading agent modules. This change enhances support for relative module paths and makes agent resolution more robust and flexible.

Agent resolution improvements:

• Updated resolveAgentImplementation to accept an optional workspace parameter, enabling resolution of agent modules relative to a workspace directory. (multimodal/tarko/agent-server/src/utils/agent-resolver.ts)
• When a workspace is provided, module resolution uses it as the base path for relative imports, improving support for custom agent modules and local development. (multimodal/tarko/agent-server/src/utils/agent-resolver.ts)
• Modified AgentServer.start() to pass the workspace context to agent resolution, ensuring agents are loaded correctly in workspace-specific scenarios. (multimodal/tarko/agent-server/src/server.ts)

Checklist

• Added or updated necessary tests (Optional).
• Updated documentation to align with changes (Optional).
• Verified no breaking changes, or prepared solutions for any occurring breaking changes (Optional).
• My change does not involve the above items.

[netlify]

✅ Deploy Preview for agent-tars-docs ready!

Name	Link
🔨 Latest commit	3bed305
🔍 Latest deploy log	https://app.netlify.com/projects/agent-tars-docs/deploys/6891b4695b90b70008d562c0
😎 Deploy Preview	https://deploy-preview-1021--agent-tars-docs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.