fix: resolve optional launcher secret from documented path

[eXPerience83]

What changed

• changes the optional generic launcher-auth override fallback from compose/secrets/launcher_password.txt to the documented repository-root secrets/launcher_password.txt;
• renders the combined base + override Compose configuration without LAUNCHER_PASSWORD_PATH and asserts that the resolved default points to the README location;
• retains the existing explicit-path test proving the secret value is absent from rendered Compose JSON.

Scope

This is a minimal follow-up to the final Codex finding on merged PR #65. It does not change the normal generic or TrueNAS launcher, Codex authentication, mounts, persistence, proxying, optional agents or hardening.

Validation required

• python3 -m py_compile scripts/test_single_stack_compose.py;
• python3 scripts/test_single_stack_compose.py;
• standalone and combined Compose rendering;
• complete Build AMD64 job on the exact final head.

[coderabbitai]

Warning

Review limit reached

@eXPerience83, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 21 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: aa0d1720-5bbd-43ca-b2ee-0cebe55c5623

📥 Commits

Reviewing files that changed from the base of the PR and between bc9578f and fe94376.

📒 Files selected for processing (2)

• compose/launcher-auth.yml
• scripts/test_single_stack_compose.py

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[eXPerience83]

@codex review

Please review exact head fe9437612bb9559c476cecb6dd4d2f5e8bc5aa8b. This is the minimal follow-up to your final #65 finding: the optional override fallback now resolves the documented repository-root secret, and the Compose regression renders the default path without LAUNCHER_PASSWORD_PATH. Confirm that the path semantics and test are correct and that the normal TrueNAS/password-free launcher boundary is unchanged.

[chatgpt-codex-connector]

Codex Review: Didn't find any major issues. More of your lovely PRs please.

Reviewed commit: fe9437612b

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".