Skip to content

ci: trim unused workflow-guard setup and duplicate capture work - #13486

Merged
teamleaderleo merged 109 commits into
mainfrom
ci/guard-python-deps-owned-groups
Sep 22, 2026
Merged

teamleaderleo merged 109 commits into
mainfrom
ci/guard-python-deps-owned-groups

Conversation

@teamleaderleo

@teamleaderleo teamleaderleo commented Sep 21, 2026 •

Copy link
Copy Markdown
Collaborator

Summary

Collapse the workflow-guard setup cleanup stack into one current-main landing unit.

The guard matrix keeps the same checks while making setup follow the groups that actually consume it:

  • Bun setup runs only in the guard groups that invoke Bun;
  • Python 3.9 is installed only for the nightly-prune compatibility owner;
  • the other Python guard groups use the runner Python inside an isolated venv;
  • PyYAML is installed only in the Python-owning guard groups;
  • bashlex is added only in the release group that runs the Ghostty Zig workflow parser;
  • the pipe-safe CI capture guard runs only in its app-host owner instead of once per matrix group;
  • the quality lanes skip Python dependency bootstrap they never use.

Why

The matrix had accumulated job-wide setup even as individual checks moved into narrower groups. That makes every shard pay for tools owned by a small subset of checks and obscures which check actually depends on which runtime/package.

Keeping setup beside its consumer makes the matrix cheaper and easier to edit without silently broadening common-path work.

Testing

Regression coverage pins:

  • Bun-owning groups;
  • Python 3.9 release ownership;
  • venv/PyYAML-owning groups;
  • release-only bashlex installation;
  • exactly one setup-python action;
  • pipe-safe capture ownership.

Demo Video

N/A — CI guard setup only.

Review Trigger

@codex review
@coderabbitai review
@greptileai review
@cubic-dev-ai review

Checklist

  • Guard semantics remain unchanged
  • Tool setup is scoped to consuming groups
  • Pinned dependency versions are preserved
  • Ownership is regression-tested
  • No production/runtime code changes

Supersedes #13483, #13484, and #13485.

@github-actions

Copy link
Copy Markdown
Contributor

All contributors have signed the CLA ✍️ ✅
Posted by the CLA Assistant Lite bot.

* fix(ios): preserve supported tagged App Groups

* ci: keep iOS-only tests off macOS runners

* ci: run tagged iOS signing regression on Linux

* ci: freeze legacy iOS test routing path

* fix(ios): harden tagged signing fallback detection

* fix(ios): fail closed on partial ASC signing credentials

* fix(ios): validate ASC key path before device signing

* chore(ios): report tagged device signing backend

* docs(ios): keep cheap regressions off macOS routing

* test(ios): bind fallback entitlements to retry build

* ci: catch nested iOS-only test routing footguns

* test(iOS): bind fallback entitlements to retry command

* fix(iOS): correct retry assertion pattern

Copy link
Copy Markdown
Collaborator Author

@greptileai review

teamleaderleo and others added 5 commits September 21, 2026 19:34
…rminal disconnects (#13471)

* iOS: add failing disconnected-composer-seat fixture and regression test (#13470)

CMUX_UITEST_WORKSPACE_DETAIL_DISCONNECTED=1 mounts a workspace shell whose
one retained terminal is Disconnected, with no Mac or sign-in; scenario
drop-after-focus starts connected, focuses the composer at t+2s (real
keyboard), and drops the Mac to unavailable at t+9s.

The new XCUITest rides the dock probe through the raise and the
blocked-input resign, waits for the settled keyboard-down rest, then
asserts the dock's constraint-resolved bottom edge leaves the whole bottom
safe area below it. On the iOS <=26 keyboard-guide seat the dock instead
rests at the raw screen bottom, so this test fails until the fix.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

* iOS: floor the keyboard-guide dock seat at the bottom safe area (#13470)

With the keyboard up over a connected terminal, the Mac dropping to
unavailable blocks input, which resigns the keyboard. After that show->hide
cycle UIKeyboardLayoutGuide rests at the RAW host bottom instead of the
bottom safe area (usesBottomSafeArea notwithstanding), so the accessory
toolbar and composer bar land inside the home-indicator band -
permanently, because blocked input means no keyboard event ever re-seats
the guide.

Add a required dock.bottom <= host.bottom - resolvedBottomSafeAreaInset
floor, active only with the guide seat, and downgrade the guide equality to
999 so it yields exactly the clamped distance when the guide rests too low.
The floor is slack whenever the keyboard holds the guide higher, follows
the same resolved-inset sources as the plain seat, and deactivates with the
guide in the chrome-hidden state (whose dock parks at the raw bottom by
design). The iOS 27 notification seat already computes from the resolved
inset and is unaffected.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
* ci: split release guards into parallel groups

Squashed onto current main after #13501 merged.

* test: include split release groups in guard matrix contract

* test: include split release groups in guard matrix contract

Copy link
Copy Markdown
Collaborator Author

@greptile-apps review

* ci: skip macOS preflight when macOS is unrouted

* test(ci): cover skipped macOS preflight routing

* test(ci): preserve preflight contract migration marker
@cursor

cursor Bot commented Sep 22, 2026

Copy link
Copy Markdown

Bugbot is paused — on-demand spend limit reached

Bugbot uses usage-based billing for this team and has hit its on-demand spend limit.

A team admin can raise the spend limit in the Cursor dashboard, or wait for the next billing cycle to continue.

teamleaderleo and others added 9 commits September 21, 2026 20:08
Fix Cloud display ownership and connection readiness
Start macOS validation after cheap static checks, remove the obsolete agent review gate workflow, and fix the stale iOS guard matrix route.
* ci: route tagged iOS entitlement guard to release-ios

* test: own tagged iOS entitlement guard in release-ios
…eanup

#13531: retire and background-reap cold warm-slot task state
…cation

fix(review): require proof for repaired findings
…ollowup

Preserve iPhone viewport lease across output stream churn
@teamleaderleo
teamleaderleo enabled auto-merge (squash) September 22, 2026 03:50
teamleaderleo and others added 4 commits September 22, 2026 03:56
* ci(ios): resolve manual test refs to full SHAs

* test(ci): cover manual iOS short-SHA dispatches

* test(ci): fix iOS workflow job parser

* ci: run iOS dispatch-ref regression on Linux
* iOS: allow all photo library task attachments

* iOS: export Foundation for recovery API

* iOS: accept video attachments in terminal composers

* iOS: show videos in composer photo pickers

* Clarify composer picker comments

* Keep photo library attachment picker unfiltered

* Bound Photos library attachment transfers

* Make Photos attachment timeout authoritative

* ci: route tagged iOS entitlement guard to release-ios
* Add structured iOS connectivity diagnostics to Axiom

* refactor: move telemetry helper to file scope

* refactor: keep diagnostic bounds in payload assembly

* fix: bound event surface telemetry
@cursor

cursor Bot commented Sep 22, 2026

Copy link
Copy Markdown

Bugbot is paused — on-demand spend limit reached

Bugbot uses usage-based billing for this team and has hit its on-demand spend limit.

A team admin can raise the spend limit in the Cursor dashboard, or wait for the next billing cycle to continue.

@teamleaderleo
teamleaderleo merged commit bb6b5f2 into main Sep 22, 2026
55 checks passed
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.

4 participants