Description
A worker: true app entry’s CONSUMER root span is named by the route default (GET /); per messaging semantic conventions a consumer span is named for the operation and destination. Source the name from signals/traces.md or the pinned messaging conventions.
Acceptance Criteria
- #1 Worker entry root spans carry a sourced messaging operation name
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/
Implementation Notes
Historical evidence reconciliation: 6f759e65 and sourced process/destination naming regression red then green; canonical messaging contract and composed story assertion retained. Full gate e029aa8e, run20261025T121935Z-synthkit-bb72a72a exit0. Naming is not full messaging-attribute compliance. Conditional generation not applicable; qualifying signals-inventory comparison missing, remaining boxes unchecked.