Debug CLI regression follow-up — manual scenario verification
Summary
Updated
debug/debug_cli_regression.pyto add_scenario_slug_from_commandhelper and enhance the manual follow-up test so it re-runs scenarios, reloadsdebug/map.json, and inspects errors, allowing onlypy_legacyissues.Recorded Bun test log for Linux via
bun run test:log:linuxper contributor guidelines.
Commands executed
bun installbun run setup:uvbun run setup:pyodidebun run test(fails in baseline due to known parser regressions)bun run check(fails because Prettier flags existing formatting on debug/map.json; not modified)bun run test:log:linux(produces failing test log matching baseline expectation)
Notes
The manual follow-up test now mirrors the primary regression test flow, relying on scenario data instead of process exit codes.
Existing Prettier warnings for
debug/map.jsonremain unresolved to avoid a repository-wide formatting churn; behaviour matches prior runs.Bun test suite continues to report the known failure for
runDrawioPipeline preserves literal HTML when stripHtml disabled.