refactor(web): rename agent workspace files → context to match budagent

[dittops]

Summary

• Companion to BudEcosystem/bda#29. The budagent rename moves the agent's prompt-context surface (AGENTS / SOUL / USER / MEMORY) from "workspace" to "context" everywhere — the previous name was overloaded with Rust workspaces, exec sandbox dirs, etc.
• This PR flips the frontend to match: type names, fetch URLs, LLM tool catalog entries, UI labels.
• Must land in lockstep with bda#29 — the frontend will 404 against the old /api/agent/workspace-files paths after the backend deploy.

Renames (breaking, no back-compat)

File	Change
components/desktop/AgentConfigView.tsx	interface WorkspaceFile → AgentContextFile; 4 fetch URLs /api/agent/workspace-files[/{path}] → /api/agent/context[/{path}]; UI strings "Workspace Files" → "Context Files"
lib/agent/tools/local-execution.ts	syncWorkspaceFileToBackend → syncAgentContextFileToBackend; fetch URL → /api/agent/context
lib/agent/tools/tool-catalog.ts	tool name fields workspace_read/write/list → context_read/write/list; descriptions reworded
app/api/local-agent/{execute,cron-tool-execute}/route.ts	imports + call sites renamed; comments updated

Untouched (separate concept)

• workspace_path / workspacePath on session payloads — that's the agent's session working directory, not the prompt-context files. Lives in gateway.ts, executor.ts, session-client.ts, BudAgentScreen.tsx, etc. Unaffected.
• SandboxPolicy::WorkspaceWrite / "workspace-write" enum values in cli-agent-tool.ts — Codex CLI sandbox-policy concept.
• Generic Slack/Asana/Bitbucket "workspace" product names in lib/connectors/connectors.tsx.
• Admin-page copy ("Manage general settings applicable to all users in the workspace") — generic product language.

Verification

• Edited files clean under pnpm tsc --noEmit (31 pre-existing errors elsewhere, all unrelated)
• Lint clean on touched directories
• Manual smoke recommended after merge: open AgentConfigView, edit a context file, start a chat, confirm context_* tool calls round-trip

Test plan

• BudEcosystem/bda#29 lands first (or simultaneously); confirm no traffic to old /api/agent/workspace-files after rollout
• Open the Agent Config (Context Files) panel — verify list/read/write all work end-to-end
• Start a fresh chat, ask the agent to "list your context files" — verify it calls the new context_list tool name
• Cron-tool execute path: schedule a quick job that touches context, confirm syncAgentContextFileToBackend flushes correctly

🤖 Generated with Claude Code

[gemini-code-assist]

Code Review

This pull request renames 'workspace files' to 'context files' across the codebase to ensure consistent terminology. The changes involve updating API endpoints from /api/agent/workspace-files to /api/agent/context, renaming internal functions and interfaces such as syncWorkspaceFileToBackend and WorkspaceFile, and modifying tool names in the catalog (e.g., workspace_read to context_read). I have no feedback to provide.