fix(devops-copilot): stop loading indicator overlapping thread messages

[RemiBonnet]

What

Fixes a UI defect in the DevOps Copilot panel where a chat bubble overlapped the "Suggested Next Steps" content and floated above the Plan steps row instead of scrolling with the thread.

Root cause

LoadingIndicator (which renders the streaming response's Plan steps toggle) wrapped its content in <div className="relative top-2 mt-auto">. Inside the fixed-height (h-[220px] / expanded) scrollable message list, mt-auto pins the element to the bottom of the viewport rather than letting it flow directly under the last message. Since the user message is added to the thread immediately on send, the loading indicator was pushed below/over the preceding bubble, producing the overlap. StreamingMessage and AssistantMessage already flow naturally without mt-auto.

Change

• Remove top-2 mt-auto from the loading indicator wrapper so it flows in normal order and inherits the list's gap-4 spacing, scrolling with the thread.

Scope

One-line Tailwind class change, no logic/TS changes. Existing unit tests don't assert on this wrapper class.

Checks

⚠️ Node/Yarn are not available in the agent environment, so format/test/typecheck/lint were not run locally — relying on CI to validate.

Testing

Open the Copilot panel, start a conversation and trigger a loading/streaming response with plan steps: the "Plan steps" row now appears in-flow under the latest message and scrolls with the thread instead of overlapping it.

---

Summary by cubic

Fixes the DevOps Copilot loading indicator overlapping prior thread messages in the chat panel.

The "Plan steps" row used mt-auto, which pinned it to the bottom of the fixed-height message list, causing it to float over the previous chat bubble instead of flowing under the latest message. Removing mt-auto lets it render in normal order and scroll with the thread.

^{Written for commit 464b216. Summary will update on new commits.}

[nx-cloud]

View your CI Pipeline Execution ↗ for commit bcb5563

Command	Status	Duration	Result
nx run console:build --parallel=3 --configurati...	✅ Succeeded	1m 23s	View ↗
nx affected --target=test --parallel=3 --config...	✅ Succeeded	2m 49s	View ↗
nx affected --target=lint --parallel=3	✅ Succeeded	2m 26s	View ↗
nx-cloud record -- yarn nx format:check	✅ Succeeded	3s	View ↗

💡 Verify your cache is correct by running tasks in a sandbox. Read docs ↗

---

☁️ Nx Cloud last updated this comment at 2026-09-22 08:53:04 UTC

[cubic-dev-ai]

No issues found across 1 file

Confidence score: 5/5

• Automated review surfaced no issues in the provided summaries.
• No files require special attention.

_{Re-trigger cubic}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 52.73%. Comparing base (4ff8108) to head (464b216).
⚠️ Report is 1 commits behind head on staging.

Additional details and impacted files

@@             Coverage Diff             @@
##           staging    #2996      +/-   ##
===========================================
+ Coverage    51.87%   52.73%   +0.86%     
===========================================
  Files          896      910      +14     
  Lines        22406    22707     +301     
  Branches      6901     6944      +43     
===========================================
+ Hits         11622    11974     +352     
+ Misses        8834     8774      -60     
- Partials      1950     1959       +9     

Flag	Coverage Δ
unittests	52.73% <ø> (+0.86%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[RemiBonnet]

🎉 This PR is included in version 1.360.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀