[aaron-y-chen]

The scheduled canary on main (Tests (ARM) run) fails deterministically on every core test job and on static checks. This comes from two PRs merged on the same day that conflict without a merge conflict:

• Keep retried task attempts and their data under the attempt UUID #74222 changed XComModel into a read projection over both XCom stores. The filters of XComModel.get_many() now live inside the aliased entity it selects, and columns added to that statement must be read through xcom_entity(query). The same PR added the check-xcom-model-columns hook to enforce this.
• Fix short-circuit in a mapped task group not skipping later tasks #74283 added _mapped_group_skip_decisions(), which projects XComModel.task_id, XComModel.map_index and XComModel.value onto the get_many() statement.

The base XComModel columns refer to the unfiltered projection, not the filtered alias. Projecting them with with_only_columns() and dropping the ordering removes the alias from the query, so every XCom row is read, whatever its run, Dag or key. A ShortCircuitOperator's boolean return_value then counts as a skip decision, and scheduling a task downstream of a short-circuit in a mapped task group fails with TypeError: argument of type 'bool' is not iterable. Outside the tests this also means one full XCom read per mapped task group per scheduling pass.

Reading the columns through xcom_entity(query) keeps the query on the filtered alias, as the other get_many() callers already do.

---

Error Msg:

    airflow-core/src/airflow/ti_deps/deps/not_previously_skipped_dep.py:181:37: `XComModel.task_id` is used directly in a SQLAlchemy query; read it through `xcom_entity(query).<column>` instead.
    airflow-core/src/airflow/ti_deps/deps/not_previously_skipped_dep.py:181:56: `XComModel.map_index` is used directly in a SQLAlchemy query; read it through `xcom_entity(query).<column>` instead.
    airflow-core/src/airflow/ti_deps/deps/not_previously_skipped_dep.py:181:77: `XComModel.value` is used directly in a SQLAlchemy query; read it through `xcom_entity(query).<column>` instead.

---

Was generative AI tooling used to co-author this PR?

• Yes (please specify the tool below)

Generated-by: [Claude Opus-5.5] following the guidelines

---

• Read the Pull Request Guidelines for more information. Note: commit author/co-author name and email in commits become permanently public when merged.
• For fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
• When adding dependency, check compliance with the ASF 3rd Party License Policy.
• For significant user-facing changes create newsfragment: {pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.

[yuseok89]

Looks good to me. Thanks for the quick fix!

[potiuk]

Thanks!