What the Dev category should absorb

Keep these visits in a structured public lane first.

• The user needs a repeatable QA fixture.
  Synthetic inputs and controlled cases are better than debugging random unstable sources.
• The task is really about command scaffolding.
  Command generation only makes sense after the source, output target, and failure type are framed.
• The browser result needs a debugging checklist.
  Public Dev pages can qualify the issue before any workspace-only execution is warranted.

Common causes to explain early

This stops Dev pages from reading like raw feature requests.

• Broken inputs make command generation noisy.
  If the source itself is unstable, generating commands too early usually increases confusion.
• QA often fails because there is no clean fixture.
  Controlled HLS samples can separate playback behavior from content instability.
• Many Dev visits start as troubleshooting, not implementation.
  Guide-first routing often solves the classification problem before the tool even matters.

Recommended order

Bias toward diagnosis and repeatability before execution.

1. Classify the failure with a guide first.
   Use symptom-first public guidance to decide whether the issue is access, playback, or output related.
2. Use the live compatibility checker or the right planned helper second.
   Run browser-side compatibility checks first, then move into command generation or test-stream prep only when the workflow is defined.
3. Escalate into workspace only when execution is real.
   Do not turn the public Dev lane into a promise of full backend processing.

HLS Error Diagnosis

HLS playback diagnosis is the best paired public step because most Dev visits still begin with “what is actually failing?”

HLS playback error

Open the matching problem guide before returning to the correct tool.

M3U8 open failed

Open the matching problem guide before returning to the correct tool.