Description
When an app hop calls a function that is also modelled as a from_resource worker app, the worker starts its own consumer-root trace, so span counts double and the worker log’s trace_id never joins the request trace that failed. Carry the caller’s trace context into the worker request (span link or parent) per messaging semantic conventions.
Acceptance Criteria
- #1 A worker request triggered by a traced hop joins or links the caller’s trace
- #2 Workers without a traced caller unchanged
Definition of Done
- #1 just check (fmt-check, lint, gen-check, env-check, docs-check, test, race, hygiene, ui-check, compose-check, helm-test, lab-check, signal-fidelity)
- #2 just gen (only if a blueprint field, construct/workload config struct, or a skill under plugins/synthkit/skills/ changed)
- #3 just dump — inventory diffed against signals/