chore(codeql): restack #2106 on protected main

[seonghobae]

Purpose

Non-force ancestry integration for #2106.

• target branch before integration: bedce1323ad5872950372942f6ebc22ab1e53994
• protected main source: fb17ef556f94f673234aa557254ae52779e9a7b0
• main advanced five commits on six non-overlapping paths
• fix(codeql): bootstrap versioned dispatch handler #2106's seven-path handler bootstrap and review repair remain the target-branch delta

A merge commit here is the ordinary two-parent equivalent of Update branch: it preserves both histories without force push or rebase. The combined tree was independently reconstructed before this PR and passed 3071 tests / 1 skipped / 36 subtests, py_compile, and diff check. This PR changes no production authority on protected main; #2106 still requires fresh exact-head hosted Checks and qualifying review after the resulting synchronize event.

[github-advanced-security]

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

• The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
• Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
• You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.

[github-advanced-security]

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

• The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
• Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
• You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.

[github-advanced-security]

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

• The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
• Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
• You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Advanced

Run ID: 698e8ead-978c-42a6-bcab-75fd758bbd64

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[seonghobae]

Exact restack review at head fb17ef556f94f673234aa557254ae52779e9a7b0, base bedce1323ad5872950372942f6ebc22ab1e53994.

Protected main's five commits change six paths that do not overlap #2106's seven-path delta. The combined tree was reconstructed from exact remote blobs and passed 3071 tests / 1 skipped / 36 subtests, py_compile, and diff check. A merge commit preserves both histories and is equivalent to GitHub's Update branch operation; it does not land #2106 on protected main. No force push, rebase, bypass, or evidence transfer.

[seonghobae]

Evidence correction: the earlier 3071 count did not yet include protected main's six newly added/modified runtime-quality/materializer paths. After reconstructing every main@fb17ef556f94f673234aa557254ae52779e9a7b0 blob together with #2106's exact delta and review repair, the authoritative combined-tree result is 3073 passed / 1 skipped / 36 subtests, with py_compile and diff check PASS. The merge commit 48c6304ffb7294c4748ddc00388e72aa2e9d49bf is 0 behind main and still changes only #2106's intended seven paths relative to main.