SubMiner/backlog/tasks/task-74 - Add-launcher-regression-tests-for-config-discovery-and-command-branching.md

id, title, status, assignee, created_date, updated_date, labels, dependencies, priority, ordinal

id	title	status	assignee	created_date	updated_date	labels	dependencies	priority	ordinal
TASK-74	Add launcher regression tests for config discovery and command branching	Done		2026-02-18 11:35	2026-02-22 07:49	launcher tests regression	TASK-70	medium	84000

Description

Launcher currently has no direct test coverage for config discovery behavior and key command branching paths. This leaves wrapper flows vulnerable to regressions when refactoring config or process-control logic.

Action Steps

1. Add launcher-focused test harness (unit/integration-lite) under existing project test runner.
2. Cover config discovery matrix:
   • XDG_CONFIG_HOME overrides
   • SubMiner vs subminer
   • .jsonc vs .json preference
3. Cover CLI branch behavior (doctor, config path/show, mpv status/socket, jellyfin command routing).
4. Mock fs/process/spawn boundaries to keep tests deterministic.
5. Wire tests into existing test:core:dist or dedicated launcher test command.

Acceptance Criteria

• #1 Launcher config discovery paths are regression-tested
• #2 Core launcher command branches are regression-tested
• #3 Tests run in CI/local test gate without external process dependencies

Definition of Done

• #1 Launcher tests included in standard test workflow
• #2 Documented how to run launcher tests locally