feat(desktop): prefer templates and generated creation drafts

[PeterGuy326]

Creation screens currently require users to type names, descriptions and acceptance items before proceeding. Local workspaces, employees, and projects/goals now offer editable template drafts so users can choose a starting point and confirm.

• Workspaces prepare a name, description and usable default Agent, with optional editing and existing directory names retained.
• Employees offer four role templates or a short natural-language brief for the existing Agent drafting flow. Model-format instructions stay internal; readable candidates require explicit application and preserve edits made while waiting.
• Projects/goals prepare descriptions and acceptance criteria, with a readable preview and optional editing. Switching templates preserves draft edits.

Confirmation uses the existing creation APIs. Role templates keep the existing budgets and permissions. Proposal application retains omitted or unchanged capability groups and their custom rules; explicit empty groups clear only that group. Advanced policy review opens only for actual changes. Request guards prevent duplicate submissions and stale callbacks; previously issued Agent turns retain their originating timeout.

Validation: latest-head full Node 24 checks on Ubuntu and macOS, CodeQL, dependency review, Scorecard, both staging/native Windows checks and unsigned installers, and cross-platform layout parity all passed. Local focused creation, lifecycle, parser and i18n checks passed. Browser QA used the real components with simulated bridge data, including template confirmation, readable generated candidates, and English light mode at 390px with zero visible text fields after selecting a project template.