SubMiner/backlog/tasks/task-199 - Forward-launcher-log-level-into-mpv-plugin-script-opts.md

id, title, status, assignee, created_date, labels, dependencies, references, documentation, priority

id	title	status	assignee	created_date	labels	dependencies	references	documentation	priority
TASK-199	Forward launcher log level into mpv plugin script opts	Done		2026-03-18 21:16		TASK-198	/home/sudacode/projects/japanese/SubMiner/launcher/aniskip-metadata.ts /home/sudacode/projects/japanese/SubMiner/launcher/mpv.ts /home/sudacode/projects/japanese/SubMiner/launcher/main.test.ts /home/sudacode/projects/japanese/SubMiner/launcher/aniskip-metadata.test.ts		medium

Description

Make subminer --log-level=debug ... reach the mpv plugin auto-start path by forwarding the launcher log level into --script-opts, so plugin-started overlay and texthooker subprocesses inherit debug logging.

Acceptance Criteria

• #1 Launcher mpv playback includes subminer-log_level=<level> in --script-opts when a non-info CLI log level is used.
• #2 Detached idle mpv launch uses the same script-opt forwarding.
• #3 Regression tests cover launcher script-opt forwarding.

Implementation Plan

1. Add a failing launcher regression test that captures mpv argv and expects subminer-log_level=debug inside --script-opts.
2. Extend the shared script-opt builder to accept launcher log level and emit subminer-log_level for non-info runs.
3. Reuse that builder in both normal mpv playback and detached idle mpv launch.
4. Run focused launcher tests and launcher-plugin verification.

Outcome

Forwarded launcher log level into mpv plugin script opts via the shared builder and reused that builder for idle mpv launch. subminer --log-level=debug ... now gives the plugin opts.log_level=debug, so auto-started overlay and texthooker subprocesses include --log-level debug and the tokenizer timing logs can actually appear in the app log.