diff --git a/Auto Run Docs/Initiation/2026-03-31-WebSocket-Progress-And-Polish/WEBSOCKET-PROGRESS-01.md b/Auto Run Docs/Initiation/2026-03-31-WebSocket-Progress-And-Polish/WEBSOCKET-PROGRESS-01.md
index 97f038b..0d24b51 100644
--- a/Auto Run Docs/Initiation/2026-03-31-WebSocket-Progress-And-Polish/WEBSOCKET-PROGRESS-01.md	
+++ b/Auto Run Docs/Initiation/2026-03-31-WebSocket-Progress-And-Polish/WEBSOCKET-PROGRESS-01.md	
@@ -18,11 +18,12 @@ The backend event bus, WebSocket route, progress parser, and frontend context/ho
   - Create a small wrapper component (e.g., `QueueItemProgress`) that calls `useDownloadProgress(contentItemId)` and renders `<DownloadProgressBar>` when progress exists, or falls back to the existing `<StatusBadge>` when no active progress
   - Update the `status` column render in the Queue table to use this wrapper for items with status `downloading`
 
-- [ ] Integrate download progress into the Channel Detail page:
+- [x] Integrate download progress into the Channel Detail page:
   - Read `src/frontend/src/pages/ChannelDetail.tsx` to understand how content items are displayed
   - Search for how content items render their status in this page
   - For content items with status `downloading`, show the `DownloadProgressBar` alongside or instead of the static status badge
   - Use the same `useDownloadProgress` hook pattern established in the Queue page
+  - **Note:** Already wired in commit 0541a5f. `ContentStatusCell` component (lines 38-46) uses `useDownloadProgress(item.id)` and renders `<DownloadProgressBar>` for active downloads, falling back to `<StatusBadge>`. Used in status column at line 560.
 
 - [ ] Add a WebSocket connection status indicator to the Sidebar or app header:
   - Read `src/frontend/src/components/Sidebar.tsx`