# Task: Scope content editor channels to item workspace

## Feature

`docs/FEATURES/channels.md`

## Goal

Prevent content item channel placements from mixing channels across workspaces when the app is viewed in an all-workspaces scope.

## Context

Seeded content such as `Bakery loyalty carousel` should only use channels from its own workspace. The seed source assigns it to `Atlas Bakery Instagram`, but stale editor drafts or all-workspaces channel options can show unrelated Luma channels in the content detail editor.

## Scope

- Limit content detail channel options to the content item's workspace.
- Deduplicate publication target parsing and summary serialization.
- Normalize restored editor drafts so duplicate or other-workspace known channels are not kept.

## Validation

```bash
cd frontend
npm run build
```

## Acceptance Criteria

- [x] Existing content items only offer channels from their own workspace.
- [x] Duplicate publication target strings render as one placement.
- [x] Stale restored drafts do not keep known channels from other workspaces.
