[tang-vu]

Summary

• add an opt-in install.sh --tui configuration menu for Linux, WSL2, and macOS
• expose runtime, tier, install directory, service profile, LAN, offline, bootstrap, and dry-run decisions before installation starts
• compile the confirmed plan into the existing non-interactive installer flags, preserving one canonical execution path
• prevent accidental execution when the plan is cancelled or --tui is mixed with CLI flags

Closes #2309.

Why this matters

Operators currently have to discover profiles and flags before they can review installer defaults. The new menu makes those choices visible up front, supports custom absolute install paths, and provides an explicit final receipt before any system-changing installer phase runs.

The behavioral invariant is: the menu may collect and translate configuration, but only the existing installer owns installation effects. Cancellation must never dispatch the installer.

Overlap check

Searched open and closed upstream PR titles/bodies for installer TUI configuration menu, reviewed the latest 1,000 open PRs and their changed production files, and inspected history for ods/install.sh. No open or closed PR covers this scope, no currently open PR changes this entrypoint, and its upstream history only contains the repository rename. Issue #2309 is the direct product request.

Test plan

• bats installer-configuration-tui.bats - 4/4 passing against the public install.sh boundary
  • confirmed custom plans preserve tier, service choices, dry-run behavior, and a spaced custom install path
  • cancellation never invokes the installer target
  • ambiguous mixed TUI/CLI input exits with status 2
• bash -n ods/install.sh
• shellcheck --rcfile=/dev/null -e SC1090,SC1091,SC3003 ods/install.sh
• git diff --check

Design and operational notes

• Existing flag-based installs are unchanged; the TUI is strictly opt-in.
• The menu uses Bash 3-compatible constructs for the macOS path and the shared dispatcher covers Linux and WSL2. Native Windows continues to use install.ps1, with an explicit error if a PowerShell target reaches this mode.
• The full profile delegates to the existing --all contract. Other profiles emit explicit positive/negative service flags so the review receipt is deterministic.
• Rollback is a single-entrypoint revert; no persisted configuration or migration is introduced.

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.

CI follow-up

CI integration-smoke exposed a SIGPIPE race in the first help implementation: the dispatcher wrote its TUI hint before install-core rendered the rest of help, so a short grep reader could close the pipe under pipefail. Follow-up commit 6650e11 buffers delegated help, preserves its status, and writes defensively. The added public-boundary regression reproduces the exact piped probe; 4/4 focused BATS tests, ShellCheck, and integration-test.sh (69 passed, 3 skipped) now pass, and the rerun of every required GitHub check is green.

[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.