fix(admin): keep running Feature Stacks collapsible

[lopugit]

Summary

• respect the admin's collapsed Feature Stack state even while a merge run is live
• keep live polling and progress updates running in the background
• update the manual regression checklist and changelog

Validation

• npm --prefix remix run test:ci-control (34/34)
• targeted ESLint on CIControlDashboard.tsx
• npm --prefix remix run build
• mobile production QA at 375x812 identified and reproduced the forced-open regression

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
thingtime	Canceled		Aug 31, 2026 10:43am

[github-actions]

🤖 Lopu live PR update

Status: ✅ Lopu finished — this PR is closed or merged

Current phase: The resolver branch work is complete

Estimated completion: Done — no further active-work ETA.

Time conversion (UTC source)

Moment	UTC	Los Angeles	Melbourne
Updated	2026-08-31 11:02 UTC (UTC+00:00)	2026-08-31 04:02 PDT (UTC-07:00)	2026-08-31 21:02 AEST (UTC+10:00)

Los Angeles and Melbourne use their real IANA time zones, so PDT/PST and AEST/AEDT offsets change automatically.

Lopu queue and PR pulse

Scope	Metric	Count
Repository	Open PRs	36
Repository	Conflicting	28
Repository	Out-of-date with target	0
Repository	GitHub state unknown	0
Repository	Part of an open stack	0
Repository	Touch files changed by another open PR	36
Repository	Target a non-root branch without an open parent PR	0
This resolver batch	Admitted snapshots	1
This resolver batch	Currently resolving	0
This resolver batch	Waiting	0
This resolver batch	Finished	1

Related PR context

• Stack: No open parent or child PR currently links to this branch.
• Target: main is a repository root/integration branch.
• Changed-file overlap: 3 changed files are also touched by #54, #57, #68, #74, #79, #92, #93, #101, #105, #107, #130, #175, +7 more.

Exact branch pair: main → codex/fix-running-stack-collapse.

Timeline

• 10:37 UTC — Detected that main needs to be merged into codex/fix-running-stack-collapse; assigning the exact snapshot to the resolver queue.
• 10:38 UTC — Still safely queued behind earlier admitted Lopu work; no duplicate resolver was spawned.
• 10:49 UTC — 10-minute check-in: still working — Waiting in Lopu's serialized PR-management lane.
• 10:59 UTC — 10-minute check-in: still working — Waiting in Lopu's serialized PR-management lane.
• 11:02 UTC — The resolver worker completed successfully and the PR is no longer open.

Technical run details — optional; this comment is the human-facing source of truth.

[github-actions]

🤖 Lopu live PR update

Status: ✅ Lopu finished — this PR is closed or merged

Current phase: The resolver branch work is complete

Estimated completion: Done — no further active-work ETA.

Time conversion (UTC source)

Moment	UTC	Los Angeles	Melbourne
Updated	2026-08-31 11:03 UTC (UTC+00:00)	2026-08-31 04:03 PDT (UTC-07:00)	2026-08-31 21:03 AEST (UTC+10:00)

Los Angeles and Melbourne use their real IANA time zones, so PDT/PST and AEST/AEDT offsets change automatically.

Lopu queue and PR pulse

Scope	Metric	Count
Repository	Open PRs	36
Repository	Conflicting	28
Repository	Out-of-date with target	0
Repository	GitHub state unknown	0
Repository	Part of an open stack	0
Repository	Touch files changed by another open PR	36
Repository	Target a non-root branch without an open parent PR	0
This resolver batch	Admitted snapshots	1
This resolver batch	Currently resolving	0
This resolver batch	Waiting	0
This resolver batch	Finished	1

Related PR context

• Stack: No open parent or child PR currently links to this branch.
• Target: main is a repository root/integration branch.
• Changed-file overlap: 3 changed files are also touched by #54, #57, #68, #74, #79, #92, #93, #101, #105, #107, #130, #175, +7 more.

Exact branch pair: main → codex/fix-running-stack-collapse.

Timeline

• 10:39 UTC — Detected that main needs to be merged into codex/fix-running-stack-collapse; assigning the exact snapshot to the resolver queue.
• 10:39 UTC — The immutable head/base selection is reserved; waiting for its worker job to enter the serialized lane.
• 10:40 UTC — Still safely queued behind earlier admitted Lopu work; no duplicate resolver was spawned.
• 10:50 UTC — 10-minute check-in: still working — Waiting in Lopu's serialized PR-management lane.
• 11:01 UTC — 10-minute check-in: still working — Waiting in Lopu's serialized PR-management lane.
• 11:02 UTC — Still safely queued behind earlier admitted Lopu work; no duplicate resolver was spawned.
• 11:03 UTC — The resolver worker completed successfully and the PR is no longer open.

Technical run details — optional; this comment is the human-facing source of truth.