prometeu-studio/docs/studio/pull-requests/PR-05d-assets-activity-progress-and-logs-integration.md

PR-05d Assets Activity Progress and Logs Integration

Briefing

Integrate the Assets workspace with Studio activity, progress, and logs according to the assets workspace specification.

Objective

Make the Assets workspace operationally legible by wiring:

• structured activity into the shell right-side panel
• contextual progress into the workspace
• detailed textual logs into the lower region
• failure retention and acknowledgement surfaces where required

Dependencies

• ./PR-05a-assets-workspace-foundation-and-service-state.md
• ./PR-05c-selected-asset-details-contract-and-preview.md

Scope

• map asset-service events into Studio activity entries
• aggregate repetitive background events into user-facing summaries
• wire progress_updated into progress surfaces without feed spam
• expose lower-region textual logs for asset operations
• retain recent actionable failures until acknowledgement
• mirror selected-asset failures inline where applicable

Non-Goals

• no generic all-workspace activity framework redesign beyond what Assets needs now
• no final cross-workspace logs unification

Execution Method

1. Define asset-workspace activity mapping rules.
2. Wire workspace and global bus publications for asset activity.
3. Implement feed aggregation for repetitive events.
4. Implement inline progress and lower-region logs integration.
5. Retain and surface actionable failures across shell and workspace surfaces.

Acceptance Criteria

• asset events appear in the global Activity feed as user-oriented entries
• progress updates do not spam the feed
• logs are visible in the lower region for technical drill-down
• actionable failures remain visible until acknowledged
• selected-asset failures also appear inline when relevant

Validation

• unit tests for activity aggregation mapping
• unit tests for failure retention logic
• UI smoke validation for shell/workspace activity interplay

Affected Artifacts

• activity event adapters
• progress surfaces
• workspace log region integration
• failure retention state
• tests for activity mapping and failure behavior