[tang-vu]

Summary

• let ods-test.sh --service/-s accept comma-separated service lists
• allow the option to be repeated while preserving first-request order and deduplicating suites
• validate the complete selection before running tests and report missing/empty entries as configuration errors
• continue through the selected subset so the final summary remains a useful validation receipt

Why this matters

Operators and CI jobs often need a focused cross-service check (for example LLM + Whisper + TTS) without paying for the entire validation suite or launching three separate processes. The previous single-service contract made that workflow awkward and produced fragmented summaries.

The behavioral invariant is: a requested service suite runs at most once, in request order, and malformed input never falls through to the all-services path.

Overlap check

Searched open and closed upstream PR titles/bodies for ods-test multiple services service selection, reviewed the latest 1,000 open PRs and their changed production files, and inspected history for ods/scripts/ods-test.sh. No matching PR or currently open production-file overlap was found; upstream history for this script only contains the repository rename. PR #2651 mentions functional-test JSON output but changes a different script and behavior.

Test plan

• bats ods-test-service-selection.bats ? 4/4 passing at the public CLI boundary
  • comma-separated and repeated selections run once in order
  • unselected suites do not run
  • unknown, missing, and empty service entries exit 2 before service dispatch
• bash ods/tests/test-ods-test.sh ? 6/6 error-handling contract checks passing
• bash -n ods/scripts/ods-test.sh
• ShellCheck: no new findings (the file retains three pre-existing SC2034 unused-variable warnings)
• git diff --check

Design and operational notes

• Existing no-argument and single-service invocations are unchanged.
• Deduplication uses an indexed array rather than associative arrays, retaining compatibility with older Bash environments.
• A failing selected suite is recorded and the remaining requested suites still execute; the aggregate failure counter continues to determine exit status.
• Rollback only restores the one-service parser and has no persisted-state impact.

Generated with Codex.

Batch compatibility

• Recommended merge/application order: feat(installer): add configuration-first TUI #3706 -> feat(test): support multi-service validation subsets #3707 -> feat(api): add conditional model-state reads #3708 -> feat(api): batch model route evidence queries #3709 -> feat(api): add GPU history query controls #3710 -> feat(dashboard): export GPU history as CSV #3711 -> feat(dashboard): focus GPU topology links #3712 -> feat(mobile): bootstrap remote ODS Talk portal #3713 -> feat(workflows): make voice memo runnable #3714 -> feat(workflows): make chat endpoint runnable #3715. The PRs have no runtime dependency; this order also covers the shared MODEL-SWITCHBOARD.md edits in feat(api): add conditional model-state reads #3708/feat(api): batch model route evidence queries #3709.
• Synthetic integration head: tang-vu/DreamServer commit 5e4e354 on integration/features-ten-20260904, built from upstream/main 6ff9b4f plus all ten PR heads.
• Combined validation: 12 BATS tests passed; 132 focused API/workflow pytest tests passed; 6 dashboard Vitest tests passed; ESLint and the 1,771-module Vite production build passed; make lint, installer integration (69 passed, 3 skipped), the 6-test ods-test contract, mobile dispatch smoke, and exact n8n 2.6.4 imports for both workflow templates passed. git diff --check is clean.
• Full-suite limitation: make test reaches tests/test-installer-noninteractive-sudo.sh and reports 3 passed / 2 failed when WSL runs as root. The same two assertions fail unchanged on the clean upstream base 6ff9b4f, so this is recorded as environment/baseline evidence rather than attributed to this batch. All required GitHub checks for the ten PR heads are green as of 2026-09-04.

[Lightheartdevs]

Thanks for this contribution. We're closing outside-contributor pull requests that have had no activity for 14 days or more, so the queue reflects work that can still land. This isn't a judgment on the change itself. If it's still needed, please rebase onto main and reopen it or open a focused PR. See #7253 for details and the contribution policy.