fix: fixed tui service status to now properly show container status instead of missing

[Vchen7629]

Summary

Fixes #2134 The TUI status screen was showing all container services as "Missing" on Podman because the container name resolution relied on reconstructing a {project_name}-{service} prefix, but Compose derives the project name from the compose file's directory (~/.openrag/tui/), producing tui-* containers instead of the assumed openrag-*. The fix introduces a _resolve_service_name helper that keys off the stable com.docker.compose.service label (Podman) and the Service field (Docker) before falling back to the existing name map, matching the pattern already used in welcome.py. This makes status resolution robust regardless of what project name Compose derives at runtime.

Changes

• src/tui/managers/container_manager.py: add _resolve_service_name helper and wire it into both Docker and Podman status paths to resolve containers by compose label before falling back to the name map
• tests/unit/test_container_manager_status.py: add regression and fallback tests for the new resolution logic

Summary by CodeRabbit

• Bug Fixes
  • Improved container status detection for Docker and Podman environments.
  • Service names are now resolved reliably from compose metadata, even when container naming conventions differ.
  • Preserved fallback support for legacy container-name mappings.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: cf1e1831-cbc8-4ae4-8cb6-4bcac5b9bfc4

📥 Commits

Reviewing files that changed from the base of the PR and between 547c868 and 2e7f0a3.

📒 Files selected for processing (1)

• tests/unit/test_container_manager_status.py

🚧 Files skipped from review as they are similar to previous changes (1)

• tests/unit/test_container_manager_status.py

---

Walkthrough

Container status resolution now prefers compose service metadata for Docker and Podman containers, falling back to legacy container-name mappings. Tests cover prefix-independent resolution and unmatched-container behavior.

Changes

Container status resolution

Layer / File(s)	Summary
Canonical service-name resolution and validation src/tui/managers/container_manager.py, tests/unit/test_container_manager_status.py	ContainerManager resolves services from compose fields or labels before using container_name_map; tests cover Docker JSON, Podman status refreshes, legacy fallback, and unrelated container names.

Estimated code review effort: 3 (Moderate) | ~15–30 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title is specific and matches the main change: fixing TUI service status resolution.
Linked Issues check	✅ Passed	The PR updates TUI container status resolution to use compose labels and fallback mapping, matching #2134.
Out of Scope Changes check	✅ Passed	The changes stay focused on TUI service-name resolution and matching tests, with no unrelated behavior changes.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch tui-service-status-fix

---

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

[coderabbitai]

Actionable comments posted: 2

🧹 Nitpick comments (1)

tests/unit/test_container_manager_status.py (1)

28-51: 📐 Maintainability & Code Quality | 🔵 Trivial | ⚡ Quick win

Add a regression test for Docker Service-field resolution.

The production change covers both Podman labels and Docker’s Service field, but these tests only exercise the Podman path and direct fallback. Add a focused _process_service_json test so regressions in the Docker branch are detected.

Suggested test

+def test_process_service_json_resolves_by_compose_service():
+    manager = _make_manager()
+    services = {}
+
+    manager._process_service_json(
+        {
+            "Name": "tui-opensearch",
+            "Service": "opensearch",
+            "State": "running",
+        },
+        services,
+    )
+
+    assert services["opensearch"].status == ServiceStatus.RUNNING

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@tests/unit/test_container_manager_status.py` around lines 28 - 51, Add a
focused test for _process_service_json that supplies a container record with
Docker’s Service field and verifies it resolves to the expected service and
status. Keep the test independent of label-based resolution and assert the
Docker branch’s resulting service mapping so regressions are detected.

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@Makefile`:
- Around line 735-743: Extend the Power architecture fallback beyond the
Makefile frontend target so every frontend dev entrypoint uses Webpack on
ppc64le and ppc64. Update the frontend package-level dev command or the
Playwright startup configuration, using the existing architecture detection and
preserving plain next dev for other architectures; ensure both npm run dev and
Playwright startup select the fallback consistently.
- Around line 739-743: Update both Next.js dev command branches in the Makefile
to pass the configured bind-host variable instead of invoking the machine’s
hostname. Preserve the existing default and use the same host setting for both
the branch containing the preceding command and the npx next dev fallback.

---

Nitpick comments:
In `@tests/unit/test_container_manager_status.py`:
- Around line 28-51: Add a focused test for _process_service_json that supplies
a container record with Docker’s Service field and verifies it resolves to the
expected service and status. Keep the test independent of label-based resolution
and assert the Docker branch’s resulting service mapping so regressions are
detected.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: e35f6e4a-ca04-4e13-b953-326edc4d2e5a

📥 Commits

Reviewing files that changed from the base of the PR and between a64af53 and 547c868.

📒 Files selected for processing (6)

• Makefile
• frontend/build.js
• frontend/next.config.ts
• frontend/package.json
• src/tui/managers/container_manager.py
• tests/unit/test_container_manager_status.py

[lucaseduoli]

LGTM but please merge to main instead of release-0.6.0. I will cherry pick the commit later