Value Statement

Upgrade Maestro to work with the newest sdk-go updates. This includes removing the CloudEvents sdk-go dependency from MQTT v2 options, updating to the new metrics and options interface, and switching manifestwork version handling to use generation instead of resource version.

Definition of Done for Engineering Story Owner (Checklist)

• MQTT v2 options no longer depend on CloudEvents sdk-go.

• Maestro uses the new sdk-go structure for metrics and options.

• ManifestWork version tracking now uses generation instead of resource version.

• Keep gRPC source client still using old (v1) options.
• All builds and tests pass.

Development Complete

• The code is complete.
• Functionality is working.
• Any required downstream Docker file changes are made.

Tests Automated

• [ ] Unit/function tests have been automated and incorporated into the
  build.
• [ ] 100% automated unit/function test coverage for new or changed APIs.

Secure Design

• [ ] Security has been assessed and incorporated into your threat model.

Multidisciplinary Teams Readiness

• [ ] Create an informative documentation issue using the Customer

Portal Doc template that you can access from [The Playbook](

https://docs.google.com/document/d/1YTqpZRH54Bnn4WJ2nZmjaCoiRtqmrc2w6DdQxe_yLZ8/edit#heading=h.9fvyr2rdriby),

and ensure doc acceptance criteria is met.

• Call out this sentence as it's own action:

• [ ] Link the development issue to the doc issue.

Support Readiness

• [ ] The must-gather script has been updated.