Inspect the workspace jobs/activity API for running, queued, completed, or failed background work. Integration imports and syncs use durable run history, so completed and failed receipts remain available after BullMQ retention expires. Use this tool whenever the user asks about jobs, activity, workflows, generation progress, imports, signal processing, PRD/TDD/user-story generation, or failures. Use for examples like: "What jobs are running right now?" -> status active, scope all. Use for examples like: "Did any PRD generation jobs fail recently?" -> status failed, scope project, since recent timeframe if inferable. Use for examples like: "Is signal processing stuck?" -> status active/pending/failed, scope discovery. This is not entity change history: do not use it to determine what a person or agent created or updated, which fields changed, or whether a write was a no-op. Use system.get_change_history for product change attempts and initiator/executor attribution. Do not use roadmap, context documents, or initiative list tools to answer job-state questions. This is the jobs API for chat.