fix(override): prune services the compose file no longer has

[grantemsley]

What changed

pruneOrphanOverrideServices() runs before every Compose Up to drop override entries for services the
compose file no longer has. To find the valid services, getMainFileServices() runs
docker compose ... config --services, but the -f list it used included the managed override itself. An
entry for a removed or renamed service holds only labels and no image, so compose failed on it ("has neither
an image nor a build context"), the list came back empty, and nothing was ever pruned. The up that followed
then failed on the same entry.

The services are now listed without the managed override and without the icon override generated from it
(new private buildComposeFileFlagsWithoutManagedOverride()). Everything else in the file list stays: the
main compose file, an indirect stack's own override, and extra compose files from COMPOSE_FILE or the
stack settings, so their services still count as valid.

Related issues

#118 (the stack that wouldn't start after a service was removed; reproduction in my comment there)

Checklist

• I have added/updated tests where applicable
• I have updated documentation (docs/, README, or plugin docs): N/A nothing user-facing changes
• Linted/formatted the code (PHPStan clean)
• Verified on Unraid or CI

Testing notes

• New tests/unit/PruneOrphanOverrideServicesTest.php: a stand-in docker on PATH that, like compose,
  fails when handed the override with an image-less entry. It fails before this change and passes after. Full
  PHPUnit suite passes.
• On Unraid 7.3.2 with v2026.10.02.1007: with the reproduction from the issue, the stock Util.php returns
  {"changed":false,"removed":[]} and this branch's returns {"changed":true,"removed":["old"]}, with the
  entry gone from the override and the other one kept.

Notes

• Stacks using default file discovery (use_default_compose_files) are unchanged: they pass no -f flags,
  so there is no file to leave out, and compose itself loads compose.override.yaml from the folder.

[Copilot]

Copilot review overview

🟡 Changes recommended

Default Compose file discovery still loads the managed override, leaving the reported failure unresolved in that supported mode.

Review effort: Balanced
Findings: 1

Open (1)

• Exclude managed override when querying direct stack services · New

What changed in this PR

Fixes orphan-service pruning by excluding managed overrides when querying valid Compose services.

Changes:

• Adds filtered Compose file flag construction.
• Adds regression tests for pruning stale override entries.

File	Description
source/​compose.manager/​include/​Util.php	Excludes managed overrides during service discovery.
tests/​unit/​PruneOrphanOverrideServicesTest.php	Tests stale-service pruning behavior.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.