Workspace · Dev

Dev QA now has a first live compatibility lane.

Developer-facing stream checks should keep their own grouping, and the first live browser-side compatibility lane now proves the boundary is useful before more helpers land.

Open compatibility lane Back to workspace home

统一外壳执行逻辑保持原样，外层节奏与公开层主题对齐。

Boundary first

The dev lane now has one real execution route, not only placeholders.

That matters more than keeping every QA helper trapped in public planned pages or in the old app shell.

Open compatibility lane Back to workspace home

Planned lane

What belongs in the dev workspace

Keep engineering and QA helpers grouped before they start to sprawl.

Compatibility checks

HLS / DASH compatibility testing now has a live browser-side route, so you can compare manifest structure, browser support, and fetch visibility before heavier playback debugging.

Compatibility laneLive dev execution lane Public Compatibility CheckerSearch-facing public helper M3U8 InspectorCurrent public diagnostic layer

Command and generator helpers

FFmpeg command generation and HLS test stream helpers still belong under dev-oriented routes, but compatibility checks now lead the live layer.

FFmpeg Command GeneratorPlanned HLS Test Stream GeneratorPlanned

Why split now

The route boundary now protects the main runtime and proves that future QA helpers can grow in dev without bloating user-facing execution.

Workspace homeBack to lane routing

User-facing toolsStay simple and task-oriented.

Dev workspace laneAbsorb debug-heavy or QA-heavy helpers later.

Immediate valueProtects the core runtime from future dev-tool sprawl.

Capability boundary

Developer helpers are QA aids only. Keep them out of the public acquisition promise.

These routes are for compatibility checks, not for consumer-facing feature claims.
Prefer noindex handling and explicit helper wording.
Do not let these utilities redefine the site as a dev toolbox.

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.