[jason810496]

• related: TypeScript SDK: embed source and integrity sections in packed bundles #69905
• follow-up to review comments on Add integrity metadata to TypeScript bundles #72046
• Depends on TS SDK: minify packed bundles and find them by metadata, not filename #73126 get merged first (only the last commit is new here).
• Diff for early review: jason810496/airflow@refactor/ts-sdk/bundle-discovery-and-minify...feature/ts-sdk/bundle-entrypoint-source

Why

The shipped code region is minified, so it was nothing readable for Airflow to display for a natively authored TypeScript Dag so we need another section in the artifact to show the entry point raw source.

How

• A packed bundle now carries the entry module as its author wrote it, in a region with its own byte range and SHA-256 digest in the layout header:

  //# airflowBundle={"code":{...},"metadata":{...},"source":{...}}
  //# airflowMetadata={...}
  /*# airflowSource
  <the entrypoint, readable>
  #*/
  <minified code>
  

• Only the entry module will be included in the source, not the whole module graph behind it.

• A block comment rather than the line comments the layout and metadata use.

• The source range's length is declared rather than derivable from a newline, so the reader pins it by checking that the prescribed opener and closer sit where the declared range implies.

• Rename the metadata dags mapping to task_handlers, which is what a TypeScript bundle currently provides: handlers for Dags declared elsewhere, not Dag definitions of its own.

• The cross-language golden fixture is reworked. Its code region was the raw contents of a .ts fixture while its
  source region was a trivial export {};, which is backwards from what the packer emits.

  • It now carries a code region nobody could read and a source region that exercises both escape branches,
    so the Python reader is validated against bytes the TypeScript encoder actually produced.
  • The fixture is added to .prettierignore, which would otherwise reformat it and invalidate its digests.

---

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

• Yes, with help of Claude Code Opus 5 following the guidelines

[pierrejeambrun]

Nice — LGTM thanks