Progress UI: no way to identify which project an operation belongs to

[FYZAFH]

Problem

When multiple MCP instances are running across different projects/directories, all progress events are merged into a single web page on port 23120. The server/client architecture correctly forwards events from secondary instances to the primary server via POST /ingest, but the resulting UI has no indication of which project or working directory each operation originated from.

The sidebar labels are generic (Write, Spec Review, Quality Review, etc.), inferred solely from the operationId prefix. When several projects are active simultaneously, it becomes impossible to tell which operation belongs to which project.

Current Behavior

• Sidebar shows entries like Write, Review, Spec Review with only a timestamp and a truncated instruction snippet
• ProgressEvent contains only timestamp, operationId, type, and content — no project/source field
• operationId is generated as write-<uuid> or review-<uuid>, which carries no project context

Expected Behavior

• Each operation should display which project/working directory it belongs to
• The sidebar or main view should make it easy to distinguish operations from different projects
• Optionally, support filtering by project

Suggested Approach

1. Add a source or project field to ProgressEvent (e.g., the working directory basename or a configurable project name)
2. Populate this field in startOperation() from the tool's workingDirectory parameter
3. Display the project name in the sidebar (e.g., as a secondary label or grouping header)
4. Forward this field through the /ingest endpoint so client-mode instances also carry project context