Workspace · HistoryPublic pagesNo need to carry history state. Workspace historyKeeps review, export evidence, and recovery logic together. Future copyOther tool groups can gain their own history route later.
History needs its own lane too.
Review and recovery do not belong on public acquisition pages, so they now sit behind a dedicated route.
Operational lane
History stays near the runtime, not inside SEO shells.
This keeps replay and review work where it belongs while preserving the public-product split.
Capability boundary
History is a review surface. It should preserve outputs and diagnostics without pretending to rerun everything inline.
- Export and replay are safer than mutating historical records in place.
- Keep prior results readable on mobile even when dense controls collapse.
- Use history to recover context, not to become a second task runner.
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
History runtime
The current history 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-history
Placementsponsor-card
Modeself-promo
Densitylight