Move Task Identity line into Pre Execution block in logs

[jscheffl]

In #66036@ashb optimized the struct log to replace the task identity attributes with a single log line.

Still one log line between the "Log message source details" and "Pre Execute" block.

This PR makes another round of log UI cleaning and moves the log line into the "Pre Execute" log group. Is this okay? For me looks much cleaner and the task identity is actually only needed for troubleshooting in my view. Not for a user checking logs.

Before this PR/main:

Default view after this change:

If you expand the "Pre Execute" block the Task Identity is displayed:

---

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

• Yes (please specify the tool below)

Claude Sonnet 4.5 (but only for fixing JSX tests)

---

• 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.

[github-actions]

Backport failed to create: v3-2-test. View the failure log Run details

Note: As of Merging PRs targeted for Airflow 3.X
the committer who merges the PR is responsible for backporting the PRs that are bug fixes (generally speaking) to the maintenance branches.

In matter of doubt please ask in #release-management Slack channel.

Status	Branch	Result
❌	v3-2-test

You can attempt to backport this manually by running:

cherry_picker 059ceef v3-2-test

This should apply the commit to the v3-2-test branch and leave the commit in conflict state marking
the files that need manual conflict resolution.

After you have resolved the conflicts, you can continue the backport process by running:

cherry_picker --continue

If you don't have cherry-picker installed, see the installation guide.

[vatsrahul1001]

@jscheffl could you help with manual backport?

[jscheffl]

@jscheffl could you help with manual backport?

Will do in a moment! (just arrived home after work...)

[jscheffl]

In #66036@ashb optimized the struct log to replace the task identity attributes with a single log line.

Still one log line between the "Log message source details" and "Pre Execute" block.

This PR makes another round of log UI cleaning and moves the log line into the "Pre Execute" log group. Is this okay? For me looks much cleaner and the task identity is actually only needed for troubleshooting in my view. Not for a user checking logs.

Before this PR/main:

Default view after this change:

If you expand the "Pre Execute" block the Task Identity is displayed:

---

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

• Yes (please specify the tool below)

Claude Sonnet 4.5 (but only for fixing JSX tests)

---

• 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.

[github-actions]

Backport failed to create: v3-2-test. View the failure log Run details

Note: As of Merging PRs targeted for Airflow 3.X
the committer who merges the PR is responsible for backporting the PRs that are bug fixes (generally speaking) to the maintenance branches.

In matter of doubt please ask in #release-management Slack channel.

Status	Branch	Result
❌	v3-2-test

You can attempt to backport this manually by running:

cherry_picker 059ceef v3-2-test

This should apply the commit to the v3-2-test branch and leave the commit in conflict state marking
the files that need manual conflict resolution.

After you have resolved the conflicts, you can continue the backport process by running:

cherry_picker --continue

If you don't have cherry-picker installed, see the installation guide.

[vatsrahul1001]

@jscheffl could you help with manual backport?

[jscheffl]

@jscheffl could you help with manual backport?

Will do in a moment! (just arrived home after work...)

[jscheffl]

In #66036@ashb optimized the struct log to replace the task identity attributes with a single log line.

Still one log line between the "Log message source details" and "Pre Execute" block.

This PR makes another round of log UI cleaning and moves the log line into the "Pre Execute" log group. Is this okay? For me looks much cleaner and the task identity is actually only needed for troubleshooting in my view. Not for a user checking logs.

Before this PR/main:

Default view after this change:

If you expand the "Pre Execute" block the Task Identity is displayed:

---

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

• Yes (please specify the tool below)

Claude Sonnet 4.5 (but only for fixing JSX tests)

---

• 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.

[github-actions]

Backport failed to create: v3-2-test. View the failure log Run details

Note: As of Merging PRs targeted for Airflow 3.X
the committer who merges the PR is responsible for backporting the PRs that are bug fixes (generally speaking) to the maintenance branches.

In matter of doubt please ask in #release-management Slack channel.

Status	Branch	Result
❌	v3-2-test

You can attempt to backport this manually by running:

cherry_picker 059ceef v3-2-test

This should apply the commit to the v3-2-test branch and leave the commit in conflict state marking
the files that need manual conflict resolution.

After you have resolved the conflicts, you can continue the backport process by running:

cherry_picker --continue

If you don't have cherry-picker installed, see the installation guide.

[vatsrahul1001]

@jscheffl could you help with manual backport?

[jscheffl]

@jscheffl could you help with manual backport?

Will do in a moment! (just arrived home after work...)

[jscheffl]

In #66036@ashb optimized the struct log to replace the task identity attributes with a single log line.

Still one log line between the "Log message source details" and "Pre Execute" block.

This PR makes another round of log UI cleaning and moves the log line into the "Pre Execute" log group. Is this okay? For me looks much cleaner and the task identity is actually only needed for troubleshooting in my view. Not for a user checking logs.

Before this PR/main:

Default view after this change:

If you expand the "Pre Execute" block the Task Identity is displayed:

---

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

• Yes (please specify the tool below)

Claude Sonnet 4.5 (but only for fixing JSX tests)

---

• 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.

[github-actions]

Backport failed to create: v3-2-test. View the failure log Run details

Note: As of Merging PRs targeted for Airflow 3.X
the committer who merges the PR is responsible for backporting the PRs that are bug fixes (generally speaking) to the maintenance branches.

In matter of doubt please ask in #release-management Slack channel.

Status	Branch	Result
❌	v3-2-test

You can attempt to backport this manually by running:

cherry_picker 059ceef v3-2-test

This should apply the commit to the v3-2-test branch and leave the commit in conflict state marking
the files that need manual conflict resolution.

After you have resolved the conflicts, you can continue the backport process by running:

cherry_picker --continue

If you don't have cherry-picker installed, see the installation guide.

[vatsrahul1001]

@jscheffl could you help with manual backport?

[jscheffl]

@jscheffl could you help with manual backport?

Will do in a moment! (just arrived home after work...)

[jscheffl]

In #66036@ashb optimized the struct log to replace the task identity attributes with a single log line.

Still one log line between the "Log message source details" and "Pre Execute" block.

This PR makes another round of log UI cleaning and moves the log line into the "Pre Execute" log group. Is this okay? For me looks much cleaner and the task identity is actually only needed for troubleshooting in my view. Not for a user checking logs.

Before this PR/main:

Default view after this change:

If you expand the "Pre Execute" block the Task Identity is displayed:

---

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

• Yes (please specify the tool below)

Claude Sonnet 4.5 (but only for fixing JSX tests)

---

• 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.

[github-actions]

Backport failed to create: v3-2-test. View the failure log Run details

Note: As of Merging PRs targeted for Airflow 3.X
the committer who merges the PR is responsible for backporting the PRs that are bug fixes (generally speaking) to the maintenance branches.

In matter of doubt please ask in #release-management Slack channel.

Status	Branch	Result
❌	v3-2-test

You can attempt to backport this manually by running:

cherry_picker 059ceef v3-2-test

This should apply the commit to the v3-2-test branch and leave the commit in conflict state marking
the files that need manual conflict resolution.

After you have resolved the conflicts, you can continue the backport process by running:

cherry_picker --continue

If you don't have cherry-picker installed, see the installation guide.

[vatsrahul1001]

@jscheffl could you help with manual backport?

[jscheffl]

@jscheffl could you help with manual backport?

Will do in a moment! (just arrived home after work...)

[jscheffl]

In #66036@ashb optimized the struct log to replace the task identity attributes with a single log line.

Still one log line between the "Log message source details" and "Pre Execute" block.

This PR makes another round of log UI cleaning and moves the log line into the "Pre Execute" log group. Is this okay? For me looks much cleaner and the task identity is actually only needed for troubleshooting in my view. Not for a user checking logs.

Before this PR/main:

Default view after this change:

If you expand the "Pre Execute" block the Task Identity is displayed:

---

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

• Yes (please specify the tool below)

Claude Sonnet 4.5 (but only for fixing JSX tests)

---

• 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.

[github-actions]

Backport failed to create: v3-2-test. View the failure log Run details

Note: As of Merging PRs targeted for Airflow 3.X
the committer who merges the PR is responsible for backporting the PRs that are bug fixes (generally speaking) to the maintenance branches.

In matter of doubt please ask in #release-management Slack channel.

Status	Branch	Result
❌	v3-2-test

You can attempt to backport this manually by running:

cherry_picker 059ceef v3-2-test

This should apply the commit to the v3-2-test branch and leave the commit in conflict state marking
the files that need manual conflict resolution.

After you have resolved the conflicts, you can continue the backport process by running:

cherry_picker --continue

If you don't have cherry-picker installed, see the installation guide.

[vatsrahul1001]

@jscheffl could you help with manual backport?

[jscheffl]

@jscheffl could you help with manual backport?

Will do in a moment! (just arrived home after work...)

[jscheffl]

In #66036@ashb optimized the struct log to replace the task identity attributes with a single log line.

Still one log line between the "Log message source details" and "Pre Execute" block.

This PR makes another round of log UI cleaning and moves the log line into the "Pre Execute" log group. Is this okay? For me looks much cleaner and the task identity is actually only needed for troubleshooting in my view. Not for a user checking logs.

Before this PR/main:

Default view after this change:

If you expand the "Pre Execute" block the Task Identity is displayed:

---

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

• Yes (please specify the tool below)

Claude Sonnet 4.5 (but only for fixing JSX tests)

---

• 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.

[github-actions]

Backport failed to create: v3-2-test. View the failure log Run details

Note: As of Merging PRs targeted for Airflow 3.X
the committer who merges the PR is responsible for backporting the PRs that are bug fixes (generally speaking) to the maintenance branches.

In matter of doubt please ask in #release-management Slack channel.

Status	Branch	Result
❌	v3-2-test

You can attempt to backport this manually by running:

cherry_picker 059ceef v3-2-test

This should apply the commit to the v3-2-test branch and leave the commit in conflict state marking
the files that need manual conflict resolution.

After you have resolved the conflicts, you can continue the backport process by running:

cherry_picker --continue

If you don't have cherry-picker installed, see the installation guide.

[vatsrahul1001]

@jscheffl could you help with manual backport?

[jscheffl]

@jscheffl could you help with manual backport?

Will do in a moment! (just arrived home after work...)

[jscheffl]

In #66036@ashb optimized the struct log to replace the task identity attributes with a single log line.

Still one log line between the "Log message source details" and "Pre Execute" block.

This PR makes another round of log UI cleaning and moves the log line into the "Pre Execute" log group. Is this okay? For me looks much cleaner and the task identity is actually only needed for troubleshooting in my view. Not for a user checking logs.

Before this PR/main:

Default view after this change:

If you expand the "Pre Execute" block the Task Identity is displayed:

---

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

• Yes (please specify the tool below)

Claude Sonnet 4.5 (but only for fixing JSX tests)

---

• 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.

[github-actions]

Backport failed to create: v3-2-test. View the failure log Run details

Note: As of Merging PRs targeted for Airflow 3.X
the committer who merges the PR is responsible for backporting the PRs that are bug fixes (generally speaking) to the maintenance branches.

In matter of doubt please ask in #release-management Slack channel.

Status	Branch	Result
❌	v3-2-test

You can attempt to backport this manually by running:

cherry_picker 059ceef v3-2-test

This should apply the commit to the v3-2-test branch and leave the commit in conflict state marking
the files that need manual conflict resolution.

After you have resolved the conflicts, you can continue the backport process by running:

cherry_picker --continue

If you don't have cherry-picker installed, see the installation guide.

[vatsrahul1001]

@jscheffl could you help with manual backport?

[jscheffl]

@jscheffl could you help with manual backport?

Will do in a moment! (just arrived home after work...)