Correct comment: canvas tasks can't carry taskbadger_parent

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

Author: snopoke

taskbadger/celery.py

@@ -324,16 +324,19 @@ def _maybe_create_task(signal_sender):
     delivery_info = getattr(signal_sender.request, "delivery_info", None) or {}
     queue = delivery_info.get("routing_key")
     external_id = signal_sender.request.id
-    # `before_task_publish` never ran for these, so per-call options are still
-    # sitting in the headers rather than resolved into the message.
+    # `before_task_publish` never ran for eager tasks, so their per-call options
+    # are still sitting in the headers rather than resolved into the message.
+    # Canvas tasks never have any here: `task_publish_handler` strips TB headers
+    # off `celery.*` messages before its early return, so nothing reaches the
+    # worker.
     header_kwargs = headers.get(TB_KWARGS_ARG) or {}
     create_kwargs = {
         "status": StatusEnum.PENDING,
         "data": data,
         "queue": queue,
         "external_id": external_id,
         # eager and canvas tasks are created here rather than at publish time, but
-        # still run inside whatever task invoked them. An explicit
+        # still run inside whatever task invoked them. For eager tasks an explicit
         # `taskbadger_parent` wins, as it does at publish time — including an
         # explicit `None`, which asks for a root task.
         "parent": header_kwargs["parent"] if "parent" in header_kwargs else parent_id(),