Skip to content

merge queue: checking #1915 on main (f060314) - #1916

Closed
mergify[bot] wants to merge 7 commits into
mainfrom
mergify/merge-queue/598b44724a
Closed

mergify[bot] wants to merge 7 commits into
mainfrom
mergify/merge-queue/598b44724a

Conversation

@mergify

@mergify mergify Bot commented Oct 25, 2026 •

Copy link
Copy Markdown
Contributor

Note

This is a merge queue draft opened by Mergify. Nobody needs to act on it.
Mergify opened it for batch sophisticated-tapenade-en13v5 of the default queue, to test #1915 before it merges into main. Pushing to this branch or closing this pull request removes #1915 from the queue.

What this draft tests

Mergify checks that #1915 still passes CI on top of main. CI runs on this draft's code, built in this order:

  1. main at f060314
  2. #1915, the pull request of this batch

🎉 Where it stands: checks passed

CI passed on this draft.

Follow the default queue in the dashboard

What happens next

  • Mergify merges #1915 into main and closes this draft.
Metadata for CI tooling, read by mergify ci
---
all_scopes: false
checking_base_sha: f06031435259b9148d9fc550244cb0dd6af7d85f
previous_check_retries: []
previous_failed_batches: []
pull_requests:
  - number: 1915
    scopes: []
scopes: []
...
Required conditions of queue rule default for merge
  • check-success = gates (linux)
  • check-success = gates (windows)
  • check-success = red-first
  • github-review-approved [🛡 GitHub repository ruleset rule main-pr-required-checks]
  • label != do-not-merge
  • any of [🛡 GitHub repository ruleset rule main-pr-required-checks]:
    • check-success = @github-actions/gates (linux)
    • check-neutral = @github-actions/gates (linux)
    • check-skipped = @github-actions/gates (linux)
  • any of [🛡 GitHub repository ruleset rule main-pr-required-checks]:
    • check-success = @github-actions/gates (windows)
    • check-neutral = @github-actions/gates (windows)
    • check-skipped = @github-actions/gates (windows)
  • any of [🛡 GitHub repository ruleset rule main-pr-required-checks]:
    • check-success = @github-actions/red-first
    • check-neutral = @github-actions/red-first
    • check-skipped = @github-actions/red-first
  • any of [🛡 GitHub repository ruleset rule main-pr-required-checks]:
    • check-neutral = @mergify/Mergify Merge Protections
    • check-skipped = @mergify/Mergify Merge Protections
    • check-success = @mergify/Mergify Merge Protections
Required conditions to stay in the queue

Cuarroc and others added 7 commits October 25, 2026 16:11
Exercise the mounted App at the Tauri boundary before implementing LIVE.
All four new cases fail on the missing live launcher at the exact base.

Plan-ID: KR-08c-2b-LIVE
Test-First: src/screens/terminal/TerminalRoute.test.tsx::appends an explicit live launch without replacing existing worker tabs
Test-First: src/screens/terminal/TerminalRoute.test.tsx::fences live insertion before exit subscription
Test-First: src/screens/terminal/TerminalRoute.test.tsx::retains live launch failure across dismissal restore and remount until acknowledgement
Co-Authored-By: GPT-6 Astra <noreply@openai.com>
Reuse the shared pending guard and retained request feedback in live views.
Track explicit route-local insertion before exit subscription settlement,
normalize the worker link and close the mounted chooser after success.
Keep chooser errors in the action strip without covering the viewer.

Plan-ID: KR-08c-2b-LIVE
Test-First: src/screens/terminal/TerminalRoute.test.tsx::appends an explicit live launch without replacing existing worker tabs
Test-First: src/screens/terminal/TerminalRoute.test.tsx::fences live insertion before exit subscription
Test-First: src/screens/terminal/TerminalRoute.test.tsx::retains live launch failure across dismissal restore and remount until acknowledgement
Test-First: src/screens/terminal/TerminalRoute.test.tsx::keeps the same request pending across empty live and empty subscription views
Co-Authored-By: GPT-6 Astra <noreply@openai.com>
Resolve the event-name gate finding without changing test expectations.

Plan-ID: KR-08c-2b-LIVE
Test-First: src/screens/terminal/TerminalRoute.test.tsx::fences live insertion before exit subscription
Test-First: src/screens/terminal/TerminalRoute.test.tsx::keeps the same request pending across empty live and empty subscription views
Co-Authored-By: GPT-6 Astra <noreply@openai.com>
Retain all deferred completions so assertion failures cannot leave
additional IPC promises pending during unconditional public cleanup.

Plan-ID: KR-08c-2b-LIVE
Test-First: src/screens/terminal/TerminalRoute.test.tsx::fences live insertion before exit subscription
Test-First: src/screens/terminal/TerminalRoute.test.tsx::keeps the same request pending across empty live and empty subscription views
Co-Authored-By: GPT-6 Astra <noreply@openai.com>
Expose R1915-C4 through the mounted App and Tauri boundary: a pending
ad-hoc insertion must retain the busy restore panel and restart result.
The regression compiles and fails against reviewed production 99d9478.

Plan-ID: KR-08c-2b-LIVE
Test-First: src/screens/terminal/TerminalRoute.test.tsx::preserves an explicit restart and its restore panel when a pending launch inserts
Co-Authored-By: OpenAI gpt-6-astra <noreply@openai.com>
Use the existing anchored popover without growing the live action strip.
Keep a newer explicit restart and restore panel intact during ad-hoc
insertion. Disarm settled launch snapshots only after checking committed
session state, preserving insertion-before-subscription observation.

Address R1915-C1/C2/C4/C5 and update the package's pending review status.

Plan-ID: KR-08c-2b-LIVE
Test-First: src/screens/terminal/TerminalRoute.test.tsx::preserves an explicit restart and its restore panel when a pending launch inserts
Co-Authored-By: OpenAI gpt-6-astra <noreply@openai.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant