feat: Add queue name, description, and op models

[cleptric]

Add convention models for queue operations (queue, queue.publish, queue.create, queue.receive, queue.process, queue.settle). Name and description inference use messaging.destination.name, with a static "Queue" fallback for names.

Name model (model/name/queue.json)

Infers span names from messaging.destination.name, falling back to "Queue".

Description model (model/description/queue.json)

Infers span descriptions from messaging.destination.name.

Op model (model/op/queue.json)

Defines the six queue span operations with descriptions. Generated JS and Rust constants are included.

[github-actions]

Semver Impact of This PR

🟡 Minor (new features)

📋 Changelog Preview

This is how your changes will appear in the changelog.
Entries from this PR are highlighted with a left border (blockquote style).

---

New Features ✨

• (description) Add cache and resource description models by cleptric in #444
• (name) Add resource span name model by cleptric in #445

• Add queue name, description, and op models by cleptric in #446

• Add name and description models for browser and url.template for HTTP server by cleptric in #448

---

_{🤖 This preview updates automatically when you update the PR.}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

Want reviews to match your repository better? Bugbot Learning can learn team-specific rules from PR activity. A team admin can enable Learning in the Cursor dashboard.

^{Reviewed by Cursor Bugbot for commit d1c3f36. Configure here.}

[cursor]

Queue ops lack name model

Medium Severity

This change registers queue.publish, queue.create, queue.receive, queue.process, and queue.settle in the op and description models, but model/name/messaging.json still omits those ops. Span name inference only applies to ops listed in name conventions, so spans using the new queue operations will not get the intended messaging.destination.name / Queue naming described in the PR.

Additional Locations (1)

• model/description/messaging.json#L6-L7

 

^{Reviewed by Cursor Bugbot for commit d1c3f36. Configure here.}