Workspace · QueueSingle-task public toolsKeep public tools fast and simple. Queue laneHandle repeated jobs, import/export, and status changes here. Future patternSubtitle/video batch lanes can copy this structure later.
Batch work belongs in a queue lane, not on public pages.
Queue is one of the clearest boundaries between acquisition pages and the workspace runtime.
Batch lane
Batch execution is now a first-class route.
This is where repeat jobs belong while public pages remain single-task and SEO-first.
Capability boundary
Queue is for repeated work, not for proving that every long job belongs in the first screen.
- Batch runs can pause, fail, or need replay; keep that state in queue/history.
- Preserve queue snapshots instead of implying guaranteed uninterrupted runs.
- Move one-off tests back to inspector or player.
Mobile execution
On narrow screens, keep the current task visible first and collapse helper rails into secondary controls.
- Player and inspector remain primary mobile modes.
- Queue, history, and settings should stay reachable without dominating the first screen.
- Avoid introducing extra fixed panels that cover inputs or results.
Execution surface
Queue runtime
The current queue runtime is mounted below.
M3U8 Toolkit
Loading workspace lane…
Low-interference sponsor slotView ad policy
Sponsor cards stay after the execution surface instead of cutting across the main input or primary action.
Slot IDad-ws-sponsor-primary-m3u8-queue
Placementsponsor-card
Modeself-promo
Densitylight